MCP server

An agent that speaks the Model Context Protocol can read, search, send and reply to email without any integration code. Point it at the server, give it a key, and the mailbox becomes nine tools.

Setup

Add the server to your MCP client’s configuration. Claude Desktop, Claude Code, and anything else that speaks MCP over stdio use the same shape.

json

{
  "mcpServers": {
    "sreemail": {
      "command": "npx",
      "args": ["-y", "@sreemail/mcp"],
      "env": { "SREEMAIL_API_KEY": "sk_live_..." }
    }
  }
}

Note

Give the key only emails:send. That is all this server needs, and it is the containment boundary if the agent is ever talked into something.

Tools

Tool	Does
`send_email`	New message from a verified domain.

Domains, webhooks, templates and key management are deliberately absent. Those are account operations rather than agent operations, and every tool listed costs context on every turn. Receiving mail is a separate service and is not exposed here.

Local development

SREEMAIL_BASE_URL points the server at a different deployment.