lockstep-mcp

Get coordinator config and state summary

Create a task. Complexity determines review requirements: simple=no review, medium=verify on completion, complex/critical=planner approval required. Isolation determines whether implementer works in shared directory or isolated git worktree.

Claim a task and set status to in_progress

Update a task

Submit a completed task for planner review (required for complex/critical tasks, recommended for medium)

PLANNER ONLY: Approve a task that is in review status, marking it done

PLANNER ONLY: Request changes on a task in review, sending it back to in_progress

PLANNER ONLY: Approve multiple tasks at once. More efficient than approving one by one.

Get task counts by status. Lighter than task_list - use when you just need to know how many tasks are in each state.

List tasks with optional filters. For active work, defaults to excluding done tasks to reduce response size. Use includeDone=true or status='done' to see completed tasks.

Acquire a named lock

Release a lock

List locks with optional filters

Append a note

List recent notes

Read an artifact file

Write an artifact file

Read a file

Write a file

Run a shell command

Install a tool using a package manager

Append a log entry

Initialize coordination session. Call this first to set up your role (planner or implementer). Returns guidance based on your role and current project state.

Store project context (description, goals, tech stack, acceptance criteria, tests, implementation plan). Called by planner to define what the project is about.

Get stored project context. Returns the project description, goals, and other context set by the planner.

Set the project status. Use 'stopped' to signal all implementers to stop working.

Launch a new implementer agent (Claude or Codex) in a new terminal window. The planner uses this to spawn workers. Set isolation='worktree' to give the implementer its own git worktree for isolated changes.

List all registered implementers and their status.

Reset all implementers to 'stopped' status. Use this when starting a fresh session or when implementers are stale/not actually running.

PLANNER ONLY: Reset the coordination session for a fresh start. Clears all tasks, locks, notes, and archives discussions. Use this when starting a new project or when data from previous sessions is cluttering the dashboard.

Open the lockstep dashboard in a browser. Call this to monitor progress visually.

Start a new discussion thread. Use this when you need input from other agents or want to discuss an architectural/implementation decision.

Reply to an existing discussion thread.

Resolve a discussion with a final decision. Creates an auditable record of the decision.

Get a discussion thread with all its messages.

List discussions. Use this to check for discussions waiting on you.

Check for discussions waiting on you. Call this between tasks to see if anyone needs your input.

Archive a resolved discussion. Archived discussions can be deleted later.

Archive old resolved discussions and optionally delete old archived ones. Use for maintenance.

Get the status of a worktree including commits ahead/behind main, modified files, and untracked files. Use this to check an implementer's progress before merging.

Merge an implementer's worktree changes back to main. This should be called after a task is approved. If there are conflicts, returns conflict information for manual resolution.

List all active lockstep worktrees in the project.

Clean up orphaned worktrees that no longer have active implementers. Call this during maintenance.