Skip to main content
Glama

Related Servers

Alternatives to agent-locks

No user-submitted related servers found.

    Related Servers

    • 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
    • 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.
      -
    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that lets multiple AI coding agents share state, preserve context across sessions, and coordinate via a knowledge graph, messaging, and branch-preserving checkpoint/resume with conflict handling.
      114 npm
      Apache 2.0

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: querying locks, checking conflicts, creating, updating, and finishing. No two tools overlap in purpose; lock_query and lock_check_conflict are complementary, with the latter explicitly informational.

    Naming Consistency5/5

    All tool names follow the exact same verb_noun pattern: lock_query, lock_check_conflict, lock_create, lock_update, lock_finish. The prefix 'lock_' is uniform and the verbs clearly indicate actions.

    Tool Count5/5

    Five tools is well-scoped for a lock-management server. Each tool covers an essential operation without redundancy, making the surface easy to navigate.

    Completeness4/5

    The lifecycle is largely covered: query, create, update, and finish. A missing explicit cancel/delete and a tool to list individual tasks are minor gaps; the error message from lock_update provides task discovery, but a dedicated view would be cleaner.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive