Cursor

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.

Endpoint https://mcp.blotato.com/mcp API key header

Connect Cursor See pricing

Updated July 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.

~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one

{
  "mcpServers": {
    "blotato": {
      "url": "https://mcp.blotato.com/mcp",
      "headers": {
        "blotato-api-key": "YOUR_API_KEY"
      }
    }
  }
}

Cursor MCP documentation showing remote server configuration — Cursor's own MCP documentation, showing where the remote server config goes.

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.

First prompt to run

What social media accounts do I have connected?

An AI agent answering "what social accounts do i have connected?" by calling Blotato and listing 10 connected social media accounts across Twitter, Bluesky, Instagram, Threads, LinkedIn, Facebook, YouTube, Pinterest, and TikTok — The reply you are looking for: the agent calls Blotato and lists every connected account. Here it returns 10 accounts across all nine platforms.

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 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.

FAQ

Cursor social media FAQs

01 Can Cursor post to social media?

Yes. Cursor cannot reach a social account on its own, because it has no platform credentials. Connecting it to Blotato's hosted MCP server at https://mcp.blotato.com/mcp gives it tools to publish and schedule across nine platforms: X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest. Cursor authenticates with api key header.

02 How do I connect Cursor to social media?

03 How do I set up Cursor for social media?

Setting up Cursor for social media takes one connection. Connect your social accounts in Blotato, then give Cursor the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with api key header. For Cursor specifically that means: ~/.cursor/mcp.json for all projects, or .cursor/mcp.json for one. Once it loads, Cursor can publish and schedule to X, LinkedIn, Facebook, Instagram, TikTok, YouTube, Threads, Bluesky, and Pinterest from a plain-language prompt.

04 What is the best way to manage social media with Cursor?

Let Cursor do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on Cursor in particular: 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.

05 What goes wrong when connecting Cursor?

06 Does Cursor need to be running for a scheduled post to go out?

No. Scheduling runs on Blotato rather than inside Cursor. Once the agent queues a post, it publishes at the scheduled time whether or not Cursor, your terminal, or your laptop is on. This is the practical difference between an agent that drafts and a system that runs unattended.

07 Do I need a developer app or platform API keys to use Cursor this way?

No. Blotato holds the platform integrations and manages the OAuth tokens, including refreshes. You connect each social account through a normal login flow instead of registering your own app on every network and waiting for review. Cursor never handles a platform credential.

08 What can Cursor not do on social media?

Publishing and scheduling cover all nine platforms, but the rest is uneven and worth knowing before you build against it. Analytics covers X, Instagram, Facebook, Threads, and Bluesky. Comments and direct messages cover Instagram and Facebook. Keyword-triggered DM automation is not available at all. None of that varies by agent: it is the same surface whichever client you connect.

09 How much does it cost to connect Cursor?

Starter is $29/mo flat for 20 connected accounts, and the price does not scale with posting volume. API and MCP access is not part of the 7-day trial: generating a key activates the paid Starter plan, so plan on subscribing rather than trialing it.

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.