About this integration
Multi-account email MCP server for Gmail, IMAP, and JMAP: search, send, drafts, labels.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- unknown
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.9.2
- Package
- mailbox-mcp
- Last compatibility test
- Not independently tested
Connect your agent
mailbox-mcpPublisher README and npm manifest reviewed; package and mail providers were not executed. Gmail uses one-time browser OAuth with locally stored tokens, while IMAP/JMAP use stored provider credentials, so authentication and setup remain mixed rather than being reduced to one native mode. Runtime eligibility begins only after an account is configured; provider consent, sender identity, and message effects remain operator responsibilities.
Capabilities: Search and read email, Send, reply to, and forward email, Manage drafts and message state, Work across multiple mail accounts
Connected profiles
Additional details
io.github.jgalea/mailbox-mcp
Source ↗ · Checked 2026-09-170.9.2
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17mailbox-mcp
Source ↗ · Checked 2026-09-190.10.0
Source ↗ · Checked 2026-09-19The publisher documents launching the package directly from npm through a persistent MCP client configuration after account setup.
Source ↗ · Checked 2026-09-19Gmail uses a browser OAuth flow with locally stored tokens; the same artifact separately supports credential-based IMAP/JMAP accounts, so the native classification is unknown/mixed.
Source ↗ · Checked 2026-09-19The documented local connection invokes mailbox-mcp with npx over the MCP client's stdio channel.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19