Windsurf

Windsurf Social Media MCP Setup

Windsurf connects to a social media MCP server through Cascade, which supports remote HTTP servers with custom headers. The config lives in ~/.codeium/windsurf/mcp_config.json, and remote servers use a serverUrl field rather than the url field most other clients take, which is the one detail that stops a copied Cursor config from working.

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

Connect Windsurf See pricing

Updated August 2026

How to connect Windsurf to social media

Connect your social accounts in Blotato and copy your API key from Settings then API.
Open ~/.codeium/windsurf/mcp_config.json, or use Cascade’s MCP settings panel.
Add the Blotato server using the serverUrl field, not url, with your key under headers.
Restart Windsurf so the server loads.

mcp_config.json entry using serverUrl, not url

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

Windsurf is now part of Devin Desktop under Cognition, so its MCP documentation lives in the Devin docs. Cascade takes the same JSON config as Cursor.

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

How do I know it worked?

Ask Windsurf 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 to ask Windsurf once it is connected

Draft a post about this refactor and put it on X.: Cascade drafts from the code it just changed, then calls blotato_create_post. The context that makes the post specific is already in the session.
Only give this agent the publishing tools.: On Teams and Enterprise an admin can allowlist the server centrally through the MCP registry, so engineers get the Blotato tools without each of them pasting a key into their own mcp_config.json.
Read the key from my environment instead of the config file.: Cascade interpolates variables in mcp_config.json, so the header value can reference an environment variable rather than sitting in plain text in a file you might commit.

What breaks, and how to fix it

The Windsurf-specific failure is pasting a config that works everywhere else. Remote HTTP servers here need serverUrl; a url field is what other clients use and Cascade will not pick the server up. On an Enterprise plan there is a second gate, since MCP has to be turned on in settings before any server appears at all. The last obstacle is finding the documentation, because Windsurf is now part of Devin Desktop under Cognition and older Windsurf-branded guides point at pages that have moved.

What is different about Windsurf

Windsurf is the only client here that names the remote endpoint field serverUrl, and the only one whose vendor documentation now sits under a different product name. Its config supports variable interpolation, so the API key can come from an environment variable rather than sitting in plain text in mcp_config.json. On Teams and Enterprise plans it also ships admin controls the others lack: an MCP allowlist and a registry, so an admin can permit the Blotato server centrally instead of every engineer configuring it themselves.

Vendor documentation: Windsurf MCP setup. For how a client discovers and calls tools once connected, see the MCP client concepts reference.

FAQ

Windsurf social media FAQs

01 Can Windsurf post to social media?

Yes. Windsurf 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. Windsurf authenticates with api key header.

02 How do I connect Windsurf to social media?

03 How do I set up Windsurf for social media?

Setting up Windsurf for social media takes one connection. Connect your social accounts in Blotato, then give Windsurf the hosted MCP endpoint https://mcp.blotato.com/mcp and authenticate with api key header. For Windsurf specifically that means: mcp_config.json entry using serverurl, not url. Once it loads, Windsurf 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 Windsurf?

Let Windsurf do the drafting and decision making, and let a publishing layer hold the accounts and the schedule. The thing that makes this work on Windsurf in particular: Windsurf is the only client here that names the remote endpoint field serverUrl, and the only one whose vendor documentation now sits under a different product name. Its config supports variable interpolation, so the API key can come from an environment variable rather than sitting in plain text in mcp_config.json. On Teams and Enterprise plans it also ships admin controls the others lack: an MCP allowlist and a registry, so an admin can permit the Blotato server centrally instead of every engineer configuring it themselves.

05 What goes wrong when connecting Windsurf?

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

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

07 What can I ask Windsurf to do once it is connected?

"Draft a post about this refactor and put it on X." Cascade drafts from the code it just changed, then calls blotato_create_post. The context that makes the post specific is already in the session. "Only give this agent the publishing tools." On Teams and Enterprise an admin can allowlist the server centrally through the MCP registry, so engineers get the Blotato tools without each of them pasting a key into their own mcp_config.json. "Read the key from my environment instead of the config file." Cascade interpolates variables in mcp_config.json, so the header value can reference an environment variable rather than sitting in plain text in a file you might commit.

08 How much does it cost to connect Windsurf?

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.