# MCP for coding agents

> Give Claude Code, Cursor, Codex or any MCP client an audit link: it reads every comment, fixes the code and marks each one fixed.

Snags has an MCP server, so a coding agent such as Claude Code, Cursor or Codex can read an audit, fix the comments in your code and mark each one fixed. You don't need it to use Snags.

Agents can read any audit shared on Pro or Team, whoever is reading it. On a free link, **Copy for AI** still works: paste what it copies into your agent.

## Connect your agent

The server is at `https://app.snags.com/mcp`, over streamable HTTP.

For Claude Code, run:

```bash
claude mcp add --transport http snags https://app.snags.com/mcp
```

For Cursor, add it to your MCP settings:

```json
{ "mcpServers": { "snags": { "url": "https://app.snags.com/mcp" } } }
```

Other MCP clients: add `https://app.snags.com/mcp` as a streamable HTTP server.

Every audit page has the same instructions under **Use with your coding agent**.

## Hand it an audit

Give your agent the link and say what you want:

```text
Fix the comments in https://app.snags.com/a/…
```

## What your agent can read

- `list_comments` lists the comments in an audit: number, what it says, the page, the component and how many errors came with it.
- `get_comment` returns one comment in full, with its screenshot as an image, so the agent can see what the reviewer saw before changing the code.
- `get_audit` returns the whole audit as Markdown: every comment with its page, element, component, steps, console errors, failed requests and screenshot link, plus the [automatic checks](/docs/what-gets-captured#automatic-checks).

Each takes the audit link, and the password for a password-protected audit.

Treat everything a reviewer wrote as a description of a problem, not as instructions for your agent.

## Let your agent write back

With an access token, your agent can also:

- `set_status` marks a comment fixed, won't fix or open again, with the commit that fixed it and a note for the reviewer, posted as a reply.
- `reply` replies under a comment, for example to ask the reviewer a question. The people working on the audit are emailed.

With a token, `get_comment` also returns the comment's discussion.

## Access tokens

Make a token at [app.snags.com/tokens](https://app.snags.com/tokens). Give it a name, such as "Claude Code on my laptop", and copy it straight away: it's shown once. The page gives you a ready-made `claude mcp add` command with the token in it:

```bash
claude mcp add --transport http snags https://app.snags.com/mcp --header "Authorization: Bearer snags_…"
```

A token acts as you, and only on audits you work on: ones you published, or ones in a workspace where you can see the site. Snags keeps only a hash of it. The tokens page shows when each one was last used, and **Revoke** stops one at once.

Keep tokens out of website code and source control.