Email management via JMAP — mailboxes, messages, identities, and Sieve scripts
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
{
"JMAP_SESSION_URL": "YOUR_VALUE_HERE",
"JMAP_AUTH_TOKEN": "YOUR_SECRET_VALUE"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-mikluko-jmap-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-io-github-mikluko-jmap-mcp"
],
"env": {
"JMAP_SESSION_URL": "YOUR_VALUE_HERE",
"JMAP_AUTH_TOKEN": "YOUR_SECRET_VALUE"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
JMAP Email is an MCP server for Email management via JMAP — mailboxes, messages, identities, and Sieve scripts. It supports STDIO transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
JMAP Email uses STDIO transport. Use the package or command config in Install.
JMAP Email inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
JMAP Email is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/mikluko/jmap-mcp:0.9.0stdio | oci | Not captured | Env: JMAP_SESSION_URL required Env: JMAP_AUTH_TOKEN required secret |