How to Post to Social Media From Cursor
Cursor connects to a social media MCP server through mcp.json. Put the Blotato endpoint at https://mcp.blotato.com/mcp with a blotato-api-key header in ~/.cursor/mcp.json to make it available everywhere, or in .cursor/mcp.json inside a project to scope it to that repo. Restart Cursor and publishing is available in the same editor as the code that generates the content.
https://mcp.blotato.com/mcp API key header Updated August 2026
How to connect Cursor to social media
- Connect your social accounts in Blotato and copy your API key from Settings then API.
- Decide the scope: ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one repo.
- Copy the MCP config from Blotato Settings then API, under Other MCP Clients, and paste it in.
- Restart Cursor. MCP servers load on startup.
{
"mcpServers": {
"blotato": {
"url": "https://mcp.blotato.com/mcp",
"headers": {
"blotato-api-key": "YOUR_API_KEY"
}
}
}
}
How do I know it worked?
Ask Cursor to list your connected accounts. It calls
blotato_list_accounts and returns your platforms, which confirms both the connection and
the authentication in one step. If you see your accounts, setup is done.
What social media accounts do I have connected?
Worth knowing before you rely on it: analytics prompts only return data for X, Instagram, Facebook, Threads, and Bluesky. The other four platforms publish normally but report no metrics yet.
What to ask Cursor once it is connected
- Post the screenshot I just took to X with a short caption.
- Cursor uploads it with blotato_create_presigned_upload_url and publishes with blotato_create_post, without leaving the editor the screenshot came from.
- Queue these three posts into my next open slots.
- Three blotato_create_post calls with useNextFreeSlot, which fills the schedule you already configured instead of asking you to pick three times.
- Add the link as a first comment rather than in the caption.
- The firstComment field on blotato_create_post, which Blotato posts as the first comment on the published post. Instagram and Facebook only, and not on stories.
What breaks, and how to fix it
The failure that catches Cursor users is pointing it at the OAuth URL on its own and getting an auth unsupported error. Cursor cannot complete the OAuth browser flow for this server, so use the API-key config rather than the bare endpoint. The second is scope confusion: a server added to one project's .cursor/mcp.json is invisible in every other project, which reads as the config silently failing.
What is different about Cursor
Cursor is the only client here that scopes MCP servers two ways from the same file name, project-level in .cursor/mcp.json or globally in ~/.cursor/mcp.json. It also resolves variables inside command, args, env, url, and headers, so the API key can come from an environment variable rather than sitting in plain text in a file you might commit.
Vendor documentation: Cursor MCP setup. For how a client discovers and calls tools once connected, see the MCP client concepts reference.
Cursor social media FAQs
01 Can Cursor post to social media?
02 How do I connect Cursor to social media?
03 How do I set up Cursor for social media?
04 What is the best way to manage social media with Cursor?
05 What goes wrong when connecting Cursor?
06 Does Cursor need to be running for a scheduled post to go out?
07 What can I ask Cursor to do once it is connected?
08 How much does it cost to connect Cursor?
Connecting a different agent?
Same endpoint, same accounts, one setup per client. The AI agents for social media hub covers what all of them share, including every tool your agent can call.