Unitpost/Guides

Claude Code

Add the server URL, then authenticate from the in-session MCP panel. The browser opens at the Authenticate step, not at add time. API keys still work as a fallback.

What are the connection details?

Server URLhttps://mcp.unitpost.com/mcp
TransportStreamable 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)
Toolsone per API operation (email_send, email_campaigns_send, …)

How do I connect Claude Code?

  1. Add the server

    Run once. This only saves the URL — no browser opens yet.

    Shell
    claude mcp add --transport http unitpost https://mcp.unitpost.com/mcp

    Use -s user to install for every project. claude mcp list now shows unitpost as ! Needs authentication — that is expected.

  2. Authenticate with OAuth (recommended)

    Start a Claude Code session, run /mcp, select unitpost, and choose Authenticate. Your browser opens to Unitpost — pick a workspace, approve the scopes, and you're connected. 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 the browser doesn't open automatically, copy the URL shown in the terminal and open it manually. Tokens refresh automatically; if auth ever lapses, repeat this step.

  3. Verify

    Run claude mcp list (or /mcp in a session). unitpost should show connected with its tools listed — no ! Needs authentication flag.

    Don't see it? Fully quit and reopen the client — closing the window is often not enough — then check again.

  4. Send a test

    Ask Claude to send an email from a verified domain and 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.