REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Bug reports your coding agent can fix: real element, console errors, failing requests with bodies.
Pick the AI app you use, then copy the settings.
Passed 5/5 checks · What you ask goes through the maker’s server (mcp.snagrelay.com)
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude · about 2 min
No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it
CustomizeConnectors
Copy each value into the field with the same name in Claude, then click Continue
Checking the commands · copy buttons appear once they pass
Checking the commands · copy buttons appear once they pass
Leave Authentication as Claude detected it, then click Add
+ConnectorsSnagRelay
Use SnagRelay and tell me what you can do for me, then show me one thing✓ If Claude says it is using SnagRelay or shows a SnagRelay tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with ChatGPT, depending on your plan
Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only
Plugins+Add custom MCP server
Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin
Checking the commands · copy buttons appear once they pass
Checking the commands · copy buttons appear once they pass
Start a new chat and pick SnagRelay from your plugins before typing
Use SnagRelay and tell me what you can do for me, then show me one thing✓ If ChatGPT says it is using SnagRelay or shows a SnagRelay tool in the answer, you are connected
Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Claude Code · about 2 min
No key, nothing to install
Mac: press Command+Space and type Terminal · Windows: open PowerShell
Checking the commands · copy buttons appear once they pass
You should see SnagRelay listed as connected
Use SnagRelay and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using SnagRelay or shows a SnagRelay tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor · about 2 min
No key, nothing to install
Checking the commands · copy buttons appear once they pass
Use SnagRelay and tell me what you can do for me, then show me one thing✓ If Cursor says it is using SnagRelay or shows a SnagRelay tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code · about 2 min
No key, nothing to install
Checking the commands · copy buttons appear once they pass
Use SnagRelay and tell me what you can do for me, then show me one thing✓ If VS Code says it is using SnagRelay or shows a SnagRelay tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
Address for apps that connect over the web
Checking the commands · copy buttons appear once they pass
JSON settings are under “For developers” below
Claude Code
Checking the commands · copy buttons appear once they pass
Cursor (~/.cursor/mcp.json)
Checking the commands · copy buttons appear once they pass
VS Code (mcp.json)
Checking the commands · copy buttons appear once they pass
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Connect over the internet in
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 13, 2026
The registry name was verified against the domain snagrelay.com (the registry checks domain ownership)
Code last changed 32 days ago
Uses MIT
Responded in 251 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed 32 days ago, and the latest version (1.0.0) reached the registry 32 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).
In the same category: REA, GitHub, Serena MCP: the IDE for your agent
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Your users find the bugs. Your agent fixes them. Give Cursor, Claude Code or Codex a ticket key and it reads the evidence a human debugger would open: the broken element, console errors with file and line, failing requests with their request and response bodies, repro steps and a short replay.
This repo is the listing and distribution repo for the SnagRelay MCP server. It holds the plugin manifests for each agent platform, the shared skills and the registry entry. The MCP server itself is hosted by SnagRelay at https://mcp.snagrelay.com/v1.
Sign-in is OAuth. A SnagRelay page opens in your browser, you click Allow, and there is no token to copy.
| Client | Install |
|---|---|
| Cursor | Open Customize → Marketplace, search SnagRelay, install, then click Needs authentication on the snagrelay MCP server |
| Claude Code | claude plugin marketplace add snagrelay/agent-plugin then claude plugin install snagrelay@snagrelay. Run /mcp and authenticate snagrelay |
| Codex | codex plugin marketplace add snagrelay/agent-plugin then codex plugin add snagrelay@snagrelay. Sign in with codex mcp login snagrelay |
| Lovable | Settings → Connectors → search SnagRelay, or add a custom MCP server with the URL below |
| Bolt | Add a custom remote MCP connector with the URL below |
| Replit | Add a custom MCP server with the URL below |
| Anything else | Point any Streamable HTTP MCP client at https://mcp.snagrelay.com/v1 |
Lovable, Bolt and Replit guides are being written; the custom-connector route works today.
For CI, scripts and other headless clients, create an API token in SnagRelay (Settings → API tokens) and send Authorization: Bearer to the same URL.
All four share one server and one sign-in. Pick the narrowest one that fits.
| URL | Use it when |
|---|---|
https://mcp.snagrelay.com/v1 | You work across projects. The default |
https://mcp.snagrelay.com/v1/readonly | You want the agent to read issues but never write. The write tools (report_progress, mark_issue_resolved) are removed and blocked. Good for security-conscious teams and shared machines |
https://mcp.snagrelay.com/v1/{projectId} | This repo belongs to one SnagRelay project. Hard-scoped, so the agent cannot see other projects |
https://mcp.snagrelay.com/v1/{projectId}/readonly | Both of the above |
{projectId} is the number from whoami, or from the project's URL in SnagRelay.
| Tool | Access | What it does |
|---|---|---|
get_issue_context | read | Full context of one issue by key: the element, repro steps, console errors with file and line, requests with bodies, and a screenshot resource link |
get_issue_payload | read | One full request or response body, or one console entry, by the index from get_issue_context |
get_related_history | read | Earlier resolved issues on the same screen or endpoint, with the PR that fixed them |
find_issues | read | List or search issues when you have no key |
whoami | read | Signed-in account, plan and accessible projects |
report_progress | write | Tells SnagRelay which file the agent is editing |
mark_issue_resolved | write | Marks an issue resolved with the PR, commit and branch. Optionally emails the reporter |
One resource: screenshot, the issue's screenshot, read with resources/read.
Every tool carries MCP annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint). None is destructive. The agent is instructed not to call mark_issue_resolved before you have reviewed the fix.
fix PROJ-123
-> get_issue_context("PROJ-123") -> reads the failing request and its response body, the console error with file and line, the repro steps -> get_related_history: has this broken before, and what fixed it? -> proposes a targeted fix on feature/PROJ-123-
Six skills, written once in skills/ and used by every client.
| Skill | What it does |
|---|---|
fix-issue | Load context and fix a SnagRelay issue on a branch, then stop for your review |
open-pr | Branch feature/{key}-{summary}, PR title [{key}] {type}: {description}, full description |
resolve-issue | Commit and open a PR if needed, then mark the issue resolved |
triage | List open issues so you can pick one |
connect | Diagnose a broken MCP connection |
scope | When the agent may (and may not) call SnagRelay |
Cursor also gets rules/snagrelay-context.mdc, which tells the agent to load an issue's context before proposing a fix.
Claude Code namespaces plugin skills: run /snagrelay:fix-issue PROJ-123. In Cursor and Codex, say fix PROJ-123 or use /fix-issue.
The agent receives what your users' widget captured on the page: element, console, network, replay and screenshot. Secrets are stripped on the server before anything reaches the agent: authorization and cookie headers, API keys, tokens, passwords, CSRF values, secret-looking query and form parameters, bearer tokens, JWTs and long hex or base64 strings. Issues are visible to the agent only as long as your plan's history window (history_days) allows. See TELEMETRY.md for the full list and SECURITY.md to report a vulnerability.
This repo contains no code that runs on your machine: only manifests, skills, a rule and a remote MCP URL.
Website · Docs · Pricing · Support · Privacy · Terms
Edit skills/ and rules/, never the manifests by hand: see AGENTS.md. MIT licensed.