VS Code / Cursor Extension
Browse tracker tickets and fix SnagRelay-captured bugs from your editor.
The SnagRelay extension for VS Code and Cursor is a developer-facing tool for fixing bugs, not reporting them. The sidebar is To do / Doing / Done — tickets on the connected tracker, filtered to you. Fix it starts a coding-agent session with screenshot, console, and HTTP context when the ticket was captured by SnagRelay.
Install
Search for SnagRelay in the VS Code Marketplace or Open VSX (for Cursor), or install
the .vsix file directly.
Sign in
Project owners: open the SnagRelay sidebar and click Sign in as owner (or run SnagRelay: Sign In). That uses your dashboard account — do not paste a token.
Invited teammates: open the magic link from Team, then Authenticate VS Code / Cursor on Your access. The editor stores a grant. It should connect, not open a “Fix this ticket” chat.
There is no token in mcp.json. See
API Keys & Tokens.
Bind this repo
If the folder has no MCP config yet, pick a SnagRelay project after sign-in, or copy
the snippet from the project MCP tab. The extension writes .cursor/mcp.json or
.vscode/mcp.json (safe to commit — no secret). That URL is which project this
workspace is.
Enable the snagrelay MCP server (Cursor Settings → MCP), then start working.
You must be invited from the project Team list (or be the owner) or the board stays empty.
Fix a ticket
Click a ticket for details. Fix it moves the card to Doing and implements the bug
on a new local feature/… branch. It does not git push, open a PR, or mark the
issue resolved. Open PR is the later step — push, create the PR, and comment the
link on the tracker.
Widget-captured tickets load evidence via MCP get_issue_context. Tracker-only
tickets already have title, description, and attachments in the panel — don’t call
other SnagRelay issue tools for those.
MCP under the hood
The extension talks to SnagRelay over the MCP protocol.
Owners use a personal access token from Sign in. Teammates use a grant from the access
page. The committed mcp.json only has the project URL.
| Tool | Purpose |
|---|---|
get_issue_context | Screenshot, console, HTTP summaries — SnagRelay-captured tickets |
find_issues | List SnagRelay-captured issues when the user asked to list them (no key) |
mark_issue_resolved | Close the ticket after the reporter tests |
get_related_history | Past fixes for the same selector / endpoint / group |
If you use a different MCP client, paste the same URL from the project MCP tab — see AI Agent (MCP).
Agency plan feature
The AI Agent / MCP integration (and therefore this extension's core workflow) requires a plan that includes the MCP agent (Agency). Chrome reporting still works for invited Team members without MCP.