> ## Documentation Index
> Fetch the complete documentation index at: https://reshot.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat a Journey, Run, Decision, Rendition, Publication, and Release Book as distinct lifecycle objects.
> Never describe imported or customer-attested material as independently verified evidence without a complete hosted custody chain.

# Coding-agent tools (beta)

> Use beta local agent tools for Reshot status, full-flow capture, and delivery verification.

Reshot ships a local [Model Context Protocol](https://modelcontextprotocol.io/) server with the screenshot CLI. It lets an MCP-compatible coding agent inspect project status, run selected flows headlessly, compare them with their baselines, and verify hosted delivery without opening the dashboard.

<Warning>
  These tools are beta. Reshot does not currently record or display hosted-agent
  provenance, so a hosted agent run is not attributable in the dashboard. A
  named human reviewer must still make every approval decision.
</Warning>

## Configure the server

Add Reshot to your MCP client configuration from the repository that contains `reshot.config.json`:

```json theme={null}
{
  "mcpServers": {
    "reshot": {
      "command": "npx",
      "args": ["-y", "@reshotdev/screenshot", "mcp"],
      "cwd": "/absolute/path/to/your/repository"
    }
  }
}
```

You can also run the installed binary directly with `reshot-mcp`. The server uses newline-delimited JSON-RPC over stdio and never opens a browser UI.

## Tools

| Tool             | Purpose                                                            |
| ---------------- | ------------------------------------------------------------------ |
| `reshot_status`  | Read project, capture, review, and drift status as JSON.           |
| `reshot_capture` | Run all configured flows or a selected list in headless diff mode. |
| `reshot_verify`  | Verify publish, pull, and hosted asset delivery readiness.         |

`reshot_capture` collects evidence; it does not approve a visual change or override the `reshot/visual-review` merge gate. A human reviewer still owns the approval decision.

## Agent loop

1. Ask the agent to run `reshot_capture` for the flow it changed.
2. Let the agent inspect the capture and diff output, fix the implementation, and rerun the flow.
3. Publish the final CI result to Reshot.
4. Review the PR's flow-by-context matrix and approve or reject it.

The project API key remains local to the CLI configuration. Use a scoped project key in CI and do not put credentials in the MCP configuration file.