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.
      3 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.
      MIT

    • sangam

      uditjainstjis
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents on different machines to share verbatim session context and coordinate file leases, preventing concurrent edits and allowing each agent to query the other's exact actions and words.
      MIT

    • MCP Agent Mail

      Dicklesworthstone
      A
      license
      Not graded
      quality
      A
      maintenance
      A coordination layer for coding agents that provides memorable identities, inbox/outbox messaging, searchable message history, and file lease management to prevent conflicts. Uses Git for human-auditable artifacts and SQLite for fast queries, enabling multiple agents to collaborate across projects without stepping on each other.
      2,144
      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