Mail-MCP

io.github.Rixtayzv0.1.2Updated Oct 1, 2026

Personal Outlook.com / Hotmail inbox: read, search, file, delete, unsubscribe via Microsoft Graph.

Overview

AI-generated overview

Lets an assistant read, search, file, delete and unsubscribe mail in a personal Outlook.com or Hotmail mailbox via Microsoft Graph.

What it does
Nine mail_ tools cover folder listing and creation, message listing and search by sender, date, unread status or full text, full message retrieval with detected unsubscribe options, per-sender aggregation across a folder, moving up to 500 messages, deleting to Deleted Items or permanently, bulk move/delete by sender with a dry-run option, and unsubscribe via RFC 8058 one-click POST, mailto: or a URL. Deletion defaults to Deleted Items and permanent deletion needs an explicit flag. There is no generic send tool; Mail.Send is used only for mailto: unsubscribe requests.
When to use it
Useful for cleaning up an overflowing personal Outlook.com, Hotmail, Live or MSN inbox with an assistant: summarising senders, flagging newsletters, unsubscribing, and filing or deleting messages in bulk.
Requirements
Runs locally over stdio via npx from the npm package @rixtay/mail-mcp; needs Node.js 22 or newer, a personal Microsoft account, and a free Microsoft Entra app registration. MAIL_MCP_CLIENT_ID is required; MAIL_MCP_CACHE_PATH is optional. A one-time login command opens the browser and stores a token cache; tokens refresh for about 90 rolling days.
Before you install
The app registration requests delegated Mail.ReadWrite, Mail.Send, User.Read and offline_access, so the assistant can read, move and delete mail and send unsubscribe requests. Deletion is a move to Deleted Items unless permanent is set; bulk actions support dryRun. The token cache is stored on disk and should be protected. Unsubscribe effectiveness depends on the sender, and a browser method leaves the request to be finished manually.

Installation

In SourceWeft

  1. Open Mail-MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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_:

ToolWhat it does
mail_list_foldersFolder tree with total / unread counts
mail_create_folderCreate a folder (idempotent)
mail_searchList / search messages (sender, date range, unread, full text), paginated
mail_get_messageFull content of one message + detected unsubscribe options
mail_senders_summaryAggregate a whole folder by sender: volume, latest message, available unsubscribe method
mail_moveMove up to 500 messages to a folder
mail_deleteMove to Deleted Items by default, permanent: true to purge
mail_bulk_by_senderMove or delete every message from one sender (dryRun supported)
mail_unsubscribeRFC 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]

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):

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

Or from a clone:

bash
git clone https://github.com/Rixtayz/Mail-MCP.gitcd Mail-MCPnpm install && npm run buildMAIL_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 variablePurpose
MAIL_MCP_CLIENT_IDRequired. Application (client) ID from step 1
MAIL_MCP_CACHE_PATHOptional. 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.

json
{  "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

bash
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 [email protected] 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

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

Layout:

src/index.ts          CLI entry point: `mail-mcp` serves stdio, `mail-mcp login` signs insrc/login.ts          interactive sign-in flowsrc/server.ts         builds the McpServer and registers the toolssrc/auth.ts           MSAL public client, file-based token cachesrc/graph.ts          Graph client: bearer auth, 429/503 retry, pagination, $batch in chunks of 20src/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 POSTsrc/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

Source: README.md at commit 8b8f760

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.1.2LatestOct 1, 2026