# agentmail-to/agentmail-mcp [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/agentmail-to/agentmail-mcp  
**GitHub Stars:** 69  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/agentmail-to-agentmail-mcp

## Description
Email for AI agents: create inboxes on the fly to send, receive and act on email.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "agentmail-mcp": {
    "command": "uvx",
    "args": ["agentmail-mcp"],
    "env": {
      "AGENTMAIL_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `AGENTMAIL_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What agentmail-to/agentmail-mcp MCP server does

The agentmail-to/agentmail-mcp MCP server gives AI agents access to AgentMail email workflows. Its supported use cases include creating inboxes as needed, sending email, receiving email, and acting on messages. This makes it suitable for agents that need to communicate through email without a manually provisioned inbox for every workflow.

The project provides access through a hosted MCP deployment and two local bridge packages. The hosted deployment is the source of the runtime tool catalog. The npm and Python packages provide client-facing stdio adapters that discover the available tools and their schemas from that hosted service.

## How it works

Remote-capable MCP clients can connect directly to `https://mcp.agentmail.to/mcp` using Streamable HTTP. The hosted endpoint supports its existing OAuth and per-request API-key authentication paths.

For clients configured around local processes, the npm package starts with `npx -y agentmail-mcp`. Python users can run the equivalent bridge with `uvx agentmail-mcp`. In both cases, the bridge forwards access to the hosted implementation rather than containing a local AgentMail SDK, REST API implementation, toolkit, or tool-definition layer.

The stdio bridge also supports `--tools name1,name2`, allowing a client to request a filtered tool catalog when it does not need every available tool.

## Setup and configuration

A Node-based MCP configuration can define the server with the `agentmail-mcp` npm package and pass an `AGENTMAIL_API_KEY` environment variable:

```json
{
  "mcpServers": {
    "AgentMail": {
      "command": "npx",
      "args": ["-y", "agentmail-mcp"],
      "env": { "AGENTMAIL_API_KEY": "YOUR_API_KEY" }
    }
  }
}
```

The Python bridge can be started from a shell with `AGENTMAIL_API_KEY=YOUR_API_KEY uvx agentmail-mcp`. For remote connections, use the hosted endpoint and the authentication method supported by the client and service. The repository includes separate hosted-server, npm-bridge, and Python-bridge areas, along with generated contract and transport tests.

## Tools and capabilities

AgentMail exposes email-oriented MCP capabilities for:

- Creating inboxes dynamically.
- Sending email from an agent workflow.
- Receiving email for an agent-managed inbox.
- Acting on email messages.
- Discovering the hosted server’s current tools and schemas.

The available catalog comes from the hosted server at runtime. A filtered catalog can be requested through the stdio bridge with the `--tools` option.

## Limitations and notes

The agentmail-to/agentmail-mcp MCP server’s local bridges are adapters, not independent implementations of the AgentMail API. They do not package the SDK, toolkit, REST API, or tool definitions locally, so operation depends on access to the hosted MCP service and its current runtime catalog.

The README does not identify specific desktop or coding clients by name, so compatibility with a particular client should be checked against that client’s support for Streamable HTTP or stdio MCP connections. The repository notes that the older local npm implementation remains under `legacy-local-v0.2.2`; the current setup is based on the hosted server and bridge architecture.

_Full upstream README: https://allmcps.com/mcp/agentmail-to-agentmail-mcp/readme_