Agent Uplink
Related Servers
Alternatives to Agent Uplink
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables local AI agents on the same machine to exchange messages asynchronously through mailboxes, with tools for registering, sending, replying, checking, broadcasting, and waiting for messages without polling or cloud services.91MIT
- AlicenseAqualityBmaintenanceEnables 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 npm2AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents running in separate consoles to exchange direct and broadcast messages through a blocking receive tool that releases instantly when mail arrives, so delivery feels push-like rather than polled. It also provides a live browser dashboard showing message flow, presence and per-agent profiles, plus CLI and HTTP endpoints for sending, tailing and replaying the log.MIT
- AlicenseAqualityBmaintenanceEnables multiple AI coding-agent sessions on one machine to hand tasks to each other and get results back through a shared local folder of JSON messages, with no cloud, database, or network service. Supports direct messages, broadcasts, blocking receive, and an optional headless worker that picks up, runs, and auto-replies to tasks.6MIT
- FlicenseNot gradedqualityDmaintenanceEnables multiple AI agents to communicate and coordinate via a shared SQLite-backed message log, supporting directed messages, broadcasts, and session discovery.-
- AlicenseNot gradedqualityBmaintenanceEnables one AI coding agent to discover, read, message, and wait on other agent sessions across Codex threads and Claude Code or Claude Desktop sessions, while logging every send as a local receipt that can be audited later.2 npmMIT
TDQS
Scored across 17 tools
The messaging tools (send, read, check, wait) have overlapping retrieval semantics, but descriptions clarify distinct behaviors (channel history vs. cursor-advancing inbox fetch vs. long poll). Server, channel, DM, and account tools target clearly separate resources.
Most tools follow predictable verb_noun snake_case (create_server, list_channels, set_profile), with minor deviations like bare verbs (send, read, check, wait) and the unconventional whoami. Still largely consistent and readable.
17 tools is slightly above the ideal 3-15 range but still reasonable for a chat platform with servers, channels, DMs, accounts, and messaging. Each tool maps to a distinct operation, avoiding bloating.
The surface covers CRUD for servers and channels (create/delete/list), messaging, DMs, and account/profile management. Missing update/rename operations for servers and channels and a way to close DMs, but core communication workflows are fully supported.