InterAgentMail
Related Servers
Alternatives to InterAgentMail
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents such as Codex and Claude Code to exchange durable, locally stored messages through shared MCP tools for listing enrolled recipients, sending and replying to messages, reading pending inbox items, acknowledging receipt, and checking message status. Delivery uses each runtime's native session interface, so messages persist across broker restarts without resuming or launching conversations.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents on the same machine to exchange asynchronous messages as plain Markdown files, with optional wake-up notifications per agent.220 npm1AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables local agent-to-agent messaging between Claude Code sessions via file-based channels, with a registry, MCP tools and CLI for sending, reading, and tracking messages.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables file-based agent-to-agent communication between Claude Code instances on the same machine, using MCP channels and plain JSON files.7 npm14MIT
- AlicenseNot gradedqualityBmaintenanceEnables local messaging between Claude Code and Codex agents with durable delivery, peer discovery, and reply tracking.MIT
- AlicenseNot gradedqualityAmaintenanceProvides asynchronous messaging infrastructure for AI agents, enabling them to get permanent addresses and send/receive encrypted messages via MCP tools.1MIT
TDQS
Scored across 23 tools
Most tools map to a distinct resource+action, but timer_clear vs timer_cancel and the timer_set_team/timer_set_for/timer_set trio could cause selection hesitation. Descriptions generally resolve the ambiguity.
All tools share the iam_ prefix and snake_case convention, and most follow verb_noun. A few noun-style names like iam_inbox and compound names like iam_timer_set_for break the strict pattern slightly.
23 tools is on the heavy side for an MCP server, though each domain cluster (mail, chat, timers, team) is internally coherent. The count feels manageable but exceeds the typical well-scoped range.
Mail, chat, timer, and team management all have core lifecycle coverage: send/read/reply/archive, join/post/tail/leave, set/list/cancel/snooze, and add/remove member. Minor gaps like team listing or message search exist but are not blocking.