From the maker

Autoposting connects AI assistants to a selected social media workspace. Generate drafts and carousels, create clips from uploaded video, and schedule or publish to connected X, LinkedIn, Instagram, Threads and YouTube accounts. The hosted server uses Streamable HTTP and OAuth 2.1 with dynamic client registration and scoped workspace permissions. Product features require paid Autoposting access. The linked repository provides public setup metadata, not the hosted implementation.

How to connect

Streamable HTTP endpoint:

https://app.autoposting.ai/mcp

What happened when we asked

We asked on 2 October 2026 and it challenged us for credentials. That is a working server guarding itself: it answered, and it wants an account we do not hold. A tool count and a response time come from a tools/list we were never served, so this listing carries neither.

How it asks you to sign in

Its refusal named a public document describing how to authenticate, which is what the MCP authorization spec asks a guarded server to publish. We read that document on 2 October 2026. Everything below is what it says; we have still not been inside this server.

Sign in through

app.autoposting.ai

Token accepted in

header

Its own docs

https://docs.autoposting.ai/mcp

Read

2026-10-02 22:12 UTC

The 2 permissions it declares

These are the scopes the document lists, verbatim. They describe what an account can grant this server, not what it will do with the grant, and we have not audited either.

• read
• write

Anything above describes one moment on the date shown. We do not re-test on a schedule, so nothing here says what this server is doing now. We have not audited its code, its data handling or its permissions, and this is not a safety rating.