agent-bridge
Related Servers
Alternatives to agent-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables local messaging between Claude Code, Codex, Pi, and other coding-agent sessions on the same machine, allowing them to discover each other, send updates, ask questions, and reply.819 npm3AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceLets local Claude Code and Codex sessions discover each other, read recent messages, and send questions between live or closed sessions.MIT
- AlicenseNot gradedqualityBmaintenanceLets independent Claude Code and Codex sessions running in different tools and projects discover each other and exchange questions, coordination messages, and replies that arrive back in the conversation that asked. Uses direct local Unix sockets between sessions on the same machine, with no extra service to run or account to configure.43 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local messaging between Claude Code and Codex agents with durable delivery, peer discovery, and reply tracking.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables local discovery, reading, and messaging between running Codex and Claude Code sessions through MCP.216 npmMIT
TDQS
Scored across 4 tools
The four tools have distinct purposes: listing sessions, sending messages, reading journal records for a recipient, and checking status of one message ID. However, read_messages and message_status both involve reading message-related records, which could cause slight confusion despite the descriptions clarifying the difference.
Three tools follow a consistent verb_noun pattern (list_sessions, send_message, read_messages), but message_status breaks the pattern by starting with a noun. This is a minor deviation and the overall naming remains readable and predictable.
Four tools is a well-scoped set for a local agent bridge, covering session discovery, message sending, journal reading, and per-message status. Each tool earns its place without excess or obvious omission.
The surface covers the core messaging lifecycle: list sessions, send, read received records, and check status. A minor gap exists in that there is no direct way to list all messages sent by a session, though message IDs can be tracked individually.