Log inSubmit server
Agent Email logo

Agent Email

Read, search, organize, draft, and send Outlook or Gmail messages through MCP with configurable safety controls.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Agent Email

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "agent-email": {
      "command": "npx",
      "args": [
        "-y",
        "email-agent-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

Agent Email connects MCP-compatible agents to Microsoft 365/Outlook and Gmail mailboxes through a local stdio server. It supports email search and reading, thread retrieval, drafts, replies, sending, folders, labels, attachments, scheduling, and inbox rules. Sending is protected by an explicit recipient allowlist, while observation-only deployments can expose read-focused tools through a scope profile. Reach for it when an agent needs mailbox access without each workflow implementing provider-specific email APIs.

Use cases

  • Search a mailbox for messages matching a full-text query
  • Draft threaded replies without sending them
  • Send approved messages to allowlisted recipients
  • Download email attachments into a sandboxed directory
  • Organize messages with labels, flags, folders, and read-state changes

Key features

  • Microsoft 365/Outlook and Gmail mailbox access
  • Email search, reading, threading, and pagination
  • Draft creation, editing, replies, and sending
  • Recipient allowlists and observation-only scope profile
  • Attachment and raw message downloads
  • Folders, labels, scheduled sends, and inbox rules

Tools27

What Agent Email lets your agent do. Expand a tool for its parameters.

Verified live~6.0k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/22 checks healthy over the last 90d

What it can do

From the 27 tools this server returned when we ran it; 27 declare their own safety hints.

Runs commands · 1Can delete or modify data · 4Writes files · 1Handles credentials · 1Makes network requests · 2Read-only tools · 21
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age202 days
Maintainers1

Observed 2026-10-19 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · email-agent-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars7Stargazers on the source repository.
npm downloads1.5kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed27Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Agent Email works

What Agent Email does

Agent Email gives MCP-compatible runtimes access to configured Microsoft 365/Outlook and Gmail mailboxes. It can retrieve recent messages, search across mailboxes, read full message content, inspect conversation threads, and report mailbox status. Mailbox selection is explicit: list_mailboxes returns logical mailbox names, addresses, providers, connection states, and the default mailbox.

The server also covers common mailbox actions. Agents can create, edit, send, and reply to messages; apply labels or categories; change read and important/starred state; move messages between folders; and manage custom folders. Additional tools expose attachments, raw RFC 822 message downloads, scheduled sends, and server-side inbox rules.

How it works

Run the package locally over MCP stdio. The setup wizard guides OAuth configuration and mailbox selection, after which an MCP client invokes the email tools. A default full scope profile exposes read and write operations. Setting EMAIL_AGENT_MCP_SCOPE_PROFILE=observe before configuration and startup provides read-focused access and removes mailbox-mutating tools from the MCP surface.

Message bodies normally come back as token-efficient Markdown. HTML can be requested when inline formatting must be preserved, but HTML should only be written back when the complete, non-truncated body is available. Draft and send operations distinguish unsent drafts from delivered messages. Send and reply operations also detect duplicate attempts and report uncertain delivery states so an agent can check Sent Items before retrying.

Setup and configuration

Start the interactive setup with:

Terminal
npx -y email-agent-mcp

The server can be added to Claude Code or Cursor as a stdio MCP process using npx -y email-agent-mcp. Gemini CLI can install it from the GitHub repository. OpenClaw can run the package through an MCP stdio configuration; its mcp configuration key requires a sufficiently recent OpenClaw app.

Configure a send allowlist before enabling outbound mail. Delete operations are disabled by default and require explicit configuration. The full profile requests Microsoft delegated permissions for reading, writing, sending, mailbox settings, user identity, and offline access; observe requests a narrower read-oriented set. Changing profiles may require renewed consent, and an already granted token can retain previously consented write permissions.

Tools and capabilities

  • List, filter, paginate, search, and read messages across configured mailboxes.
  • Retrieve complete conversation threads and distinguish draft messages from sent mail.
  • Create, update, send, and reply to drafts, including threaded replies and recipient controls.
  • Apply labels, mark messages read or unread, flag them, and move them between folders.
  • Inspect, download, and save attachments or whole messages as sandboxed files.
  • List or cancel provider-held scheduled sends.
  • Create, inspect, and delete inbox rules using restricted actions; forwarding, redirection, and deletion actions are blocked when creating rules.

Limitations and notes

The observation profile reduces the available MCP tools but is not always an OAuth boundary when a mailbox previously received broader consent. Gmail draft deletion is permanent under the default scopes, while deleting sent or received Gmail messages is unsupported. Folder moves can produce a new message ID with Microsoft Graph.

Attachment downloads return inline base64 by default, with a default 5 MB limit and a 25 MB ceiling; saving to a sandboxed directory returns file metadata instead. Microsoft item/reference attachments are unsupported. Inbox rules continue acting after the agent session ends, so rule creation requires user confirmation.

If a send or reply returns an unknown status, delivery may already have occurred. Check Sent Items before retrying. Repeated identical sends are refused within the duplicate window unless a human explicitly permits the duplicate.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Agent Email

Agent Email is an MCP server that connects AI agents to Microsoft 365/Outlook and Gmail mailboxes. Its main tools list, search, read, and thread messages; create, update, send, and reply to email; organize mail; inspect attachments; and manage selected scheduled sends and inbox rules.

Install and start it with `npx -y email-agent-mcp`. An interactive wizard handles OAuth configuration and mailbox selection. You can then register the local stdio process in an MCP client such as Claude Code or Cursor.

Yes, Agent Email works with Cursor through a local stdio MCP configuration. Add an `email-agent-mcp` server entry whose command is `npx` and whose arguments are `-y` and `email-agent-mcp` in `.cursor/mcp.json`.

Set the `observe` scope profile before configuring and starting the server to remove mailbox-mutating tools from the MCP surface. For full-profile deployments, configure a send allowlist; delete operations are disabled by default.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAgent Email AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/agent-email?style=directory)](https://allmcps.com/mcp/agent-email)
HTML Embed
<a href="https://allmcps.com/mcp/agent-email"><img src="https://allmcps.com/api/badge/agent-email?style=directory" alt="Agent Email on AllMCPs" /></a>