Skip to main content
Windsurf Cascade reads MCP servers from ~/.codeium/windsurf/mcp_config.json. Remote HTTP uses serverUrl (url also works). That is not Cursor’s mcp.json. This page is Cascade. The newer Devin Local agent (the default in new Windsurf tabs) configures MCP in Devin CLI files instead of mcp_config.json.
You need your PostQueen API key first. In the app at app.postqueen.ai, open Settings → API Keys and click Reveal.

​
Option A: Cascade UI

1

Open MCP settings

In the Cascade panel, click MCPs, or open Devin Settings → Cascade → MCP Servers.
2

Add PostQueen

PostQueen is not in the Windsurf marketplace. Edit the raw mcp_config.json and add the block below.

​
Option B: mcp_config.json

~/.codeium/windsurf/mcp_config.json
Field name per Windsurf Cascade MCP: remote HTTP needs serverUrl or url. ${env:VAR_NAME} interpolation works in serverUrl, url, and headers.
Your API key can post to every account you have connected. Keep mcp_config.json off shared screens. If the key leaks, regenerate it in Settings → API Keys and update every client that uses it.

​
Self-hosted

Swap the host for your NEXT_PUBLIC_BACKEND_URL and keep the /mcp/YOUR_API_KEY tail. Most self-hosted setups serve the backend under /api. The reverse proxy has to forward /mcp and stream the response: MCP on a self-hosted install.

​
Verify

In a Cascade chat, ask:
“List my connected social media accounts”
Your channel names come back when Cascade calls integrationList. Toggle the postqueen tools on the MCP settings page if they stay off. Teams can allowlist servers by the key name in mcp_config.json; a missing allowlist entry looks like a broken URL.