Skip to main content
Glama
Buggy1111

agent-lease-mcp

by Buggy1111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-lease-mcp

No user-submitted related servers found.

    Related Servers

    • Agent Collab MCP

      Nathan-Z01
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple AI coding agents to collaborate on a project by coordinating tasks, file leases, and messages through a shared hub, preventing conflicts and enabling parallel development.
      MIT

    • 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

    • agent-bridge

      suneel944
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.
      2
      MIT

    • tower-mcp

      Rohanxmalik
      A
      license
      B
      quality
      A
      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

    • Hive

      okezue
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple coding agents to collaborate in a shared workspace with roles, messaging, concurrent file editing, task graphs, and live awareness of each other.
      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.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Lease tools (claim/release/owner), task queue tools (next_task/ack/retry/cancel), and history are clearly distinct. Some overlap exists among messaging/state tools—say vs send, and room vs inbox vs jobs—but their descriptions give enough distinction to avoid most misselection.

    Naming Consistency3/5

    All names are lowercase snake_case and only next_task is multiword, so surface formatting is consistent. However, the set mixes bare verbs (claim, release, say, ack) with nouns (owner, jobs, inbox, room, history), so there is no predictable verb_noun pattern.

    Tool Count5/5

    13 tools is well within the appropriate range for a coordination server covering leases, messaging, task delivery, and audit. Each tool maps to a distinct operation and the count does not feel bloated.

    Completeness4/5

    Core lease lifecycle (claim/release/owner), task delivery lifecycle (send/next_task/ack/retry/cancel), messaging (say/inbox/room/jobs), and audit (history) are covered. Minor gaps remain: no way to list your active leases without releasing, and no global task listing beyond addressed items.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources