Connect Your Agent (MCP)

What your coding agent can do with SnagRelay over MCP: the tools, how it signs in, and how to keep it safe.

SnagRelay runs one MCP server at https://mcp.snagrelay.com/v1. Add it to Cursor, Claude Code, or Codex and the agent can read your reports with full context, then close them when the fix lands. Setup takes a minute and lives on the project's Agent tab. The plugin source is on GitHub.

How it signs in

OAuth 2.1 with PKCE and dynamic client registration. The agent opens a SnagRelay page, you click Allow, and it's connected. There's no token to copy.
The consent screen says the agent can read your reports, console logs and network data and mark reports resolved.
Sign-in lasts 90 days. You can revoke it any time with Disconnect on the Agent tab, or under Account → API tokens.
Clients that can't do OAuth can send an API token as a Bearer header.

Endpoints

URL	Access
`https://mcp.snagrelay.com/v1`	Every project you can access. Read and write
`https://mcp.snagrelay.com/v1/readonly`	Every project you can access. Read-only: list and read, write tools are hidden
`https://mcp.snagrelay.com/v1/{projectId}`	One project only. Read and write: list, read, report progress, mark resolved
`https://mcp.snagrelay.com/v1/{projectId}/readonly`	One project only. Read-only

Tools

Tool	What it does
`find_issues`	Lists recent open reports (key, title, status) without payloads. Filter by status, search by title, and page through results. `list_issues` is an alias
`get_issue_context`	Loads one report: the elements picked, console errors, failed requests, repro steps, replay link, and a screenshot as a resource link. Pass a key like `SHOP-12`, a tracker key, or a report URL
`get_issue_payload`	Fetches one full network request or response body, or one console line, by the index from `get_issue_context`
`get_related_history`	Past resolved reports that share this report's CSS selector, failing API path, or similarity group, including the PR that fixed them
`report_progress`	A heartbeat while the agent works. Pass the key plus the current tool or file
`mark_issue_resolved`	Marks the report resolved. Optionally passes `pr_url`, `commit_sha`, `branch`, and a `resolution_note`
`whoami`	Identity, accessible projects, plan, and token scope. Useful when a call fails

report_progress and mark_issue_resolved are the write tools. They're not available on the read-only endpoint, or with a token that lacks write scope.

Close the loop with a note

When the agent calls mark_issue_resolved, it can pass a resolution_note: one plain sentence written for the person who reported the bug. It's included in the "It's fixed" email. See Closing the loop.

Prompts that work

Fix the latest open SnagRelay report in this project.

fix SHOP-12

List my open SnagRelay reports and pick the most likely to be one root cause.

The agent only calls SnagRelay when you ask

The tools are written so an agent won't query SnagRelay just because the server is connected. It loads a report when you give a key, a report link, or ask it to list reports.

Without MCP

Every report has a No MCP? Copy the full context option, in Markdown or JSON, for pasting into any agent. You'll find it on the report page under Hand it to your agent.