English Français العربية

SnagRelay

السجل الرسمي أدوات المطورين

Bug reports your coding agent can fix: real element, console errors, failing requests with bodies.

الشيفرة المصدرية الموقع التوثيق

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http snagrelay 'https://mcp.snagrelay.com/v1'
إعداد JSON (Claude Desktop وCursor وVS Code) 
{
    "mcpServers": {
        "snagrelay": {
            "type": "http",
            "url": "https://mcp.snagrelay.com/v1"
        }
    }
}

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. SnagRelay for coding agents
  2. Connect
  3. Which URL?
  4. Tools
  5. Usage
  6. Skills
  7. Data and privacy
  8. Requirements
  9. Links
  10. Contributing

SnagRelay for coding agents

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.

Connect

Sign-in is OAuth. A SnagRelay page opens in your browser, you click Allow, and there is no token to copy.

ClientInstall
CursorOpen Customize → Marketplace, search SnagRelay, install, then click Needs authentication on the snagrelay MCP server
Claude Codeclaude plugin marketplace add snagrelay/agent-plugin then claude plugin install snagrelay@snagrelay. Run /mcp and authenticate snagrelay
Codexcodex plugin marketplace add snagrelay/agent-plugin then codex plugin add snagrelay@snagrelay. Sign in with codex mcp login snagrelay
LovableSettings → Connectors → search SnagRelay, or add a custom MCP server with the URL below
BoltAdd a custom remote MCP connector with the URL below
ReplitAdd a custom MCP server with the URL below
Anything elsePoint 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 <token> to the same URL.

Which URL?

All four share one server and one sign-in. Pick the narrowest one that fits.

URLUse it when
https://mcp.snagrelay.com/v1You work across projects. The default
https://mcp.snagrelay.com/v1/readonlyYou 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}/readonlyBoth of the above

{projectId} is the number from whoami, or from the project's URL in SnagRelay.

Tools

ToolAccessWhat it does
get_issue_contextreadFull 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_payloadreadOne full request or response body, or one console entry, by the index from get_issue_context
get_related_historyreadEarlier resolved issues on the same screen or endpoint, with the PR that fixed them
find_issuesreadList or search issues when you have no key
whoamireadSigned-in account, plan and accessible projects
report_progresswriteTells SnagRelay which file the agent is editing
mark_issue_resolvedwriteMarks 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.

Usage

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-<summary>

Skills

Six skills, written once in skills/ and used by every client.

SkillWhat it does
fix-issueLoad context and fix a SnagRelay issue on a branch, then stop for your review
open-prBranch feature/{key}-{summary}, PR title [{key}] {type}: {description}, full description
resolve-issueCommit and open a PR if needed, then mark the issue resolved
triageList open issues so you can pick one
connectDiagnose a broken MCP connection
scopeWhen 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.

Data and privacy

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.

Requirements

  • A SnagRelay account. The free plan includes the MCP server, network bodies and 1 project. See pricing
  • Cursor, Claude Code, Codex, or any MCP client that supports Streamable HTTP with OAuth

Website · Docs · Pricing · Support · Privacy · Terms

Contributing

Edit skills/ and rules/, never the manifests by hand: see AGENTS.md. MIT licensed.

الأسئلة الشائعة

ما هو SnagRelay؟

Bug reports your coding agent can fix: real element, console errors, failing requests with bodies.

كيف أثبّت SnagRelay؟

يعمل كخادم بعيد. في Claude Code: claude mcp add --transport http snagrelay 'https://mcp.snagrelay.com/v1'. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج SnagRelay إلى مفتاح API؟

لا يذكر إدراجه في السجل أي مفتاح أو سر إلزامي. قد تتطلب بعض الميزات حسابًا لدى الخدمة التي يتصل بها.

هل SnagRelay مفتوح المصدر؟

نعم. شيفرته متاحة على GitHub بترخيص MIT.

من يصون SnagRelay؟

ينشره snagrelay. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.