Agenticmail

What agenticmail/agenticmail MCP server does

The agenticmail/agenticmail MCP server connects AI agents to real email and SMS workflows. It can provide disposable inboxes, send messages, receive messages, retrieve verification codes, and operate an inbox programmatically. The project is designed to run locally rather than route core email activity through a third-party email API.

This makes it suitable for agents that need to register for services, monitor an inbox, respond to incoming mail, or complete processes that deliver one-time codes by email or SMS. The repository also describes phone-based capabilities, including outbound calling and realtime voice support through supported carrier transports, but those features require additional configuration and services.

How it works

The MCP package exposes AgenticMail functionality to an MCP-compatible client. The local service manages the agent’s mail and messaging operations, while disposable inboxes provide temporary addresses for workflows where a permanent mailbox is unnecessary. Agents can use received messages and verification codes as inputs to subsequent tasks.

The broader project includes an HTTP API and agent-oriented features beyond basic messaging. Its later releases describe persistent per-agent memory, Telegram messaging, phone missions, and voice bridges. These capabilities are part of the same project but may depend on separate providers, credentials, or configuration. The media toolset described in the repository is marked unreleased and should not be treated as a generally available MCP capability.

Setup and configuration

The simplest MCP installation described by the project is:

npx -y @agenticmail/mcp

The repository’s setup instructions also provide a CLI-based route for Claude Code: install @agenticmail/cli globally and run agenticmail bootstrap. That flow is presented as an alternative setup path and asks the user to restart Claude Code afterward.

Basic email and SMS use does not list a required environment variable in the supplied material. Realtime voice support requires OPENAI_API_KEY; the README says this can be supplied through the environment or config.json. Phone features also require a provisioned number with a supported transport provider, including 46elks or Twilio, depending on the feature and setup.

Tools and capabilities

The agenticmail/agenticmail MCP server supports:

• Sending real email from an agent.
• Receiving email and working with an inbox.
• Creating or using disposable inboxes.
• Fetching verification codes from received messages.
• Sending and receiving SMS through the project’s phone functionality.
• Connecting agents to phone-call workflows, including realtime voice features described in the repository.

The project also documents MCP memory tools and a Telegram channel in newer releases. Those are additional agent features rather than replacements for the email and SMS functions.

Limitations and notes

Some capabilities are provider-dependent. The README identifies 46elks and Twilio as phone transport options, and realtime voice additionally depends on OpenAI Realtime configuration. The live voice paths described for those releases still require operator smoke testing according to the repository notes.

The media/video tools are explicitly labeled unreleased. They also depend on locally installed binaries such as ffmpeg, ffprobe, ImageMagick, whisper.cpp, or Python, none of which are bundled. Avoid assuming that these tools are available in the published MCP installation.

The supplied material does not specify a software license, supported MCP client list, or a complete authentication model. Those details should be verified in the repository before production deployment.