How to do it
- Make a key for Windsurf In https://app.socialhandoff.com, open Connections, add an agent called Windsurf, and give it draft permission on selected networks.
- Open the MCP config In Windsurf, open the Cascade panel, choose the MCP servers or plugins menu, and click to view the raw config. The file is ~/.codeium/windsurf/mcp_config.json.
- Add a remote server Paste the entry below. Windsurf uses serverUrl for streamable HTTP servers and accepts a headers object.
- Refresh the server list Save the file and press refresh in the MCP panel. The SocialHandoff tools should appear, each with its own toggle.
- Run a draft Ask Cascade for a post about your latest change, then approve or edit it in the SocialHandoff inbox.
{
"mcpServers": {
"social": {
"serverUrl": "https://app.socialhandoff.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_AGENT_KEY"
}
}
}
}What Cascade can do with SocialHandoff
Cascade plans multi-step work. When you ask for a launch post, it can read your changelog, call get_brand_memory for your voice rules, call draft_post once per network, and finish with preview_posts so you see the checks inline. Each call appears in the Cascade timeline. None of them publish.
Keep secrets out of the file
Windsurf supports environment variable interpolation in serverUrl and headers using its env: syntax. Put the key in an environment variable and reference it from the header value so the raw key never sits in mcp_config.json. Check the Windsurf MCP docs for the exact syntax your version expects, then restart Windsurf after changing the environment.
Prompts for Cascade
- "Look at the files changed today. Draft a short X post and a longer LinkedIn post for users, with a docs link. Draft only."
- "Plan a week of Mastodon posts from the open issues labeled good first issue, inviting contributors."
- "Show me pending Bluesky drafts and fix any over 300 graphemes."
- "Read brand memory and tell me which banned topics my draft touches."
Tool limits
Windsurf caps the total number of MCP tools Cascade can use at once. SocialHandoff exposes 11 tools. If you run several servers and hit the cap, turn off the ones you do not need for writing posts, such as get_insights, from the per-tool toggles in the MCP panel.
Permissions
Start with draft. Windsurf may run several tool calls in a row, so a per-account daily limit guardrail is a good backstop against a loop that drafts 40 posts. Promotion to auto-publish is per network and can be reversed; any guardrail failure demotes the agent immediately.
Troubleshooting
- Server missing after edit: press refresh in the MCP panel; Windsurf does not always reload automatically.
- Connection fails: make sure you used
serverUrlfor the remote entry and the URL ends in/mcp. - 401: header value must be
Bearerplus a space plus the key. - Admin disabled MCP: team plans can turn MCP off or allowlist servers. Ask your admin to allow the SocialHandoff endpoint.
Per-network setup: Windsurf for X, Windsurf for LinkedIn, Windsurf for Bluesky, Windsurf for Mastodon, and Windsurf for Threads.