Skip to main content
Glama
Sign In
Compounding MCP

Compounding MCP

by dshguilherme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Compounding MCP

No user-submitted related servers found.

    Related Servers

    • ClawSouls MCP Server

      clawsouls
      A
      license
      A
      quality
      C
      maintenance
      Provides tools for AI agent persona management, safety verification, and efficient swarm memory synchronization across multiple agents. It enables users to search and install personas while utilizing a token-efficient Git-based workflow for maintaining shared project context.
      9
      12 npm
      MIT

    • DIP

      vxu-labs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to maintain local-first project memory, coordinate task ownership across Git worktrees, and verify completion against project-defined checks with durable evidence stored in the repository.
      1
      Apache 2.0

    • swarm-engine

      PRIYAGDEV
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to spawn, parallelize, and synchronize multi-agent programming swarms through a stdio MCP interface. Provides tools for DAG-scheduled task dispatch, isolated Git worktree execution, atomic file locking, shared blackboard memory, and clean merging of completed agent work back to the main repository.
      17 npm
      1
      MIT

    • tower-mcp

      Rohanxmalik
      A
      license
      B
      quality
      B
      maintenance
      Enables AI coding agents on different machines and accounts to work one repository as a team by declaring file and symbol claims before editing, so collisions are refused up front rather than discovered at merge. It also supports delegating tasks between teammates' agents, which do the work with their own tokens and commit, with replies, commit shas, claims and messages landing on one shared board.
      20
      2
      MIT

    • Contrail

      mikey92
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables many coding agents to change one codebase at once by granting function-level clearances before edits, holding conflicting work, landing verified commits one at a time, and recording each change's intent, plan and test evidence as retrievable git notes.
      6 npm
      MIT

    • Kith

      connorhriley
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables cooperating coding agents to coordinate locally by claiming task scopes, working in isolated Git worktrees, reserving shared resources like ports and serialized commands, and verifying changes before integration. Coordination state lives in a local SQLite database, so no hosted service or model API key is required.
      73 npm
      4
      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.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a clearly distinct action within the swarm lifecycle: init/status manage the swarm, announce/commit/nominate/abstain handle worker contributions, and ancestry traces lineage. The descriptions explicitly distinguish similar concepts (e.g., nominate is a vote, not a quality proof; commit records a validated contribution). No overlapping purposes.

    Naming Consistency5/5

    All tool names follow the same `swarm_` prefix followed by a concise snake_case verb (abstain, ancestry, init, status, announce, commit, nominate). The convention is uniform with no deviations or mixed styles.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range and each maps to a distinct coordination operation in the swarm protocol. No tool feels redundant or out of scope for the server's stated purpose.

    Completeness4/5

    The surface covers the core swarm lifecycle: create a swarm, announce work, commit validated contributions, nominate candidates, abstain, trace ancestry, and read status. Minor gaps remain, such as no explicit tool to list/update/close swarms or fetch a specific candidate's full details, but these are workaroundable via status and ancestry.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources