Skip to main content
Glama
andy5090

central-mcp

by andy5090
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to central-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Orchestrator

      Hackerprod
      A
      license
      Not graded
      quality
      B
      maintenance
      A shared MCP hub that enables multiple coding-agent CLIs to register, discover, and communicate asynchronously via a standalone daemon. It provides MCP tools for agent registration, session management, non-blocking messaging, and cursor-based event reading.
      4 npm
      1
      MIT

    • 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

    • CacheBash

      rezzedai
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.
      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

    A3.9/5.0

    Scored across 19 tools

    Disambiguation4/5

    The tools fall into clear clusters—project registry, dispatch lifecycle, history/portfolio reporting, preferences—and each tool has a distinct primary purpose. Some pairs could still be confused at first glance (dispatch_history vs list_dispatches, portfolio_digest vs orchestration_history), but the descriptions make the differences recoverable.

    Naming Consistency4/5

    Most tools follow a snake_case verb_noun pattern like add_project, remove_project, list_projects, and cancel_dispatch. A few break the pattern with noun-first names like project_status, project_pulse, and portfolio_digest, but the overall convention is predictable and readable.

    Tool Count4/5

    At 19 tools, the set is on the heavier side, but the breadth is justified for a central orchestration server covering project registry management, dispatch lifecycle, monitoring, history, preferences, and token usage. It feels slightly dense rather than bloated, and few tools are obvious candidates for removal.

    Completeness4/5

    The core domain is well covered: project CRUD plus reorder, dispatch start/check/list/cancel, per-project and portfolio history, project state/note, preferences, and token usage. Minor gaps exist—no dedicated workspace lifecycle tools, and check_dispatch references a dispatch_background tool that is not present in the set—but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources