SnagRelay

com.snagrelay由 snagrelay.com 发布官方发布者v1.0.0更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

SnagRelay 让编程助手按工单号获取缺陷证据——出错的元素、控制台错误、带请求体的失败请求——从而定位并修复问题。

可以做什么
  • 按工单号读取问题完整上下文：出错元素、复现步骤、带文件与行号的控制台错误、含请求体的请求以及截图链接
  • 按索引获取某一条完整的请求或响应体，或单条控制台记录
  • 查询同一页面或接口上此前已解决的问题，以及修复它们的 PR
  • 在没有工单号时列出或搜索问题，并查看当前账号、套餐与可访问项目
  • 回写进度（正在编辑的文件），并用 PR、提交和分支将问题标记为已解决，可选通知报告人
适用场景
适合通过 SnagRelay 收集用户缺陷报告的团队，让 Cursor、Claude Code、Codex 等 MCP 客户端中的助手读取页面捕获的证据，在分支上提出或提交针对性修复。
运行要求
远程 Streamable HTTP 端点 mcp.snagrelay.com；通过浏览器 OAuth 登录（无需复制令牌），无头客户端可使用 API 令牌并以 Authorization Bearer 头发送。需要 SnagRelay 账号，免费套餐包含 MCP 服务器、网络请求体和 1 个项目。可选 URL 变体可限制为只读或仅限单个项目。
安装前请注意
助手会收到用户页面组件捕获的内容：元素、控制台、网络、回放和截图，但服务器会在下发前剥离 authorization 与 cookie 头、API 密钥、令牌、密码等敏感信息。写工具会上报进度并将问题标记为已解决，标记已解决时可能向报告人发送邮件。可用只读 URL 禁止写入；问题可见范围受套餐历史窗口限制。

安装

在 SourceWeft 中

  1. 打开 控制台中的 SnagRelay，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.snagrelay%2Fsnagrelay/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "snagrelay": {
      "type": "http",
      "url": "https://mcp.snagrelay.com/v1"
    }
  }
}

README

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

Links

Website · Docs · Pricing · Support · Privacy · Terms

Contributing

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

来源：README.md，提交 21ecc6e

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Oct 11, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分