mm_claim_paths

Claim files or directories you’re about to edit so a peer session sharing this checkout can see they’re taken. Advisory only (never blocks an edit) and covers path prefixes; a conflicting claim returns the holder’s session id and activity so you can coordinate via mm_send_peer_message, and claims should be released with mm_release_claims when done.

At a Glance

• Category: Core
• Source: Built-in
• Availability: Listed by default
• Required parameters: 3
• Total parameters: 6

Parameters

Parameter	Type	Required	Description
project_path	string	Yes	Absolute path to the project root (the directory containing .mm/).
session_id	string	Yes	Your MM session id — the claim holder.
paths	array of string	Yes	Repo-relative paths or directory prefixes to claim.
intent	string	No	What you are doing with them, shown to whoever collides with your claim.
label	string	No	Human-readable name for you (agent name/model).
pid	number	No	Your process id, if known — lets a peer detect that an abandoned claim’s holder is gone.

Example

{
  "tool": "mm_claim_paths",
  "arguments": {
    "project_path": "/Users/you/projects/my-app",
    "session_id": "my-example",
    "paths": [
      "2026-01-15-my-feature"
    ],
    "intent": "example-intent",
    "label": "example-label"
  }
}

Related Tools

• mm_search - Full-text search across all entity types (specs, features, issues, notes, ide…
• mm_configure_integration - Configure an external service integration (github, trello, grain, gmail, noti…
• mm_sync_notion - Bidirectional sync between a Notion database and .mm/specs/ or .mm/notes/. Pu…
• mm_daily_brief - Generate a structured morning summary with active tasks, blockers, recently c…
• mm_revert_spec_completion - Revert a spec’s completion status in its parent feature. Tasks stay [x] but t…