An MCP server that gives AI agents a real email client with full read/write access to configured mailboxes (IMAP/SMTP and Microsoft Graph).
mailbridge demonstrates strong definition quality across 15 email tools. All tools have clear action-verb names (mail_*), comprehensive descriptions (avg 180 chars), and complete input schemas with types and descriptions for all parameters. Rich parameter constraints (enums for folder roles, numeric bounds on limits) guide LLM behavior effectively. Output schemas are documented through descriptions. Error handling is present but could be more specific. Confirmation-gate patterns are correctly applied to destructive operations (send_message, delete). A few improvements remain: some descriptions could be more prescriptive about when/why to use each tool, and output field documentation could be more formal.
Compose a new message (unsent). Returns a draft id to use with mail_send_message or mail_discard_draft. Optionally includes attachments as base64.
Permanently delete one or more messages (they go to Trash first on most providers, then to permanent deletion). Requires confirm=true after showing the user exactly what will be deleted.
High-level summary of inbox activity: unread counts by folder, recently received messages, and flagged messages. A quick alternative to many individual searches.
Delete an unsent draft (from mail_compose, mail_reply, or mail_forward).
Flag (star) or unflag one or more messages.
Start a forward of a message. Returns a draft id for use with mail_send_message or mail_discard_draft.
Download an attachment. Streams large files (the endpoint reads from the backend without buffering the whole attachment into memory).
Output schemas not formally documented in function signatures or schema definitions. mail_get_message, mail_search, mail_digest return complex structured data (headers, body, attachment list, unread counts) but these are only described in text, not as explicit JSON Schema output schemas.
Parameter interdependencies not fully documented. mail_search's 'accounts' parameter behavior when omitted ('search every configured account') is clear, but there is no explicit guidance on mutual exclusivity (e.g., can both 'query' and 'sender' be used together? Are they OR'd or AND'd?). Similar for folder role aliases vs real folder names.
Error handling guidance incomplete. Tools document risk levels (READ_ONLY, WRITE, DESTRUCTIVE) but do not provide recovery hints in descriptions. E.g., mail_send_message with confirm=false should explain what error to expect and how to retry; mail_move with an invalid folder name should guide the agent to call mail_list_folders first.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Fetch a message in full: headers, body (plain text and/or HTML), and attachment list. Bodies over max_body_chars are truncated with a hint to call again with a larger limit.
List every configured mailbox with its type and connection status. Call this first when you do not already know which accounts exist.
List the folders in a mailbox, with unread and total counts where the provider reports them. Use this to find the exact name of a folder before moving mail.
Mark one or more messages as read or unread.
Move one or more messages to a folder. Folder names are case-sensitive; use mail_list_folders to find the exact names.
Start a reply to a message. Returns a draft id for use with mail_send_message or mail_discard_draft.
Search mail across one or all accounts and return message summaries (no bodies). Combine filters freely: free-text `query`, `sender`, `subject`, date range, unread-only, attachments-only. Results are newest first. Use the returned `id` with mail_get_message to read a message in full.
Send a composed message (from mail_compose or a reply/forward draft). Requires confirm=true after showing the user exactly what will be sent.
Pagination not explicit for mail_search. Description mentions 'limit' (max 200 per account) and 'Results are newest first', but no mention of offset, cursor, or how to retrieve the next page. Large result sets could exhaust context windows.
Confirmation-gate pattern incomplete. mail_send_message and mail_delete require confirm=true, but the descriptions say 'Always show the user what you are about to send/delete before setting this', there is no dry-run or preview mechanism. An agent could call with draft in memory but misremember what's in it.