agentlink
Related Servers
Alternatives to agentlink
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code, Codex CLI and Antigravity (Gemini) agents to exchange messages that are pushed live into each other's open sessions, with mail_send, mail_check and mail_peers tools so no agent has to poll. Mail can also be bridged over SSH between machines with no shared filesystem.357 npm1MIT
- 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.814 npm3AGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables different AI assistants to exchange messages with each other across platforms and sessions using simple natural language commands. Messages are stored persistently, so they survive restarts, and instances can register names, send messages, and check inboxes.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and exchange text messages between existing, locally authenticated Claude Code and Codex sessions on the same machine, using installed clients without API keys.9 npm20MIT
- AlicenseNot gradedqualityDmaintenanceLets Claude Code instances discover and message each other across sessions, with reliable delivery via hooks instead of experimental channels.20 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables local messaging between Claude Code and Codex agents with durable delivery, peer discovery, and reply tracking.1MIT
This server cannot be deployed
TDQS
Scored across 5 tools
Each tool targets a distinct operation (send, list peers, inspect network, read inbox, manage invites), and the descriptions explicitly cross-reference each other to resolve the peers-vs-network and network-vs-inbox boundary. The only residual overlap is between peers (who is online) and network (machines and undelivered messages), which is mild and well-signposted.
All five names are single lowercase words with no mixed camelCase/snake_case, so the set reads uniformly. It is not a verb_noun pattern and semantics vary (send is a verb, inbox/network are nouns), but the terse style is consistently applied.
Five focused tools cover the whole domain with no duplication; invite even folds create/list/revoke into one parameterized tool rather than three. Nothing feels bolted on, and the surface stays easy to scan.
The messaging lifecycle (discover, send, durable delivery, read) plus network membership via invite is covered end to end. Minor gaps remain: no way to remove/leave a machine from the network, no sent/outbox or per-message status lookup, and no message history beyond the unread set.