Email for Claude agents

Claude speaks MCP natively. Add MCPmailer as a connector and Claude can send, receive, and wait for email replies in any conversation or agent workflow.

Setup

  1. 01

    Open Settings, then Connectors

    In the Claude app. Add custom connector, then paste the URL.

  2. 02

    Sign in

    A browser window opens. Approve, and there is no key to copy back.

  3. 03

    Pick what it may do

    The approval screen lists scopes: reading mail and sending are separate.

  4. 04

    Ask it to check your mail

    The tools show up in the conversation straight away.

Claude Code (.mcp.json)
{
  "mcpServers": {
    "mcpmailer": {
      "type": "http",
      "url": "https://connect.mcpmailer.com/mcp",
      "headers": { "Authorization": "Bearer mmk_live_..." }
    }
  }
}

Worth knowing

01

The connector route needs no key

Signing in through the connector screen issues a scoped session. The config block on the right is for Claude Code and anything else editing files by hand.

02

Project scope versus user scope

A .mcp.json in the repo is shared with anyone who checks it out, which is why the key belongs in an env var rather than inline. claude mcp add --scope user keeps it to your machine.

03

Revoking is immediate

Connections in your dashboard lists every app acting as your agents. Revoke one and its next call fails, without touching your other clients.

What Claude can reach

The endpoint speaks Streamable HTTP MCP with 67 tools across mail, contacts, notes, and a vault, including send_email, read_message, search_inbox, and wait_for_reply. Errors are structured so Claude can react: a quota rejection includes the reset time.