Agent Tab
Connect Cursor, Claude Code, or Codex to a project so your agent can read reports and fix them.
The Agent tab is where you hand a project's reports to your coding agent. SnagRelay runs
an MCP server at https://mcp.snagrelay.com/v1. You add it to your agent once, approve
it in your browser, and from then on the agent can read reports, fetch their context, and
mark them resolved. The URL on this tab is scoped to the current project.
There's no token to copy. Your agent signs in with OAuth 2.1 (PKCE): it opens a SnagRelay page, you click Allow, and it's connected.
Connect
Choose your client with the switch at the top of the tab. Every command below already contains your project's URL on the tab itself:
https://mcp.snagrelay.com/v1/YOUR_PROJECT_IDTo let one connection reach every project you can access, drop the project id:
https://mcp.snagrelay.com/v1.
The quickest way is the Add to Cursor button on the Agent tab. It adds this project's server. To also get ready-made skills, install the SnagRelay plugin instead:
- In Cursor, open Customize → Marketplace, search for SnagRelay, and install the plugin. It adds the SnagRelay MCP server, ready-made skills (fix an issue, open a pull request, resolve an issue, triage, connect), and a rule that tells the agent to load the report before proposing a fix.
- Approve SnagRelay in your browser when Cursor asks you to sign in. Click Allow.
The plugin connects to all of your projects. Use either the button or the plugin, not both:
each registers a server named snagrelay.
Install the plugin. It adds the MCP server and the same skills as in Cursor:
-
Add the marketplace and install:
claude plugin marketplace add snagrelay/agent-plugin claude plugin install snagrelay@snagrelay -
Run
/mcpin Claude Code, pick snagrelay → Authenticate, then click Allow in the browser.
Skills are namespaced, for example /snagrelay:fix-issue SHOP-12.
Prefer the bare server, scoped to this project? Use it instead of the plugin, because both are named snagrelay:
claude mcp add --transport http snagrelay https://mcp.snagrelay.com/v1/YOUR_PROJECT_IDInstall the plugin. It adds the MCP server and the same skills as in Cursor:
-
Add the marketplace and install:
codex plugin marketplace add snagrelay/agent-plugin codex plugin add snagrelay@snagrelay -
Run
codex mcp login snagrelayand click Allow in the browser.
Prefer the bare server, scoped to this project? Use it instead of the plugin, because both are named snagrelay. Add it to ~/.codex/config.toml:
[mcp_servers.snagrelay]
url = "https://mcp.snagrelay.com/v1/YOUR_PROJECT_ID"Add the server URL to any MCP client that supports Streamable HTTP with OAuth. If a
client can't do OAuth, send an API token
as a Bearer header instead.
Ask it to fix something
Once connected, try:
Fix the latest open SnagRelay report in this project.or name a report by its key:
fix SHOP-12The agent loads the report, reads the evidence, proposes the change, and marks the report resolved. See Connect your agent (MCP) for what it can call.
You can also start from the inbox. Reports have a Fix in Cursor button and a Copy for Claude Code command. See The inbox.
Status and connections
The side panel shows the connection status:
- Waiting for your agent… until the agent makes its first call. The tab updates by itself, with no refresh.
- Connected · read 2m ago once it has.
Below that is a list of the agents that have signed in, each with when it last read a report and when its access runs out (sign-in lasts 90 days). Click the × on a connection to Disconnect it. It loses access until it signs in again.
Read-only URL
For CI or tools that should only look, use the read-only URL shown on the tab:
https://mcp.snagrelay.com/v1/YOUR_PROJECT_ID/readonlyA read-only connection can list reports and read their context, but can't mark anything resolved or report progress.
Not connecting? See Agent not connecting.