Skip to main content
Glama
aetheris-consulting

Council Blackboard

by aetheris-consulting
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Council Blackboard

No user-submitted related servers found.

    Related Servers

    • agent-broker

      strommy76
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables multi-agent communication workflows with consensus arbitration, peer messaging, and operator-mediated collaboration through authenticated MCP tools.
      1
      -

    • Warren

      Dymyt-ry
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multi-agent and human collaboration through MCP with scoped rooms, invites, @mentions, task claims, file locks, and push delivery to Claude Code, Codex, and Cursor. Provides cross-company safety, human review, and MCP/A2A protocols for coordinated agent work.
      16 npm
      Apache 2.0

    • Agent Hub MCP

      gilbarbara
      A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      12
      27 npm
      33
      MIT

    • kitty-hive

      seangx
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for multi-agent collaboration enabling AI agents to communicate, delegate tasks, and share artifacts across clients and machines with federation support.
      11 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources