MCP Getting Started

MCP Getting Started

The MinuteMail MCP server lets AI assistants like Claude operate your MinuteMail account conversationally: create test mailboxes, wait for verification emails, extract codes and links, manage custom domains, teams, and mock OAuth identities — all through the Model Context Protocol.

• Endpoint: https://mcp.minutemail.co/mcp
• Transport: Streamable HTTP (protocol revision 2025-06-18)
• Auth: a MinuteMail API key sent as Authorization: Bearer mmak_...

The server is a stateless proxy over the MinuteMail REST API: it holds no credentials or sessions of its own and forwards your key verbatim, so API scopes and quotas apply exactly as they do for the REST API and SDK.

Get an API key

1. Sign up at minutemail.co (free during early access)
2. Open the dashboard → API Keys and create a key
3. Copy the key — it is shown only once (mmak_XXXXXXXX)

Connect Claude Code

claude mcp add --transport http minutemail https://mcp.minutemail.co/mcp \
  --header "Authorization: Bearer mmak_XXXXXXXX"

Connect Claude Desktop or Cursor

Add the server to your client config (claude_desktop_config.json for Claude Desktop, ~/.cursor/mcp.json for Cursor):

{
  "mcpServers": {
    "minutemail": {
      "type": "http",
      "url": "https://mcp.minutemail.co/mcp",
      "headers": {
        "Authorization": "Bearer mmak_XXXXXXXX"
      }
    }
  }
}

Older Claude Desktop builds only support stdio servers in the JSON config. If yours rejects type: "http", use its built-in remote-server UI with the URL and header above, or bridge with mcp-remote:

{
  "mcpServers": {
    "minutemail": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.minutemail.co/mcp",
        "--header",
        "Authorization: Bearer mmak_XXXXXXXX"
      ]
    }
  }
}

Try it

Once connected, ask your assistant to create a mailbox, then send a test email to its address:

“Create a MinuteMail mailbox that expires in 30 minutes.”

The agent will call the mailboxes.create tool and return the address. When a message arrives, mails.list / mails.get retrieve it so the agent can extract verification codes or links.

Available tools (40)

Every tool maps 1:1 to a REST API route. Write operations require the matching API key scope.

Group	Tools	Scope
Mailboxes	mailboxes.list/create/get/delete/delete_bulk, mails.*, attachments.*	mailboxes
Archived mailboxes	archived.list/get/delete/reactivate	mailboxes
Custom domains	domains.list/register/verify/delete	domains
Team	team.members.*, team.invitations.*	team
Mock identities & OAuth clients	identities.list/create/get/update/delete, oauth.clients.*	identities

Note: the claims parameter on identities.create / identities.update is a custom-provider feature — the API rejects it with a 400 for google, github, apple, and facebook clients. See Provider Behavior.

Errors surface as tool errors with the HTTP status: 401 invalid key, 403 scope/domain, 429 quota exceeded, 502 upstream down.

Related

• API Getting Started — the REST API the MCP server proxies
• SDK Getting Started — the Python SDK
• API Keys (web UI) — creating and scoping keys
• mcp-server source