Connection check
verified live · 20h ago
radmail-mcp
Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.
Tools
6
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http, stdio
Last checked
20h ago
Tools & capabilities
6 toolsRead from the running server on 20h ago.
draft_reply
guidancemessage_id*
Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it. Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.
list_commitments
Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when. Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.
list_right_now
Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed. Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.
search
limitquery*
Find a specific message by sender, subject, or content. Results come back most-relevant + newest first, and every hit says where it matched (from / subject / body) and why. On this… Find a specific message by sender, subject, or content. Results come back most-relevant + newest first, and every hit says where it matched (from / subject / body) and why. On this hosted sandbox it searches the built-in demo inbox; run the radmail-mcp package with RADMAIL_API_KEY set and the same tool searches your REAL ingested inbox read-only (with from / after / before filters) via the v1 search API.
triage_inbox
Rank a mailbox on two axes (importance x urgency) and return what needs a human now versus what can wait or is already handled — with each thread's open commitment (the promise you… Rank a mailbox on two axes (importance x urgency) and return what needs a human now versus what can wait or is already handled — with each thread's open commitment (the promise you owe or are owed, and whether it's overdue) surfaced inline, so the follow-through is visible on the very first call.
why_surfaced
message_id*