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)
helm install jmap-mcp oci://ghcr.io/mikluko/helm-charts/jmap-mcp \
--version 0.1.0 \
--set jmap.sessionURL="https://api.fastmail.com/jmap/session"
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
go install github.com/mikluko/jmap-mcp@latest
From source
git clone https://github.com/mikluko/jmap-mcp.git
cd jmap-mcp
make install
Usage
# stdio mode (default)
export JMAP_SESSION_URL=https://api.fastmail.com/jmap/session
export JMAP_AUTH_TOKEN=your-token
./jmap-mcp
# HTTP mode
./jmap-mcp -mode http -listen :8080
Build
make build # Build and push container image + Helm chart
make image # Build and push container image with ko
make package # Package and push Helm chart to OCI registry
make test # Run tests
make install # Install binary locally
References
- RFC 8620 — JMAP Core
- RFC 8621 — JMAP Mail
- RFC 9425 — JMAP Sieve Scripts
- MCP Specification