CommunicationPublic source

Email MCP Server

The most complete multi-backend email MCP server. 24 tools across 5 send backends and 3 read backends — send via SMTP, AWS SES, or SendGrid while reading from any IMAP server. File attachments, OAuth with auto-refresh,…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Multi-backend — 5 send + 3 read backends, mix and match freely

IMAP-first reading — works with any email provider, no OAuth required

SMTP-first sending — universal, works with any relay

Full email lifecycle — send, read, reply, forward, draft, organize, batch, delete

No credential exposure — tokens stay in env vars, never reach LLM context

Single binary — no Node.js, no Python, no runtime dependencies

Architecture

How Email MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Email MCP Server

Validates the request and owns 24 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Email MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Email MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

9 named tools shown from 24 documented tools

send_email

Send an email

external write

list_inbox

List inbox messages

read only

get_email

Get a specific email by ID

read only

search_emails

Search emails by query

read only

reply_to_email

Reply to an email

external write

list_labels

List email labels/folders

read only

move_to_folder

Move an email to a folder/label

external write

mark_read

Mark an email as read

external write

get_attachments

Get attachments for an email

read only

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

5 read only4 external write

IMAP-first reading — works with any email provider, no OAuth required

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-email

MCP client configuration

export SMTP_HOST="smtp.gmail.com"
export SMTP_PORT="587"
export SMTP_USERNAME="you@gmail.com"
export SMTP_PASSWORD="app-password"
export SMTP_FROM="you@gmail.com"
export IMAP_HOST="imap.gmail.com"
export IMAP_PORT="993"
export IMAP_USERNAME="you@gmail.com"
export IMAP_PASSWORD="app-password"

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md Api Reference ↗docs/api-reference.md Security ↗docs/security.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring