Skip to main content
Glama
danieldoderlein

LLM Bus

by danieldoderlein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to LLM Bus

No user-submitted related servers found.

    Related Servers

    • Axis

      VirSanghavi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for coordinating multiple AI agents across developers and vendors with a shared job board, per-file locking, and live project context.
      5
      AGPL 3.0
    • STMA by Matte-AI-LLC

      STMAofficial

      Matte-AI-LLC
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables AI coding agents to coordinate by sharing environment snapshots and diffs, surfacing overlapping work, exchanging debug-session messages, handing off tasks, and enforcing policy preflight checks.
      -

    • AgentRoom MCP Server

      seonglae
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that provides coordination tools (claim, release, broadcast, state) for concurrent coding agents working on a CRDT-merged shared filesystem, ensuring no edits are lost and enabling collaborative task completion.
      MIT

    • Concordia

      Zorabi
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first MCP server for coordinating Codex and ZCode agents, enabling task management, event tracking, and optional cross-machine Redis relay.
      5 npm
      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

    B3.4/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: admin tools for project management, task tools for workflow, sequence tools for numbering, communication tools for posts, and utility tools for awareness. No two tools overlap in intent.

    Naming Consistency4/5

    Names follow a consistent verb_noun or prefix_noun pattern (e.g., admin_provision, task_create, list_participants), with minor exceptions like 'whoami' vs. 'who_is_active' and 'whats_new' vs. 'whoami'—mostly predictable.

    Tool Count3/5

    27 tools is relatively high, covering project admin, tasks, sequences, leases, and communication. While each tool serves a specific need, the set could likely be consolidated, e.g., merging some sequence tools or reducing admin variants.

    Completeness4/5

    The server covers core operations for project collaboration: admin provisioning, task lifecycle (create, assign, start, block, resolve, ship), sequence management, leases, and communication (post, ack, read). Minor gaps exist (e.g., no direct message or broadcast), but the surface is largely complete for its domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources