SnagRelay

com.snagrelayPublished by snagrelay.comOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper Tools Security & Monitoring

Server details

Identifier: com.snagrelay/snagrelay
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 11, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to snagrelay.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.snagrelay%2Fsnagrelay.svg)](https://sourceweft.com/mcp/com.snagrelay%2Fsnagrelay?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

SnagRelay gives coding agents bug-report evidence — broken element, console errors, failing requests with bodies — so they can fix issues by ticket key.

What you can do: Read an issue's full context by key: broken element, repro steps, console errors with file and line, requests with bodies, screenshot link
Fetch one full request or response body, or a single console entry, by index
Look up earlier resolved issues on the same screen or endpoint, with the PR that fixed them
List or search issues when no ticket key is known, and check the signed-in account, plan and projects
Write back progress (file being edited) and mark an issue resolved with PR, commit and branch, optionally emailing the reporter
When to use it: Useful when a team collects user bug reports through SnagRelay and wants an agent in Cursor, Claude Code, Codex or another MCP client to pull the captured evidence and propose or ship a targeted fix on a branch.
Requirements: A remote Streamable HTTP endpoint at mcp.snagrelay.com; OAuth sign-in through a browser (no token to copy), or an API token sent as an Authorization Bearer header for headless clients. A SnagRelay account is required; the free plan includes the MCP server, network bodies and one project. Optional URL variants restrict access to read-only or to a single project.

Before you install

The agent receives what the user's widget captured on the page — element, console, network, replay and screenshot — though the server strips secrets such as authorization and cookie headers, API keys, tokens and passwords before delivery. Write tools report progress and mark issues resolved, and marking resolved can email the reporter. Use the read-only URL to block writes; issue visibility is limited by the plan's history window.

Installation

In SourceWeft

Open SnagRelay in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.snagrelay%2Fsnagrelay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "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.

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 <token> to the same URL.

Which 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.

Tools

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.

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>

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.

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.

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.

Source: README.md at commit 21ecc6e

Tools

This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

v1.0.0LatestOct 11, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts