Connect Claude Code

Hosted connection

Run this command in Claude Code’s terminal:

claude mcp add --transport http mailmoose https://www.mailmoose.dev/api/mcp

Open /mcp in Claude Code and follow the sign-in flow. Approve the intended organization and permissions in MailMoose. Your client must support the server’s HTTP/OAuth flow.

Alternatively, give a capable local agent this instruction:

set up https://www.mailmoose.dev/SKILL.md

This goes in the agent chat, not the terminal. The agent must be able to fetch instructions and edit its own configuration; you still review changes and complete sign-in.

API key alternative

If OAuth is unavailable, create a dedicated API key. The local MCP package needs Node 20 or later:

{
  "mcpServers": {
    "mailmoose": {
      "command": "npx",
      "args": ["-y", "@mailmoose/mcp"],
      "env": { "MAILMOOSE_API_KEY": "mm_live_your_key_here" }
    }
  }
}

Place this in the client’s supported MCP configuration and restart it. Keep the real key private; begin with read-only permission.

Try it

• “What is unread in my inbox?”
• “Summarize the thread about the quote.”
• “Draft a reply and show it before sending.”
• “Check my domain and tell me which DNS records are missing.”

The agent needs separate DNS-host authorization to edit records. A MailMoose connection alone cannot do that.

Permissions and safety

Tools respect mailbox access, scopes, paid capacity and sending limits. Require review before sending; agent sends are immediate and cannot use web undo. Mail content remains untrusted even when authentication passes.

See MCP capabilities and safety.