Skip to main content
Glama
johannschiffer

CliSeat MCP

by johannschiffer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CliSeat MCP

No user-submitted related servers found.

    Related Servers

    • JEVULON VII (JVII)

      Jason-Fay
      A
      license
      A
      quality
      C
      maintenance
      Enables parallel AI coding agents to claim files atomically, detect and prevent workspace collisions, and receive deterministic zero-latency safety verdicts on destructive shell commands without any network egress. It also provides autonomous wave dispatch, worker recovery, and completion verification for multi-agent workflows via a shared coordination board.
      7
      13 npm
      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.
      2 npm
      MIT

    • agent-work-mcp

      yurikaza
      A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to run persistent, budgeted work sessions with dependency graphs, human decision queues, required validation, and clean handoffs for autonomous or human-in-the-loop execution.
      16
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct seat lifecycle action: claim, release, status check, listing, and command execution. There is no meaningful overlap between acquiring a seat and executing commands within it.

    Naming Consistency5/5

    All names use consistent snake_case verb_noun patterns (claim_seat, release_seat, get_seat_status, list_seats, execute_domain_command). The verbs are predictable and descriptive.

    Tool Count5/5

    Five tools is well-scoped for a seat-coordination server, covering the full acquire/use/release lifecycle without extras. Every tool earns its place.

    Completeness4/5

    The seat lifecycle is well covered: claim, release with handover, status, list, and bounded command execution. A lease-renewal or heartbeat operation is the only minor gap, but agents can work around it by releasing and re-claiming.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources