Skip to main content
Glama
Mail-MCP

Mail-MCP

by Rixtayz

Mail-MCP

CI npm Node License: MIT MCP Registry

Mail-MCP: AI-powered inbox control for Outlook

A small, focused MCP server that lets Claude (Claude Desktop, Cowork, Claude Code or any MCP client) work on a personal Outlook.com / Hotmail / Live mailbox through Microsoft Graph: read and search mail, file it into folders, delete it, and unsubscribe from newsletters.

Built for one job: clean up an overflowing personal inbox with an AI assistant, safely.

Tools

Nine tools, all prefixed mail_:

Tool

What it does

mail_list_folders

Folder tree with total / unread counts

mail_create_folder

Create a folder (idempotent)

mail_search

List / search messages (sender, date range, unread, full text), paginated

mail_get_message

Full content of one message + detected unsubscribe options

mail_senders_summary

Aggregate a whole folder by sender: volume, latest message, available unsubscribe method

mail_move

Move up to 500 messages to a folder

mail_delete

Move to Deleted Items by default, permanent: true to purge

mail_bulk_by_sender

Move or delete every message from one sender (dryRun supported)

mail_unsubscribe

RFC 8058 one-click POST → mailto: email → otherwise a URL for the assistant to open in a browser

Design choices:

  • Safe by default. Deletion goes to Deleted Items (visible and restorable in Outlook). Permanent deletion requires an explicit flag. Bulk actions support dryRun.

  • Efficient on big mailboxes. mail_senders_summary scans thousands of messages in a few seconds (1,000-item pages, minimal $select) and only fetches headers for the top senders through $batch.

  • No generic send tool. The Mail.Send permission is used solely to send mailto: unsubscribe requests.

  • Every tool ships a strict input schema, an output schema and MCP annotations (readOnlyHint, destructiveHint, …) so hosts can auto-approve read-only calls.

Inbox chaos to inbox zero with Mail-MCP: analyze senders, review, unsubscribe, organize, and safely delete

Related MCP server: outlook-mcp

Requirements

  • Node.js 22 or newer.

  • A personal Microsoft account (outlook.com, hotmail.com, live.com, msn.com).

  • A free Microsoft Entra app registration (5 minutes, below). Password-based IMAP was switched off for personal accounts in September 2024, so an OAuth app is the only supported way in.

1. Register an app in Microsoft Entra (once, free)

No Azure subscription is needed for a public client app.

  1. Go to https://entra.microsoft.com and sign in with your personal Microsoft account.

  2. Identity → Applications → App registrations → New registration.

  3. Fill in:

    • Name: Mail-MCP

    • Supported account types: Personal Microsoft accounts only

    • Redirect URI: platform Mobile and desktop applications, value http://localhost

  4. Click Register and copy the Application (client) ID (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

  5. Under Authentication, make sure http://localhost is listed under "Mobile and desktop applications" and Allow public client flows is Yes.

  6. Under API permissions, add Microsoft Graph delegated permissions: Mail.ReadWrite, Mail.Send, User.Read, offline_access. No admin consent is needed; you consent at first sign-in.

No client secret is created: the server is a public client using the authorization code flow with PKCE.

2. Sign in

No install needed, npx fetches the package from npm (@rixtay/mail-mcp, the installed command is mail-mcp):

MAIL_MCP_CLIENT_ID=<your-client-id> npx -y @rixtay/mail-mcp login

Or from a clone:

git clone https://github.com/Rixtayz/Mail-MCP.git
cd Mail-MCP
npm install && npm run build
MAIL_MCP_CLIENT_ID=<your-client-id> npm run login

The login command opens your system browser, signs you in with Microsoft, then stores the token cache in ~/.mail-mcp/token-cache.json (file mode 600). Tokens refresh silently for 90 rolling days. If a tool ever answers "Token expired", run the same command again.

Environment variable

Purpose

MAIL_MCP_CLIENT_ID

Required. Application (client) ID from step 1

MAIL_MCP_CACHE_PATH

Optional. Token cache location

3. Connect to Claude Desktop / Cowork

Edit ~/Library/Application Support/Claude/claude_desktop_config.json on macOS (or %APPDATA%\Claude\claude_desktop_config.json on Windows), reachable through Settings → Developer → Edit Config.

{
  "mcpServers": {
    "mail": {
      "command": "npx",
      "args": ["-y", "@rixtay/mail-mcp"],
      "env": {
        "MAIL_MCP_CLIENT_ID": "<your-client-id>"
      }
    }
  }
}

If Claude Desktop cannot find npx (it does not inherit your shell PATH), use absolute paths instead: "command": "/absolute/path/to/node", "args": ["/absolute/path/to/Mail-MCP/dist/index.js"].

Quit Claude Desktop completely and start it again. Logs: ~/Library/Logs/Claude/mcp-server-mail.log.

Cowork runs local MCP servers only in local sessions, not in cloud sessions.

4. Connect to Claude Code

claude mcp add --scope user --env MAIL_MCP_CLIENT_ID=<your-client-id> --transport stdio mail -- npx -y @rixtay/mail-mcp

5. Example prompts

  • "Summarise the senders in my inbox and flag the newsletters."

  • "Unsubscribe me from every newsletter I haven't opened in six months, then move their messages to Deleted Items."

  • "Create an Invoices folder and move everything from billing@vendor.com into it."

  • "Show me the latest email from my bank."

Typical flow: mail_senders_summary → the assistant proposes a list, you confirm → mail_unsubscribe(lastMessageId) per newsletter (when the answer is method: "browser", the assistant opens the URL in its browser and finishes there) → mail_bulk_by_sender(action: "delete").

Development

npm test          # vitest: header parsing, Graph retry/batch/pagination, service with a mocked Graph
npm run typecheck
npm run inspect   # MCP Inspector against dist/index.js

Layout:

src/index.ts          CLI entry point: `mail-mcp` serves stdio, `mail-mcp login` signs in
src/login.ts          interactive sign-in flow
src/server.ts         builds the McpServer and registers the tools
src/auth.ts           MSAL public client, file-based token cache
src/graph.ts          Graph client: bearer auth, 429/503 retry, pagination, $batch in chunks of 20
src/mail.ts           business logic (folders, search, sender summary, move/delete, unsubscribe cascade)
src/unsubscribe.ts    List-Unsubscribe / List-Unsubscribe-Post parsing, RFC 8058 one-click POST
src/tools/*.ts        tool definitions (zod v4 schemas, annotations)

Stack: @modelcontextprotocol/server v2, zod v4, @azure/msal-node v6, html-to-text.

Things worth knowing

  • Message ids change whenever a message changes folder. mail_move and mail_delete return the old → new id mapping.

  • A normal delete is a move to Deleted Items. Graph's own DELETE would drop the item into Recoverable Items, which is invisible in Outlook, so it is deliberately not used.

  • Microsoft throttles Outlook to 10,000 requests per 10 minutes per mailbox and 4 concurrent requests. Batches are serialised and retried on 429.

  • mail_search with query (full text) cannot be combined with the other filters (Graph limitation) and tops out at a few hundred results.

  • Whether an unsubscribe actually takes effect is up to the sender. One-click and mailto: send the request; the assistant's browser handles the rest.

  • The authority is login.microsoftonline.com/consumers. With common, refresh tokens for personal accounts are rejected after the first refresh.

Contributing

Bug reports, fixes and focused new tools are welcome: see CONTRIBUTING.md. Please never paste real email content, addresses or tokens in an issue. Found a way the server could leak mail or tokens, or act without being asked? Please report it privately, as described in SECURITY.md.

Release history: CHANGELOG.md.

License

MIT

Available Tools

9 tools
mail_bulk_by_senderBulk action by senderA
DestructiveIdempotent

Move or delete EVERY message from a sender (exact address) in a folder (Inbox by default). Use dryRun: true first to learn how many messages match. Deletion goes to Deleted Items unless permanent: true.

Inputs: from (required), action (required), dryRun, folder, +2 more. Returns: dryRun, failed, matched, succeeded

mail_create_folderCreate folderA
Idempotent

Create an Outlook folder (at the root or under a parent). Idempotent: if a folder with the same name already exists it is returned without error. Example: { name: "Newsletters" } or { name: "2025", parent: "Invoices" }.

Inputs: name (required), parent. Returns: folder, created

mail_deleteDelete messagesA
DestructiveIdempotent

Delete one or more messages (up to 500 ids). By default messages go to Deleted Items (recoverable with mail_search folder=deleteditems then mail_move; their id changes). permanent: true deletes irreversibly: only use it when the user explicitly asks for it.

Inputs: ids (required), permanent. Returns: moved, failed, succeeded

mail_get_messageRead a messageA
Read-onlyIdempotent

Return the full content of one message (body converted to text, recipients, attachment flag, web link) plus the unsubscribe options found in its headers (https, mailto, one-click). The body is truncated at 25,000 characters.

Inputs: id (required). Returns: to, body, message, webLink, +3 more

mail_list_foldersList foldersA
Read-onlyIdempotent

List every folder of the Outlook.com mailbox with its path, total message count and unread count. Call it before filing messages to learn which folders exist. Other tools accept a folder by display name ("Invoices"), by path ("Archive/2024"), by well-known name (inbox, deleteditems, junkemail, archive) or by id.

Inputs: no named parameters. Returns: folders

mail_moveMove messagesA
Idempotent

Move one or more messages (up to 500 ids) to a folder (name, path or id). Used for filing. NOTE: Outlook assigns a new id to every moved message; the moved result maps old id → new id. To move every message from a sender, prefer mail_bulk_by_sender.

Inputs: ids (required), folder (required). Returns: moved, failed, succeeded

mail_senders_summarySummary by senderA
Read-onlyIdempotent

KEY TOOL FOR TRIAGE. Scans a whole folder (Inbox by default) and aggregates messages by sender: count, unread, latest message, and for the top senders the available unsubscribe method (oneClick / https / mailto). Sorted by volume. The scan is cached for the session. Follow up with mail_unsubscribe(lastMessageId) and mail_bulk_by_sender(address).

Inputs: top, since, folder. Returns: scanned, senders, totalSenders

mail_unsubscribeUnsubscribeA

Try to unsubscribe from the mailing list of a message, in order: (1) RFC 8058 one-click HTTPS POST, (2) automatic email to the List-Unsubscribe mailto address, (3) otherwise returns method: "browser" with the URL to open in a browser to finish manually, (4) method: "none" when no header exists. Deletes nothing. Preferably pass the lastMessageId returned by mail_senders_summary.

Inputs: id (required). Returns: ok, url, from, detail, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a clearly distinct operation: folders, individual message retrieval, search, sender aggregation, move/delete by ID, bulk by sender, and unsubscribe. Overlap between search and sender summary is explicitly addressed by their descriptions and intended use cases.

    Naming Consistency4/5

    The mail_ prefix and snake_case style are consistent throughout, and most names use a verb_noun pattern. A few names like mail_senders_summary and mail_bulk_by_sender are noun/adjective phrases rather than clear verb-first names, which is a minor deviation.

    Tool Count5/5

    Nine tools is a well-scoped count for a mailbox management server. Each tool covers a meaningful operation without redundancy or unnecessary bloat.

    Completeness4/5

    The toolset covers the core mailbox triage workflow well: search, read, summarize, move, delete, bulk-manage, and unsubscribe. Missing operations like folder deletion/renaming, sending messages, or marking messages as read are notable but do not break the primary use case.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to manage Microsoft Outlook email and calendar through the Microsoft Graph API, including reading, sending, searching emails, and handling calendar events.
      43
      86 npm
      30
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables personal Outlook/Hotmail/Live account email management through Microsoft Graph, letting users list, search, read, and delete emails (with confirmation) via MCP.
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access a personal Outlook.com mailbox and calendar through Microsoft Graph, supporting email search, reading, drafting, sending, organization, and calendar event management.
      86 npm
      MIT