API, MCP and extension
Connect an AI assistant to your workspace
Add the MCP server to an AI assistant, sign in and allow it on the consent page, choose the workspace, and see or remove connected assistants.
Most AI assistants connect to the MCP server with a sign-in, so you never paste a key.
Connect
- Copy the MCP Server URL from Settings, Security, AI Assistants (MCP).
- In your assistant, add a custom connector with that address.
- The assistant opens the SocialApp consent page. Sign in if you are not signed in.
- Check the name of the application and the address it returns to. The application chose its name itself, so allow it only if you started this connection.
- Pick the Workspace it may work in and see what it will be able to do.
- Choose Allow. Deny cancels.
The assistant works in that workspace only, with your role and access. Role changes apply at once, without reconnecting.
Assistants that cannot sign in
Some clients cannot use the sign-in. They can send an API key in the Authorization header instead. Never put a key in the server address; it is refused there.
See and remove connections
The AI Assistants (MCP) card lists Connected assistants: the application, who connected it, when, when it was last used, and its access. Everyone sees their own; Owners and Admins see the whole workspace's.
Remove ends a connection at once. Posts and drafts it created stay. A connection also ends when you change your password, when you are removed from the workspace, or when the assistant revokes it.