JMAP Email MCP Server

Email management via JMAP — mailboxes, messages, identities, and Sieve scripts. That is what the jmap email mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

MCP server exposing JMAP email and Sieve script operations as tools.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 2 tools. What each one is for:

• Identity — The Identity tool exposed by this server
• Binary — The Binary tool exposed by this server

What it needs from you

Configuration is passed through the environment: JMAP_SESSION_URL, JMAP_AUTH_TOKEN, ATTACHMENT_URL_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. JMAP Email's toolset — Identity, Binary — is a fair guide to whether it matches your workflow. It is maintained by mikluko; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against JMAP Email's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.