Your mailbox as MCP tools

A native Model Context Protocol (MCP) server. Point an MCP client at one endpoint and your agent gets email as callable tools.

API reference ↗

MCP endpoint

https://mail.sairaph.com/mcp/v1/mcp
Authorization: Bearer $SAIRAPH_MAIL_KEY

The MCP endpoint and a mailbox key.

How it works

The server speaks the streamable-HTTP transport. Authentication is a mailbox API key, the same scoped key as the REST API, so a client gets only the role you grant. Connect a client and the mailbox's actions appear as tools.

Connect a client

Point your client at the MCP endpoint and pass a mailbox API key as a Bearer token.

Claude Desktop

{
  "mcpServers": {
    "sairaph-mail": {
      "type": "streamable-http",
      "url": "https://mail.sairaph.com/mcp/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${SAIRAPH_MAIL_KEY}"
      }
    }
  }
}

What your agent can do

The mailbox surfaces its actions as tools: messages.send, messages.list, messages.search, threads.reply, and the rest of the mailbox surface. The full tool set is published from the live server in the API reference ↗.

Scoped by design

Each key is scoped to a single mailbox with one role and an optional expiry, so a connected client can do only what you allow. Suppression and limits are isolated per mailbox.

Security & trust

Wire up MCP

Get started Read the quickstart