entangled-mcp
Related Servers
Alternatives to entangled-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables cooperating coding agents to coordinate locally by claiming task scopes, working in isolated Git worktrees, reserving shared resources like ports and serialized commands, and verifying changes before integration. Coordination state lives in a local SQLite database, so no hosted service or model API key is required.02MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding-agent sessions on the same machine to collaborate locally and durably by exchanging requests, replies, and task results through an authenticated loopback server with SQLite-backed storage, joined via CLI or an MCP stdio bridge. It also handles message delivery by priority and wait time, deduplicates idempotent sends, enforces task versioning, and preserves artifacts by content hash.10 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents in different editors and MCP clients to share messages, project context, notes, task ownership, handoffs, and advisory file claims through a local SQLite-backed coordination server. Supports MCP stdio, MCP Streamable HTTP, a JSON HTTP API, and a local CLI for multi-project agent collaboration.MIT
- AlicenseBqualityBmaintenanceEnables AI agents from different frameworks to communicate asynchronously via a persistent SQLite-backed bus, with doorbell wakeups for sub-second notifications and full message history.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and tools to share durable, approved knowledge, current decisions, task ownership, and handoffs from a local-first workspace kept outside any single AI product. Markdown holds human-readable rules, goals, and narratives while SQLite tracks agents, sessions, tasks, leases, and audit events behind one transport-independent core.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables peer-to-peer communication, discovery, shared state, and file coordination between AI coding agents across machines and sessions.16 npm17Elastic 2.0
TDQS
Scored across 10 tools
Each tool has a distinct purpose: presence (announce, get_swarm), knowledge (broadcast, query), messaging (send, check), locks (acquire, release, list), and activity feed. Descriptions clarify boundaries, and no two tools overlap significantly.
All tools use consistent snake_case with an 'entangled_' prefix and a verb_noun pattern (e.g., acquire_lock, send_message). 'announce' is a verb-only outlier but still fits the predictable action-oriented style.
10 tools cover the multi-agent coordination domain well without redundancy; each tool earns its place. The set is well-scoped for the server's stated purpose.
Core operations are covered: knowledge sharing (broadcast/query), messaging (send/check), locks (acquire/release/list), presence, and activity feed. Minor gaps include no update/delete for knowledge or messages, and no explicit leave-swarm or lock-renew operation.