Unofficial MCP server for Fastmail API integration (not affiliated with or endorsed by Fastmail)
Four tools with clear verb-noun naming and reasonable descriptions (avg 150 chars). All have input schemas with type definitions. However, parameter descriptions are sparse or missing in several tools, and output schemas are not documented. list_mailboxes and list_emails lack pagination metadata (total count, next_cursor). Error handling is minimal, no recovery guidance or actionable error messages visible in the tool definitions. The fork architecture (src/fork/index.ts) suggests additional tools exist but are not shown in the sample, making full assessment impossible.
Create a new mailbox (folder). Returns the new mailbox ID. The caller is responsible for validating the name is appropriate (length, character set, parent-folder allow-list) before calling — JMAP itself only enforces uniqueness within a parent.
Look up a single mailbox by its full path from root (e.g. "Folder/Subfolder/Leaf"). Returns the mailbox ID and minimal metadata, or throws "Mailbox not found" if no exact match. The path separator is "/"; folder names containing a literal "/" are not supported.
List emails from a mailbox. When the server reports a total match count, results are wrapped in a {"total", "items"} JSON envelope; otherwise a bare JSON array is returned.
List mailboxes in the Fastmail account. By default returns all mailboxes with full metadata; on accounts with hundreds of mailboxes the full result can exceed the MCP tool result window. Use `properties: ["id","name","parentId"]` for a slim view, and/or `parentId` to filter to one level of children.
Output schemas not documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., mailbox IDs for chaining). list_mailboxes and list_emails return JSON but structure is not specified.
Pagination incomplete. list_mailboxes and list_emails accept limit but do not document total count, next_cursor, or offset. Large result sets will blow context window without proper pagination metadata.
Parameter descriptions incomplete. create_mailbox 'parentId' description is minimal; list_emails 'mailboxId' is marked optional but no guidance on default behavior when omitted.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Error handling not visible. No recovery guidance in tool descriptions (e.g., 'Mailbox not found' error in get_mailbox_by_name has no suggestion for next steps). Agents cannot self-correct on failures.
Tool definitions inferred from fork architecture. src/fork/index.ts references mailboxes.ts, emails.ts, bulk.ts, account.ts, sending.ts, ops.ts, search.ts but source code not provided. Cannot verify schemas, descriptions, or error handling for ~30+ additional tools.