Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@jmap-mcp List my mailboxes"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server exposing JMAP email and Sieve script operations as tools.
Built with the Go MCP SDK (go-sdk) and go-jmap library.
Tools map closely to JMAP methods. Email mutation tools provide structured convenience wrappers over Email/set patches.
Tool | JMAP Method | Description |
|
| Get mailboxes by ID, or list all |
|
| Create, update, or destroy mailboxes |
Tool | JMAP Method | Description |
|
| Search emails with filters, returns IDs and total count |
|
| Get full content of emails by ID |
|
| Create a new email draft in the Drafts mailbox |
|
| Move emails to a different mailbox |
|
| Set or remove flags (seen, flagged, answered, draft) |
|
| Delete emails (move to Trash or permanently destroy) |
| Blob download | Signed URL streaming an attachment, expires in 30 s (HTTP mode only) |
Tool | JMAP Method | Description |
|
| List sender identities (email addresses) |
Tool | JMAP Method | Description |
|
| Submit a draft for delivery (requires |
Tool | JMAP Method | Description |
|
| List all scripts, or get one with full content (requires |
|
| Create, update, or destroy Sieve scripts (requires |
|
| Validate a Sieve script without saving (requires |
Related MCP server: mail-mcp
Env var | Required | Description |
| always | JMAP session endpoint (e.g. |
| stdio mode | Bearer token for JMAP authentication |
| no | Secret sealing signed attachment URLs; set for multi-replica deployments (default: random per-process key) |
Flag | Default | Description |
|
| Server mode: |
|
| HTTP listen address (http mode only) |
|
| Enable the |
|
| Enable Sieve script tools (off by default, requires JMAP server support) |
| derived | External base URL for signed attachment links; default derives from the request ( |
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.
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.
go install github.com/mikluko/jmap-mcp@latestgit clone https://github.com/mikluko/jmap-mcp.git
cd jmap-mcp
make install# 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 :8080make 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 locallyThis server cannot be deployed
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Your agent needs a mailbox of its own — to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** • "Create an inbox for this agent and tell me its address." • "Read the new messages in this thread and draft a reply." • "Send this message with the attachment and wait for the response." • "Search this inbox for everything from that domain." • "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries — reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
