SuperAPI AI Directory

agentmail-mcp

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

Open website

About this tool

AgentMail MCP is the official MCP implementation repository for the AgentMail project, with the goal of providing email capabilities for AI agents: create inboxes on demand to send and receive emails and take action based on emails.

Purpose This project is aimed at scenarios that require AI agents to handle email, and the only MCP tool implementation is provided by the AgentMail hosted server.

Main capabilities and structure

  • Hosted MCP server: packages/server in the repository is the hosted MCP server and the only AgentMail tool implementation. It uses a Streamable HTTP endpoint, and clients that support remote MCP can connect directly to this endpoint. This endpoint provides the tool catalog of the current runtime and supports both authentication paths already available on the hosted server: OAuth and per-request API keys. Related usage instructions can be found in the AgentMail MCP documentation.
  • stdio compatibility bridges: To be compatible with clients that only support stdio, the repository provides two bridges. Existing Node configurations can continue to work through the npm bridge; Python users can run the equivalent local bridge. Both bridges discover tools and schemas from the hosted server and do not themselves contain the AgentMail SDK, toolkits, REST API, or tool definition logic.
  • Tool filtering: For stdio clients that need to filter the tool catalog, the --tools name1,name2 parameter can still be used.

Repository contents

  • packages/server: the hosted MCP server, the only AgentMail tool implementation.
  • packages/npm-stdio-bridge: the npm package agentmail-mcp.
  • python/stdio-bridge: the PyPI package agentmail-mcp.
  • mcp-manifest.json: the generated runtime contract.
  • tests: contract and transport checks.
  • docs: architecture, compatibility, migration, release, and operations documentation.

Compatibility and migration notes The old local npm implementation is retained on the legacy-local-v0.2.2 branch. Authentication hardening is a separate project, and this consolidation keeps the existing behavior of the hosted server unchanged.

Limitations and not yet provided The materials do not provide specific installation commands, how to obtain API keys, OAuth configurationdetails, the list of supported clients, billing methods, pricing, or the functional limits for sending and receiving email.