Radmail MCP

What radmail-mcp MCP server does

The radmail-mcp MCP server exposes an email workflow through Model Context Protocol tools. It helps an agent identify messages that need immediate attention, find open promises and their due windows, search for a relevant message, explain why a message was prioritized, and prepare a reply for an eligible commitment.

Its main workflow is built around triage. triage_inbox returns the Right Now lane, open commitments, and hard stops in one batch. list_right_now narrows the result to recent and important messages and includes an explanation for each surfaced item. triage provides the same kind of scoring for one message.

The server also separates automation from human review. draft_reply can prepare a response intended to discharge a commitment, but it does not draft for hard-stopped cases. Money, banking, and first-contact situations stay human-only according to the supplied tool description.

How it works

In sandbox use, several tools accept a messages input. The server can use that data to score messages, extract commitments, search content, and identify hard-stop flags without connecting to a live inbox. provision_sandbox explicitly creates a free sandbox tenant.

Connected mode is read-only and uses RADMAIL_API_KEY. In that mode, the agent can omit the sandbox message data for the real Right Now lane, tracked commitments, and inbox search. read_email can fetch one full message by ID, including headers and textBody; the returned body is marked as taint-tagged content.

The explanation path is explicit rather than implicit. why_surfaced describes in plain English the signals contributing to a message's importance and urgency. This lets an agent or developer inspect the reason behind a ranking instead of treating triage as an unexplained score.

Tools and capabilities

The radmail-mcp MCP server provides these capabilities:

• Batch triage through triage_inbox.
• Right Now prioritization through list_right_now.
• Per-message scoring with triage.
• Plain-language prioritization explanations with why_surfaced.
• Open commitment extraction and due-window listing with list_commitments.
• Sender, subject, and content search with search, ordered by relevance and recency.
• Full-message retrieval in connected mode through read_email.
• Commitment-oriented response drafting through draft_reply.
• Sandbox creation with provision_sandbox.
• Feedback submission through report_need.
• Work-pattern information through radmail_learning_insights.

Setup and configuration

Use the sandbox by passing message data to the tools that support it. This allows evaluation of triage, search, commitment extraction, and hard-stop handling without a live inbox connection. Call provision_sandbox when an explicit sandbox tenant is needed.

For connected use, configure RADMAIL_API_KEY and omit messages where the tool supports real-inbox operation. The supplied material describes connected access as read-only, so the server is suited to inspection and drafting workflows rather than sending, editing, or deleting email. The available description does not specify an installation command, package manager, transport, or client configuration format.

Limitations and notes

The server does not provide a send-email tool in the listed capabilities. Drafting a reply is not the same as dispatching it. Hard-stopped messages must remain with a human when they involve money, banking, or first contact.

Live inbox features depend on RADMAIL_API_KEY; sandbox operation uses supplied messages instead. Full email retrieval is limited to connected mode. Message bodies returned by read_email are taint-tagged, which should be considered when an agent processes their contents.

The available material does not document supported MCP clients, licensing, installation steps, or the exact ranking algorithm. report_need and radmail_learning_insights are listed as tools, but their input and output schemas are not specified here.