radmail-mcp
Server Details
Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- dougsureel-tech/radmail-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 6 of 6 tools scored.
Each tool serves a distinct purpose: drafting replies, listing commitments, showing urgent messages, searching, triaging inbox, and explaining rankings. No two tools overlap in functionality.
All tool names use a consistent verb_noun pattern (draft_reply, list_commitments, list_right_now, search, triage_inbox, why_surfaced) in snake_case, making the set predictable.
With 6 tools covering essential email management tasks (search, triage, commitments, drafts, explanations), the count is well-scoped without being excessive or sparse.
The set lacks a send operation (draft_reply explicitly cannot send), no full inbox listing (only a 'right now' lane), and no archive/delete functionality, creating notable gaps for a mail assistant.
Available Tools
6 toolsdraft_replyInspect
Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.
| Name | Required | Description | Default |
|---|---|---|---|
| guidance | No | Optional steer for the draft. Never sent — review-only. | |
| message_id | Yes | An id from triage_inbox to draft a reply for. |
list_commitmentsInspect
Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
list_right_nowInspect
Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
searchInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max hits to return (default 10). | |
| query | Yes | Words to find, matched against from / subject / body. Every word must appear somewhere in a message. |
triage_inboxInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
why_surfacedInspect
Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | An id from triage_inbox, e.g. m_001. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!