agentmail-mcp

AgentMail MCP

Prefer the hosted Streamable HTTP server:

https://mcp.agentmail.to/mcp

It avoids a local Node.js process and the slower release cadence of the published local MCP package.

Claude Code, Codex, and Cursor

Use OAuth. Do not put an empty API key in the configuration.

{
  "mcpServers": {
    "agentmail": {
      "type": "http",
      "url": "https://mcp.agentmail.to/mcp"
    }
  }
}

Claude Code can also install it directly:

claude mcp add --transport http agentmail https://mcp.agentmail.to/mcp

Complete the browser sign-in on first connection. Multi-organization OAuth sessions can use the server's organization-selection tools.

Claude.ai, Claude Desktop, and ChatGPT connectors

These apps add the server as a connector and complete OAuth in the browser. No API key is needed.

• Claude.ai and Claude Desktop: Settings → Connectors → Add custom connector. Name it AgentMail, set the URL to https://mcp.agentmail.to/mcp, then click Connect and sign in at console.agentmail.to.
• ChatGPT: turn on Settings → Security and login → Developer mode (on a workspace plan, an admin must allow it first). Then open ChatGPT Plugins, click +, set the URL to https://mcp.agentmail.to/mcp, choose OAuth, and sign in at console.agentmail.to. In a chat, pick AgentMail from the + menu under Developer mode.

Connectors added on Claude.ai do not sync to Claude Code; add it there separately.

Per-client configuration

Add the same type: http server entry to the client's MCP config file:

• Cursor: .cursor/mcp.json
• VS Code: .vscode/mcp.json
• Windsurf: its MCP config file
• Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%/Claude/claude_desktop_config.json (Windows)

Auth options

• OAuth — browser-based sign-in, for clients that support remote MCP OAuth. Use the bare URL with no credentials.
• x-api-key header — recommended for clients without OAuth support (see below).
• Authorization: Bearer <am_...> header — an alternative header form some clients require.
• apiKey query param — supported but not recommended; prefer a header so the key doesn't end up in logs or history.