Multi-account email management MCP server with IMAP/SMTP support
The MCP Mail Manager server defines 7 tools with mostly complete schemas and reasonable descriptions. However, there are significant gaps in error handling, output schema documentation, and parameter constraint specificity. Naming follows verb_noun conventions well, but descriptions lack actionable context for LLM selection. The server does NOT expose secrets as parameters (credentials encrypted locally), which is a security plus. However, the tool descriptions are generic and would benefit from explicit guidance on when to use each tool vs. alternatives. Output schemas are inferred from code but not formally documented in tool definitions.
Add a new email account. Auto-detects provider from email address.
Get full email thread/conversation by message ID or thread ID
List all configured email accounts
List emails from an account's inbox. Returns subject, from, date, and preview.
Remove an email account from the configuration
Search emails by query, sender, date range, or other criteria
Send an email from a configured account
Output schemas not documented anywhere in tool definitions. LLMs cannot predict what fields are returned, forcing trial-and-error or multi-turn discovery.
Error handling guidance is absent. No indication of what errors each tool can return, whether they are retryable, or what the LLM should do next. E.g., add_email_account may fail if test_connection=true and credentials are wrong, but no recovery guidance.
Descriptions lack LLM-optimized context for tool selection. Generic descriptions like 'List all configured email accounts' don't explain when to call this vs. other tools or what prerequisites exist. Should state: 'Call this first to discover account IDs, required for all other email tools.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Destructive operation (send_email, remove_email_account) descriptions do not explicitly state irreversibility. send_email should warn 'This sends the email immediately, use draft=true to compose first.' remove_email_account should warn 'This permanently deletes the account and all cached emails.'
Parameter constraints not fully specified. imap_port and smtp_port default to 993 and 587 but descriptions don't state valid ranges. Enum values for provider are good, but 'custom' provider requires additional params (imap_host, smtp_host), this conditional dependency is not documented.
Potential naming ambiguity: search_emails vs list_emails both fetch emails. search_emails description says 'searches subject and body' but list_emails can filter by unread_only and folder. When would an LLM choose one over the other? Add explicit guidance like: 'Use list_emails to browse a folder; use search_emails for keyword matching across folders.'
get_email_thread accepts 'message_id or thread_id' per description but schema only shows message_id parameter. Either schema is incomplete or description is inaccurate.
No pagination guidance. list_emails has limit=20 default; search_emails has limit=20 default. But are there more results available? Should the tool return a next_cursor or total_count? Without pagination metadata, LLMs cannot efficiently retrieve large result sets.