A
licenseNot graded
qualityC
maintenanceEnables independent agents to share persistent, project-scoped memory and coordinate work through connected records, evidence, claims, leases, and handoffs.
MIT
CPG-Radio
by pierre427
Related Servers
Alternatives to CPG-Radio
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with shared communication and persistent state over HTTP and MCP, letting an agent save its progress, search and reuse other agents' prior work, coordinate tasks in shared spaces, exchange direct messages, and hand its role to a successor when a session ends. State is kept on PostgreSQL with signed, append-only records that anyone can verify.Business Source 1.1
- AlicenseNot gradedqualityAmaintenanceLocal OS for your AI Agents fleets. ——————- Enables AI agents to coordinate through a durable local board with shared state, ticket lifecycle, evidence-based approvals, and journal-woken handoffs.2Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables multiple coding agents running side by side to coordinate through a shared mailbox, claim list, and append-only log, so they can see peers, avoid duplicate work, and share findings or dead ends.MIT
- AlicenseNot gradedqualityBmaintenanceEnables provider-neutral durable coordination for coding agents sharing Git work, including peer discovery, durable messaging, job progress tracking, and FIFO integration authority with fenced leases.MIT
- 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
TDQS
C2.7/5.0
Scored across 59 tools
Disambiguation2/5
Several tool families—poll_messages/poll_thread, ack_messages/ack_thread/ack_delivery, record_structured_result/reveal_result/complete_assignment, renew_lease/renew_resource, complete_worker/complete_assignment—have nuanced but near-overlapping purposes, so an agent can easily select the wrong one. The descriptions are detailed, but at 59 tools the set lacks clear semantic separation.
Naming Consistency2/5
Most tools use snake_case verb_noun, but there are many inconsistent outliers: cpg_think, cpg_query, replan, reflect, tips, protocol_health, stale_report, post_progress, complete_assignment. Verbs are not normalized across categories (create/start/spawn, poll/subscribe, ack/acknowledge, close/complete/cancel), so the pattern is only loosely predictable.
Tool Count1/5
59 tools is an extreme size for an MCP server; even though the platform covers many subdomains, it is far beyond a well-scoped tool set and will overwhelm agents with selection overhead. It would benefit from consolidated compound tools or splitting into focused servers.
Completeness4/5
The server covers the core lifecycle well: planning, task leasing, workflow fan-out/fan-in, worker heartbeats/completion, threaded messaging with cursors/acks, campaign and barrier coordination, facts/beliefs/tips, and result commitments. Minor gaps like explicit campaign dissolution or direct fact/belief deletion are workaroundable through supersede/cancel/query tools.
Maintenance
ActivitySlowing
ResponsivenessNo issues