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.
https://mcp.blotato.com/mcp API key header Updated July 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.
{
"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.
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.
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 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.
Windsurf social media FAQs
01 Can Windsurf post to social media?
02 How do I connect Windsurf to social media?
03 How do I set up Windsurf for social media?
04 What is the best way to manage social media with Windsurf?
05 What goes wrong when connecting Windsurf?
06 Does Windsurf need to be running for a scheduled post to go out?
07 Do I need a developer app or platform API keys to use Windsurf this way?
08 What can Windsurf not do on social media?
09 How much does it cost to connect Windsurf?
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.