cos-link-mcp
Related Servers
Alternatives to cos-link-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding sessions across multiple agent CLIs to share one identity and inbox, hand off tasks, send encrypted files and conversation transcripts, publish living documents, and coordinate approvals through hooks and MCP tools.218 npmMIT
- AlicenseAqualityAmaintenanceWalkie-talkies for AI coding agents: Claude Code, Codex, Cursor and any MCP client message other developers' agents directly, peer to peer over HyperDHT and end-to-end encrypted. No server, no account. Pair once with a 6-digit verify code; offline peers get messages through a sealed mailbox on the DHT. Tools: send_message, read_inbox, list_messages, list_peers, get_status.5Apache 2.0
- FlicenseNot gradedqualityCmaintenanceExposes stdio MCP tools that let an AI coding agent delegate bounded tasks to a peer agent, exchange updates and cancellations, and send non-blocking messages over an authenticated local WebSocket hub. It carries routing IDs, mailbox durability, and a peer-message notification channel so independent sessions can coordinate work.-
- AlicenseAqualityAmaintenanceLocal agent-to-agent messaging and coordination for coding sessions on one machine, through MCP and a CLI. Includes threaded mail, full-text search, per-repository agent rosters, advisory file reservations, and optional notifications. Integrations cover Claude Code, Codex, Cursor, Devin, Grok, OpenCode, and Antigravity. Standalone agents and T3 Code sessions can share the same local server.2232MIT
- AlicenseCqualityCmaintenanceEnables IDEs and MCP hosts to drive a user's Grok Bot cloud agents, including sending messages, waiting for replies, reading history, and managing agents, secrets, widgets, handoffs, and desktop access. It acts as an outbound bridge from Cursor, Claude, and VS Code to those cloud agents.21MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to exchange end-to-end encrypted, threaded email-style messages across tools, vendors, and machines through a zero-install remote MCP server. Supports sending, replying, reading, and threading messages with inbox checks, read receipts, and key verification.MIT
TDQS
Scored across 8 tools
Each tool targets a distinct resource/action: identity, contact listing, inbox polling, task listing/reading/canceling, coordination sending, and status updating. No two tools appear to do the same thing, and boundaries are clear.
All names follow a consistent snake_case verb_noun pattern (get/list/read/send/cancel/update). The convention is predictable across the entire set.
Eight tools is a well-scoped count for a coordination/communication server, covering identity, contacts, inbox, and task lifecycle without obvious redundancy.
Core workflows for identity, relationship listing, inbox polling, task read/cancel/update, and coordination sending are present. Minor gaps exist, such as no explicit create_task or inbox acknowledgement/delete, but likely workable via existing operations.