A
licenseNot graded
qualityC
maintenanceEnables local discovery, reading, and messaging between running Codex and Claude Code sessions through MCP.
117 npm
MIT
tincan
OfficialRelated Servers
Alternatives to tincan
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents on the same machine to discover each other as named peers and exchange messages across sessions, bridging MCP-based clients and Claude Code without a daemon.23 PyPIMIT
- 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.1383 PyPI13MIT
- 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
TDQS
A4.6/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct role: peers discovers sessions, send_peer sends messages, message_log reads the audit trail, and reregister fixes stale registration. Descriptions explicitly draw boundaries (e.g., call peers before send_peer; reregister only when a peer reports unreachability), leaving no overlap.
Naming Consistency3/5
All names use snake_case and are readable, but the pattern is mixed: peers and message_log are nouns, reregister is a bare verb, and send_peer is verb_noun. There is no single predictable convention across the set.
Tool Count5/5
Four tools is well-scoped for an inter-agent messaging server: discovery, sending, log auditing, and registration repair. Each tool earns its place with no redundant or missing basic capability.
Completeness5/5
The surface covers the full tool-accessible lifecycle: see live peers, send messages (to one or many), inspect the log with filtering and integrity checks, and repair the session's registration. Inbound message handling is external to the tool set, so no core operations are missing.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive