The short answer
SOSPosting runs an MCP server. Connect an AI assistant that supports remote MCP servers, approve access, and you can ask it to check what is connected, look at recent posts, or publish a new one to the networks you name.
What the assistant can do
| Tool | What it does | Type |
|---|---|---|
list_connected_platforms | Shows which networks are connected | Read |
get_token_balance | Shows the current token balance | Read |
list_recent_posts | Lists recent posts and their status | Read |
get_post | Shows one post and its per-network delivery | Read |
create_post | Publishes a post | Write |
Four of the five only read. The one that writes publishes publicly and spends tokens, and it is marked as destructive so that a client knows to confirm with you first.
Connecting
- Endpoint:
https://app.sosposting.com/api/mcp, over streamable HTTP. - Sign-in: OAuth 2.1 with PKCE, approved in your browser, or an API key from Settings, API access.
- Scope: each connection is bound to one business. To work with a second business, connect again and choose it.
You can disconnect an assistant at any time from the dashboard, which revokes its access.
What the server refuses to do
An assistant that can publish in your name deserves narrower permissions than you have yourself. Two things are deliberately left out:
- Buying tokens. The balance can be read, but money cannot be moved through the connector.
- Generating images, video or audio. The assistant publishes media you give it.
Before you connect one
Two honest cautions. First, a post is public the moment it is published, so decide whether your assistant should confirm each one, and check that it is set to. Second, the ordinary rules still apply: a video reaches up to five networks and a photo up to seven, and each network must already be connected in the dashboard. Developers who prefer plain HTTP can use the REST API instead.
Frequently asked questions
What is an MCP server for social media?
It is a service that exposes social media actions, such as listing connected accounts or creating a post, to an AI assistant through the Model Context Protocol, so the assistant can carry them out when you ask.
Can an AI assistant post to my accounts without asking me?
The create_post tool is annotated as destructive, which tells a well-behaved client to confirm with you before calling it. Whether it asks is ultimately decided by the assistant you use and how you have configured it, so check that setting before connecting.
Can the assistant spend my money?
It can publish posts, which spends tokens from your balance, and it can read the balance. It cannot buy tokens: purchasing is deliberately not available through the connector.
How does the assistant sign in?
Either through an OAuth 2.1 authorisation flow with PKCE, where you approve access in the browser, or with an API key created in the dashboard. Each connection is bound to one business.