radmail-mcp

Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
97%
Integridad del esquema
65%
Calidad de los nombres
90%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~559Tokens (definiciones de herramientas)
~469 BTamaño de respuesta típico
Impacto mínimo en la atención (0.44% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "radmail-mcp": {
      "command": "npx",
      "args": [
        "radmail-mcp"
      ]
    }
  }
}

Paquetes ejecutables

npmradmail-mcp0.5.0stdio

Puntos de conexión remotos

https://radmail.ai/api/mcp/sandboxstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (6)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
⚪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 owe or are owed, and whether it's overdue) surfaced inline, so the follow-through is visible on the very first call.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢list_right_now

Return only the 'Right Now' lane — the most recent and most important messages that genuinely can't be missed.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟢why_surfaced(message_id)

Explain in plain English why a given message was surfaced — the signals (sender, urgency, commitment) behind its rank.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "An id from triage_inbox, e.g. m_001."
    }
  },
  "required": [
    "message_id"
  ],
  "additionalProperties": false
}
🟢list_commitments

Extract the open commitments in the correspondence, both owed by you and owed to you, with who and by-when.

Esquema de entrada

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡draft_reply(message_id, guidance)

Draft a reply for a thread. It returns text for a human to review — it does not and cannot send it.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "message_id": {
      "type": "string",
      "description": "An id from triage_inbox to draft a reply for."
    },
    "guidance": {
      "type": "string",
      "description": "Optional steer for the draft. Never sent — review-only."
    }
  },
  "required": [
    "message_id"
  ],
  "additionalProperties": false
}
🟡search(query, limit)

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.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Words to find, matched against from / subject / body. Every word must appear somewhere in a message."
    },
    "limit": {
      "type": "number",
      "description": "Max hits to return (default 10)."
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas