Skip to main content
Glama
gabogabucho

ACDP

by gabogabucho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to ACDP

No user-submitted related servers found.

    Related Servers

    • STMA by Matte-AI-LLC

      STMAofficial

      Matte-AI-LLC
      F
      license
      Not graded
      quality
      C
      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.
      -

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      123 npm
      5
      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

    • mcp-agent-bridge

      xfajarr
      A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that provides shared, real-time context across multiple AI agents via WebSocket and MCP resource notifications, enabling collaborative workspaces, memory, tasks, and messaging.
      29 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

    A4.1/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct action: locking, unlocking, checking locks, requesting commits, notifying sync, listing agents, starting/connecting to servers, and checking connection status. No two tools have overlapping purposes.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., lock_files, release_files, list_agents, request_commit). Minor deviations like connection_status (noun_noun) and start_local/connect_remote (verb_adjective) break the pattern slightly, but the naming remains readable and predictable.

    Tool Count5/5

    With 9 tools, the set is well-scoped for a coordination server. Each tool serves a clear purpose without redundancy, fitting comfortably within the ideal 3-15 range.

    Completeness4/5

    The tool set covers the core workflow: file locking (lock_files, release_files, check_locks), commit request and notification (request_commit, notify_sync), and agent/connection management (list_agents, start_local, connect_remote, connection_status). Minor gaps exist, such as no explicit approve_commit or disconnect tool, but these are likely handled outside the tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources