F
licenseNot graded
qualityC
maintenanceEnables multi-agent communication workflows with consensus arbitration, peer messaging, and operator-mediated collaboration through authenticated MCP tools.
1
-
Council Blackboard
Related Servers
Alternatives to Council Blackboard
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables multi-model leader-worker agent orchestration, workflow execution, and deterministic validation via structured MCP tools.5 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables multi-agent collaboration across different AI assistants and projects by providing a universal coordination layer for MCP-compatible agents to communicate, share context, and coordinate complex tasks seamlessly.1212 npm33MIT
ax-platform-mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables agent-native collaboration network for long-running agents and MCP clients with shared context, tasks, and interactive MCP App widgets.6MIT- AlicenseNot gradedqualityAmaintenanceMCP server for multi-agent collaboration enabling AI agents to communicate, delegate tasks, and share artifacts across clients and machines with federation support.21 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables multiple AI models to collaborate under a shared goal, architecture, plan, loops, sandbox, and acceptance criteria via a local-first MCP server.-
TDQS
C2.7/5.0
Scored across 11 tools
Disambiguation3/5
Some overlap exists: blackboard_add_item and colloquium_commit_to_blackboard both write to the blackboard, and get_state/get_session could be confused. However, descriptions clarify direct vs. distilled and state vs. session, so most tools have distinct purposes.
Naming Consistency3/5
Most tools follow a <domain>_<action> pattern (e.g., blackboard_get_state, colloquium_interject), but 'system_status' lacks a verb, breaking the otherwise consistent naming scheme.
Tool Count5/5
With 11 tools, the server is well-scoped, covering blackboard, colloquium, and audit operations without feeling bloated or sparse. This is within the ideal range for a specialized server.
Completeness4/5
The tool surface covers the core lifecycle of the domain: reading state, adding/proposing/approving items, managing sessions, and auditing. Minor gaps like explicit item deletion or update are not critical, so it feels reasonably complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues