# Coordination MCP tools

Coordination tools let clients coordinate project work with lease locks.

## Tools

- `lock_acquire` — Acquire a project-scoped lease lock for coordinated work. Pass `lock_key` and `lease_ttl_seconds`; the lease starts when the lock is acquired. By default it tries once. Pass `wait_ms` to wait for the lock, up to 20,000 ms; if it's still held when the wait ends, the response has `acquired: false` and the last lease Solo saw. Waiting can be cancelled, has no fairness guarantee, and database contention can delay the reply past the wait budget.
- `lock_status` — Check whether a project-scoped lease lock is currently held.
- `lock_release` — Release a project-scoped lease lock you own.

## Notes

Use locks for short-lived coordination around shared files, plans, migrations, or other work where overlapping edits would be expensive. Locks are coordination signals, not permanent ownership.

Acquiring or releasing locks requires an actor identity; checking lock status only requires project scope. Solo-managed agents are identified automatically. For acquire and release operations, callers running outside Solo can register as external actors with `identify_session`. See [Agent and terminal tools](./agent-terminal.md).

---

Are you a human? Read this doc on the web: https://soloterm.com/docs/mcp-tools/coordination