
JMAP Email
io.github.miklukoPublished by GitHub account miklukov0.10.0Updated Oct 24, 2026
Email management via JMAP — mailboxes, messages, identities, and Sieve scripts
Overview
A local MCP server that connects an assistant to a JMAP email account to browse mailboxes, search and read messages, and manage flags, moves and drafts.
- What you can do
- List, create, update and delete mailboxes, and list sender identities available for sending messages. Search emails with filters and retrieve full message content by ID. Create drafts, move messages between mailboxes, set or clear flags such as seen, flagged, answered and draft, and delete messages to Trash or permanently. Optionally submit drafts for delivery and manage Sieve filter scripts, including validating a script without saving it.
- When to use it
- Useful when an assistant should work with a JMAP-based mailbox, such as Fastmail, for triage, search, drafting replies or organizing folders. Sending and Sieve script tools are off by default and must be enabled deliberately.
- Requirements
- Runs as a local process (Go binary or container image) over stdio. Requires the JMAP session endpoint URL in JMAP_SESSION_URL and a bearer token in JMAP_AUTH_TOKEN. Network access to the JMAP server. Sending requires the -enable-send flag; Sieve tools require -enable-sieve and server support.
Installation
In SourceWeft
- Open JMAP Email in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
jmap-mcp
MCP server exposing JMAP email and Sieve script operations as tools.
Built with the Go MCP SDK (go-sdk) and go-jmap library.
Tools
Tools map closely to JMAP methods. Email mutation tools provide structured convenience wrappers over Email/set patches.
Mailbox (RFC 8621)
Email (RFC 8621)
Identity
Submission (feature-gated)
Sieve Scripts (RFC 9661, feature-gated)
Configuration
In HTTP mode, the token can be passed per-request via Authorization: Bearer <token> header or jmap_token query parameter (query parameter takes precedence).
In HTTP mode, email_attachment_url returns a link served from /attachments/ that expires 30 seconds after issuance. The link is an AES-GCM sealed capability: it embeds the JMAP token, account, and blob IDs, so the endpoint streams the attachment from the JMAP server without any additional authentication and stores nothing on disk.
Installation
Kubernetes (Helm)
In HTTP mode, JMAP auth tokens are passed per-request via Authorization: Bearer header or ?jmap_token= query parameter — no static tokens are stored in the cluster.
Binary
From source
Usage
Build
References
- RFC 8620 — JMAP Core
- RFC 8621 — JMAP Mail
- RFC 9425 — JMAP Sieve Scripts
- MCP Specification
Source: README.md at commit c0bcbf9
Tools
0Version history
1- v0.10.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.