Agent Claim MCP server

Agent Claim MCP

Languages: English · 日本語 · 简体中文 · Русский · Español

Use Agent Claim MCP when multiple coding agents share one worktree and you need a tiny local coordination primitive before edits, not a full orchestration framework. It gives agents one job: claim paths, detect collisions, and release ownership so parallel work stops stomping the same files.

Agent Claim MCP is a local-first MCP server for Claude Code, Cursor, Cline, and other MCP clients that need file ownership coordination without queues, planners, or custom AGENTS.md conventions. The current release surface centers on three bounded actions only: claim normalized paths, inspect who owns them, and release by path or claim id with explicit conflict reporting across separate sessions.

Release status: @vk0/agent-claim-mcp@1.0.0 is live on npm, so the npx -y @vk0/agent-claim-mcp install path is now the truthful default for external users. Phase 5 external proof may be satisfied by either Official MCP Registry validation or a live Smithery listing, but the current proof state remains pending until one of those public artifacts is explicitly verified. Official MCP Registry validation is still pending, so do not describe the package as registry-accepted or marketplace-listed until a real registry or Smithery proof URL is cited.

Milestone truth: the product wedge stays narrow, 3 tools plus a local JSON ledger for shared-worktree collision prevention, not a broader orchestration platform.

Current next manual step: complete the pending human rerun and verification path for Official MCP Registry proof, then record the verdict from that run instead of assuming acceptance from npm availability.

Registry rerun quickstart

Current truthful state:

• npm 1.0.0 is live
• Official MCP Registry acceptance is still pending
• workflow 25282612113 did not complete the registry validation path
• the repo is now past the earlier NPM_TOKEN secret-fix step, but the registry proof still needs a human rerun plus verification before it can be treated as accepted

Exact rerun command:

gh run rerun 25282612113 --repo vk0dev/agent-claim-mcp

After the rerun, verify in this order:

1. confirm the rerun completed successfully in GitHub Actions
2. run npm run preflight:registry
3. follow docs/official-registry-validation-runbook.md
4. only then record registry acceptance as proven

Operator shortcut: use the runbook's Quick operator path for the exact rerun-to-verification order, and treat npm-live status as separate from registry-proof status.

Why / When to use

Choose this server when your workflow already has task routing, but still needs a simple lock-like primitive at edit time:

• two or more agents can touch the same repo in parallel
• you want collision detection before file edits, not after merge conflicts
• you want claims to expire automatically with TTLs
• you want a narrow primitive that another agent can understand from name + description alone
• you do not want a bundled rules engine, queue runner, or orchestration platform

Installation

The canonical external install path is now the published npm package:

{
  "mcpServers": {
    "agent-claim": {
      "command": "npx",
      "args": ["-y", "@vk0/agent-claim-mcp"]
    }
  }
}

Status note: npm install is live today, but Official MCP Registry validation and Smithery/other marketplace proof are still not established, so treat the package as npm-available first rather than marketplace-verified.

Shortened. The full README is on GitHub.