Connect any MCP client to Unitpost

Any streamable-HTTP MCP client that speaks MCP OAuth connects with just the URL. Anything else uses a Bearer API key.

  1. Connect with OAuth (recommended)

    Point the client at the server URL below. A spec-compliant client discovers OAuth itself: it reads the WWW-Authenticate: Bearer resource_metadata="…" challenge on the first 401, fetches /.well-known/oauth-protected-resource, runs the PKCE code flow against the advertised authorization server, and retries with the token. No key to copy. Your client opens Unitpost in the browser — pick a workspace, approve the scopes, and you're connected. Tokens refresh automatically.

    Server URLhttps://mcp.unitpost.com/mcp
    TransportStreamable HTTP
    Auth (recommended)OAuth 2.1 — add the URL, approve in the browser
    Auth (legacy)Authorization: Bearer pk_live_YOUR_KEY
    Toolsone per API operation (email_send, email_campaigns_send, …)
    Toolsets (optional)https://mcp.unitpost.com/mcp?toolsets=default,campaigns
  2. Discover tools

    The server advertises one tool per API operation (email_send, email_campaigns_send, email_domains_verify, …). A write's body maps to the API request body. Every tool declares securitySchemes: [{ type: "oauth2", scopes: […] }] so linking-aware clients (ChatGPT) show the Connect UI.

  3. Choose toolsets (optional)

    With no parameters the server lists its default set of tools, the same list it always has. Newer tools come in groups: add ?toolsets= to the URL, or send an X-MCP-Toolsets header, with any of audience, templates, campaigns, sending, inbox, domains and workspace (the server instructions list every group), plus default for the standard set and all for everything. ?readonly=1 (X-MCP-Readonly: 1) lists only read tools and refuses writes; ?scoped=1 (X-MCP-Scoped: 1) hides tools your key can't call. Fewer tools means less of the model's context spent on tool definitions.

    Text
    https://mcp.unitpost.com/mcp?toolsets=default,campaigns,templates
  4. Verify

    Call a read tool (e.g. list domains). An unauthenticated call answers 401 with a WWW-Authenticate: Bearer resource_metadata="…" challenge (start OAuth there). With a key, a 401 Invalid API key usually means a missing Bearer prefix or a mistyped key — recreate the key and retry.

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

No browser on this machine? For headless setups, CI, SSH, or clients that can only paste a key, use the API-key setup instead.

Search docs and guides

Search the docs and product guides.