Skip to main content
The Paubox MCP Server authenticates against the Paubox Email API on your behalf. You provide your API key once when configuring the connection. A key set on the connection (the OAuth connector, a request header, or an environment variable) is not passed through the AI model.
1

Sign up for a Paubox account

If you don’t have one, sign up for Paubox Email API. Free tier includes up to 300 emails per month.
2

Add and verify your domain

Go to Paubox Email API > Domains and add the domain you will send from. Complete domain verification before generating an API key; unverified domains cannot send email.
3

Generate an API key

From Paubox Email API > API Keys, press Add API Key. Give the key a name, select the Paubox Email API scope (add Paubox Forms if you’ll use the Forms management tools), and choose your verified sender domain. Copy the key when it’s created; it is displayed only once.
4

Pass your API key to the MCP server

How you pass the key depends on the transport. Over HTTP, every request must carry a credential, either an OAuth Bearer token or the x-paubox-api-key header; requests with neither are rejected. If both are sent, the header wins. Over stdio, the key comes only from the PAUBOX_API_KEY environment variable.1. OAuth connector form (HTTP, recommended for Claude.ai and Claude Desktop)Add https://mcp.paubox.com as a connector. The client presents a Configure Paubox form automatically. Enter your API key once; the client stores a short-lived encrypted Bearer token and sends it on every subsequent request.2. Custom request headers (HTTP)Some MCP clients let you set custom headers on the connector. Pass:
3. Environment variables (stdio / Claude Code)The stdio server exits at startup if PAUBOX_API_KEY is missing or shorter than 10 characters.
Claude Code / stdio config:
4. Per-call tool parameters (HTTP only)Over HTTP, every tool except submit_form accepts an optional apiKey parameter. When passed, it overrides the key from the header or OAuth token for that call. The request still needs its own header or Bearer credential to reach the server. The stdio server does not accept an apiKey parameter.
Never commit API keys to source control. Use environment variables or a secrets manager to inject credentials at runtime.

Required permissions

See MCP tools for the tools in each area. get_form and submit_form call public Forms API endpoints, but the server connection itself still needs a credential: the HTTP transport rejects requests without a header or Bearer token, and the stdio server does not start without PAUBOX_API_KEY.