Windsurf
Prefer the OAuth browser approval. If your setup needs static config, paste the key block instead.
What are the connection details?
| Server URL | https://mcp.unitpost.com/mcp |
|---|---|
| Transport | Streamable HTTP |
| Auth (recommended) | OAuth 2.1 — add the URL, approve in the browser(scopes match API capabilities; tokens refresh automatically) |
| Auth (legacy) | Authorization: Bearer pk_live_YOUR_KEY(workspace API key from Settings → API keys; for clients that can only paste a key) |
| Tools | one per API operation (email_send, email_campaigns_send, …) |
How do I connect Windsurf?
Connect with OAuth (recommended)
In Windsurf: Settings → Cascade → MCP Servers → Add Server, or paste this into `~/.codeium/windsurf/mcp_config.json`. Windsurf uses
serverUrl(noturl) for remote HTTP. No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically.JSON{ "mcpServers": { "unitpost": { "serverUrl": "https://mcp.unitpost.com/mcp" } } }Refresh and verify
Refresh the MCP server list. Unitpost's tools should appear under unitpost.
Send a test
Ask Cascade to send a test email from a verified domain, then confirm in Unitpost Activity.
No browser on this machine? For headless setups, CI, SSH, or clients that can only paste a key, use the API-key setup instead.