Mail bridge for Claude Code via email - enables remote management and communication through email with support for presence, team management, and email-based permission requests
Claude Mail Bridge has significant definition quality issues. While 7 of 8 tools have detailed descriptions and well-structured schemas, the tools exhibit critical naming and composition problems. Most critically, mail_user_and_wait and mail_teammates violate the single-responsibility principle by combining email sending with polling/waiting logic. The tool names use 'and' which signals multiple concerns. Additionally, several tools (get_presence, set_presence, set_dnd_mode, add_to_teammates, remove_from_teammates, get_teammates_list) require undocumented preconditions (_init_skill_invoked, _team_rules_skill_invoked boolean flags) that indicate a broken tool composition pattern, these should be handled via server initialization, not exposed as tool parameters. The use of internal-only boolean parameters (_ prefix) in public tool schemas is a red flag for poor API design. Error handling is minimal with no recovery guidance. Parameters have good descriptions but lack comprehensive validation/range documentation. Output schemas are not visible in the provided source, only some input schemas. The server has 8 tools where 3-4 could be consolidated, and the precondition pattern violates the composition principle.
Add teammate to team members list with optional alias. Requires /claude-mail-bridge-init and /claude-mail-bridge-team_rules to be invoked first.
Get user's current online status. Returns 'online' or 'away'. Requires /claude-mail-bridge-init to be invoked first.
Get current team members list with their email addresses and aliases. Requires /claude-mail-bridge-init and /claude-mail-bridge-team_rules to be invoked first.
Send email to teammates with optional wait for reply. Formats email with machine name, tmux session info, and sender alias for team communication.
Send email to user and wait for reply with adaptive polling. Validates attachments first, generates ticket ID, formats email with session info, sends via configured email, then polls for replies with fast then slow polling intervals.
Remove teammate from team members list by email or alias. Requires /claude-mail-bridge-init and /claude-mail-bridge-team_rules to be invoked first.
Tool names contain 'and' (mail_user_and_wait, mail_teammates) indicating multiple responsibilities bundled into single tools. mail_user_and_wait sends email AND polls for reply. mail_teammates sends email AND optionally waits. These should be split: send_email_to_user, get_email_reply, send_email_to_teammates.
Internal-only boolean parameters exposed in public tool schemas (_init_skill_invoked, _team_rules_skill_invoked). These are implementation details that should be handled via server initialization or context, not as required tool inputs. This breaks the tool interface contract and forces agents to track internal state.
Preconditions documented as text in descriptions ('Requires /claude-mail-bridge-init to be invoked first') rather than handled via tool composition or server state. This forces agents to understand and track multi-step initialization order. Should be replaced with proper stateless request handling (per MCP spec) or precondition validation inside tools.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 38 | - | v1 |
Set do-not-disturb mode for current tmux session. Modes: 'off' (disable), 'on' (permanent), 'fixed' (timed with duration_minutes), 'auto' (follow presence). Requires /claude-mail-bridge-init to be invoked first.
Set user's online status to 'online' or 'away'. Requires /claude-mail-bridge-init to be invoked first.
No visible output schemas or return type documentation in provided source code. Tools document input parameters well but do not document what data structures are returned. This prevents agents from chaining tools and forces them to guess field names and types.
Minimal error handling visible. No recovery guidance, error classification, or actionable next steps documented. If attachment validation fails, email sending fails, or polling times out, agents have no clear recovery path.
mail_user_and_wait has timeout_minutes=120 default (2 hours) without explicit documentation of what happens when timeout is exceeded. Does the tool return partial results, an error, or hang? Agents need clear timeout semantics.
attachments parameter accepts file paths as strings but validation is mentioned in code (_validate_attachments) with no explicit description of what formats are valid, size limits, or what happens with invalid attachments.
set_dnd_mode requires duration_minutes only when mode='fixed' but this conditional requirement is not formally expressed in schema. Agents cannot automatically validate whether they must provide this parameter.