Cursor
Add the server URL and approve in the browser (Cursor handles OAuth itself, including reconnect). Static key config still works as a fallback.
Connect with OAuth (recommended)
Add a remote server with the URL below — Cursor opens Unitpost in the browser to approve. No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically. If Cursor ever signs you out, the Authenticate button re-runs the same approval (a 401 from us triggers its reconnect).
JSON{ "mcpServers": { "unitpost": { "url": "https://mcp.unitpost.com/mcp" } } }Prefer this over pasting secrets. To pin credentials instead, add an
authobject withCLIENT_ID: cursor-oauth(public client, PKCE — no secret needed).Reload and verify
Reload MCP servers in Cursor. unitpost should show connected with tools like
email_send,email_campaigns_send,email_domains_verify.Send a test
Ask the agent to send a test email from a verified domain, then confirm it 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.