{"id":"wyattjoh-jmap-mcp","name":"jmap-mcp","af_score":61.8,"security_score":64.8,"reliability_score":32.5,"what_it_does":"Provides a Model Context Protocol (MCP) server exposing tools to interact with JMAP-compliant email servers for email search/retrieval, mailbox listing, message state changes (seen/flagged), moving/deleting messages, and sending/replying to emails. It is implemented in Deno using the @htunnicliff/jmap-jam client library and uses Zod for input validation.","best_when":"You want an MCP-native interface for email tasks against a JMAP server and can run a Deno stdio MCP server in your agent environment.","avoid_when":"You cannot securely manage bearer tokens for the JMAP server or you need explicit, documented rate-limit behavior and retry/idempotency guarantees.","last_evaluated":"2026-03-30T13:39:45.122459+00:00","has_mcp":true,"has_api":false,"auth_methods":["JMAP bearer token (JMAP_BEARER_TOKEN)"],"has_free_tier":false,"known_gotchas":["Write actions like send_email and reply_to_email are likely non-idempotent; agents should avoid automatic retries without safeguards.","Bearer token and session URL must be passed via environment variables; missing/expired tokens will cause failures (retry strategy not documented).","Tool batch sizes are capped in the parameter descriptions (e.g., send/retrieve IDs limits), so agents must chunk requests."],"error_quality":0.0}