LABSCO SUMMARY

The endpoint is the product.

Both bridges are deliberately empty — no SDK, no schemas, no REST calls — so whatever the hosted server gains, a stdio client picks up without upgrading anything, and the two transports cannot drift apart.

What it is

AgentMail's single MCP implementation, hosted at https://mcp.agentmail.to/mcp over Streamable HTTP. Everything else in the repository is transport: an npm bridge and a PyPI bridge that pull the tool catalog from that server and forward calls to it.

What you get

The hosted endpoint as the primary integration, over OAuth or the server's per-request API-key header
npx -y agentmail-mcp with AGENTMAIL_API_KEY for Node clients that only speak stdio
uvx agentmail-mcp for the same thing without a Node toolchain
A tool catalog discovered at runtime, so new tools reach you on the next connection rather than in a bridge release
--tools name1,name2 to hand a stdio client a filtered catalog instead of the whole surface
Structured MCP results and errors preserved through both bridges, which hold no SDK and no tool definitions of their own

Requirements

An AgentMail API key in AGENTMAIL_API_KEY, or OAuth where your client supports it. Nothing to install on the hosted path. If you are on the Python bridge, know its one gap: cancelling a call stops the local wait but the server keeps processing, because the Python SDK version it targets exposes no way to forward the cancellation upstream.

Setup effort

One command plus a key — npx -y agentmail-mcp, then supply credentials

See installation options

USE CASES

01

Connecting a client that already speaks remote MCP

Point it at the hosted URL and authorise; there is nothing to install and nothing to keep updated.

02

Using a client stuck on stdio

Run the npm or PyPI bridge as a local process with your key in the environment, and get the same catalog.

03

Keeping the tool list small for a focused agent

Pass an explicit tool list to the stdio bridge so the model sees only what that agent needs.

04

Avoiding an upgrade treadmill

Tools are discovered from the server at connect time, so a new capability does not require a package bump.

BEFORE YOU INSTALL

What to know first

Requires

npx on PATH
AGENTMAIL_API_KEY in your environment

INSTALLATION

Connect your client

Server setup

npx

TERMINAL

npx -y agentmail-mcp

Hosted endpoint

ENDPOINT URL

https://mcp.agentmail.to/mcp

Add this hosted endpoint to your MCP client using the credentials listed under Requirements.

MCP Clients

Any MCP client — npx

ANY MCP CLIENT — NPX · JSON

{
  "mcpServers": {
    "AgentMail": {
      "command": "npx",
      "args": [
        "-y",
        "agentmail-mcp"
      ],
      "env": {
        "AGENTMAIL_API_KEY": "<YOUR_AGENTMAIL_API_KEY>"
      }
    }
  }
}

Any MCP client — uvx

ANY MCP CLIENT — UVX · TERMINAL

AGENTMAIL_API_KEY=<YOUR_AGENTMAIL_API_KEY> uvx agentmail-mcp

AgentMail