Productivity
radmail.ai
Manages email by prioritizing messages based on importance and urgency, and tracks commitments.
ENDPOINT 1
https://radmail.ai/api/mcp/sandbox
MCP server metadata
- Name
- radmail-sandbox
- Version
- 0.1.0
RadMail is pre-release. The engine is live in a test bed on two real businesses today; the commercial multi-tenant product is launch-gated. The MCP sandbox you connect to is real and runnable now (heuristic, in-memory, free, no credentials), but it is the sandbox engine — not the production multi-tenant engine. RadMail's MCP server exposes only the read/triage/draft tools above. There is no tool that auto-sends money, changes banking details, or makes first contact with a new party — those stay human-only, forever, as a defense against business-email-compromise (BEC) fraud. An agent literally cannot use RadMail to do the dangerous thing. Compliance is a shared responsibility. RadMail is a tool that supports your program, not a compliance guarantee, and it does not by itself make any organization compliant. For regulated tiers RadMail signs a BAA and processes on BAA-covered, audited infrastructure. RadMail is not HIPAA-certified, FedRAMP-authorized, or SOC 2-certified. Connect docs: https://radmail.ai/for-agents
Known tools 6
triage_inboxRank 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.
Inferred read-onlylist_right_nowReturn only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.
Inferred read-onlywhy_surfacedExplain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.
Potential side effectslist_commitmentsExtract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.radmail-sandbox]
url = "https://radmail.ai/api/mcp/sandbox"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"radmail-sandbox": {
"type": "http",
"url": "https://radmail.ai/api/mcp/sandbox"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: radmail-sandbox
Remote MCP URL: https://radmail.ai/api/mcp/sandbox
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"radmail-sandbox": {
"url": "https://radmail.ai/api/mcp/sandbox"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"radmail-sandbox": {
"type": "http",
"url": "https://radmail.ai/api/mcp/sandbox"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "radmail-sandbox",
"transport": "streamable-http",
"url": "https://radmail.ai/api/mcp/sandbox"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.