mcpmessage
Related Servers
Alternatives to mcpmessage
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to collaborate on the same project by sharing session briefs and reading each other's native transcripts, memories, and instructions in place, with zero-copy, across different agent tools.58 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables peer-to-peer communication between Claude Code sessions, allowing them to send messages, hand off tasks, and coordinate across worktrees without manual intervention.MIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple Claude Code sessions to communicate and share results automatically, with optional orchestration for hands-off workflow coordination.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceConnect any AI session to any other across models, machines, and people with one code. Enables relay, handoff, and verification of session contexts.37 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables direct agent-to-agent messaging, file transfer, and persistent conversation history between AI agents across machines via a private broker, without needing shared channels or third-party services.7 npm1MIT
- AlicenseAqualityDmaintenanceEnables Claude Code sessions to communicate with each other, allowing discovery, messaging, and synchronous queries across sessions.630 npmMIT
TDQS
Scored across 5 tools
Each tool targets a clearly distinct operation: listing chats, registering a chat, sending a message, reading an inbox, and fetching a thread. There is no functional overlap or ambiguity between them.
All tools share the mcpmessage_ prefix and use lowercase snake_case, but the pattern is not uniformly verb_noun: list_chats and register_chat follow it, while send, inbox, and thread are shorter. The names are still predictable and readable.
Five tools is well-scoped for a chat mailbox server. Each tool covers a necessary core operation and none feel redundant or excessive.
The toolset covers the full lifecycle of the domain: chat registration, discovery, sending with replies, reading with read-state tracking, and thread reconstruction. No significant gaps are apparent for the stated mailbox purpose.