Skip to main content
Glama
jarmstrong158

agentsync

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agentsync

No user-submitted related servers found.

    Related Servers

    • agentclaim

      volkangunay
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to safely collaborate in the same git working tree by managing file ownership, merging writes, and preventing snapshot races.
      10 npm
      2
      MIT

    • AgentXFlow

      harlixay7
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to collaborate on the same Git repository without conflicts through isolated worktrees, file locking, automated test verification, and a serialized merge queue.
      3 npm
      7
      MIT

    • connectr

      JrKrishh
      A
      license
      Not graded
      quality
      B
      maintenance
      Coordinates multiple AI coding agents by providing a shared task board, memory, and advisory file claims, letting agents work on the same repo concurrently without duplicating work or overwriting each other.
      27 npm
      1
      MIT

    • scoped

      OrenSegal
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coordination of concurrent Claude Code agent sessions by providing file claiming (claim/release/check) and automatic PreToolUse enforcement to block edits on files owned by other sessions.
      39 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

    A4.4/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with only minor overlap between provision and add_collaborator (both can add collaborators, but provision is for first-time setup) and between update_status and finish (both can mark done, but finish also opens a PR). The descriptions explicitly call out these differences, reducing ambiguity.

    Naming Consistency3/5

    Tool names mix verb_noun patterns (add_collaborator, check_conflicts, update_status) with bare verbs (provision, claim, release, finish) and one noun (history). While still readable, the naming convention is not consistent across the set.

    Tool Count5/5

    With 9 tools covering the full collaboration workflow (setup, claiming, surveying, conflict checking, status updates, release, finish, and history), the count is well-scoped for the server's purpose and does not feel padded or incomplete.

    Completeness4/5

    The tool surface covers the core lifecycle: provision and add_collaborator for setup, claim for staking work, survey and history for state visibility, check_conflicts for verification, and update_status/release/finish for progress and completion. Minor gaps exist, such as no direct way to view or edit your own claim details without using survey or re-claiming, but these are workaroundable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources