A
licenseNot graded
qualityC
maintenanceEnables local discovery, reading, and messaging between running Codex and Claude Code sessions through MCP.
247 npm
MIT
tincan
OfficialRelated Servers
Alternatives to tincan
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables multiple coding agents (Claude Code, Codex, Cursor) to discover each other's sessions, search transcripts, ask questions, and handoff tasks through a shared MCP server.54 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code sessions to discover each other as named peers and exchange instant messages across directories, machines, and Docker containers, with durable delivery for offline sessions.MIT
- AlicenseAqualityAmaintenanceEnables real-time cross-machine communication for Claude Code agents using a shared MCP relay server.1398 PyPI12MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code instances to discover each other and exchange messages instantly via a local broker and channel protocol. Supports scoped peer discovery, reliable ack-based delivery, and cross-platform operation.3 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables multiple Claude Code sessions to communicate and coordinate through broadcast and peer-to-peer messaging.2 npm1MIT
TDQS
A4.3/5.0
Scored across 3 tools
Disambiguation5/5
Peers, send_peer, and message_log each target a distinct operation: discovering sessions, sending a message, and reading the message log. There is no overlap or ambiguity between them.
Naming Consistency3/5
Naming is readable and lowercase with underscores, but the conventions are mixed: 'peers' and 'message_log' are nouns, while 'send_peer' is verb_noun. A more uniform pattern like list_peers, send_peer, get_message_log would be clearer.
Tool Count5/5
Three tools is well-scoped for the stated purpose of peer messaging. Each tool earns its place and the set is neither bloated nor too thin.
Completeness5/5
The tool set covers the full lifecycle of the domain: discover available peers, send a message, and inspect the log to verify delivery status. There are no obvious dead ends for the intended workflow.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive