SnagRelay MCP server
Commit 11 Okt 2026Memungkinkan coding agent untuk mengakses bug report termasuk error console, network request yang gagal beserta body-nya, dan langkah-langkah reproduksi untuk mengotomatisasi perbaikan.
Juga dikenal sebagai snagrelay/agent-plugin, agent-plugin
- Stars
- 0
- Tools
- 7
- Unduhan, 30 hari
- —
- Versi terbaru
- 1.0.0
- Commit terakhir
- 11 Okt 2026
- Lisensi
- MIT
Apa itu SnagRelay MCP?
Memungkinkan coding agent untuk mengakses bug report termasuk error console, network request yang gagal beserta body-nya, dan langkah-langkah reproduksi untuk mengotomatisasi perbaikan. Server ini menyediakan 7 tool, seperti get_issue_context, get_issue_payload, get_related_history.
Ringkasan dibuat dari README proyek
Tentang SnagRelay MCP server
SnagRelay memungkinkan otomatisasi perbaikan bug dengan memberikan akses langsung kepada coding agent ke error yang dilaporkan pengguna. Developer yang menggunakan Cursor, Claude Code, Codex, atau Lovable dapat memberikan ticket key kepada AI agent untuk mengambil bukti spesifik yang dibutuhkan untuk debugging. Ini mencakup error console dengan nomor file dan baris yang akurat, langkah-langkah reproduksi, serta network request yang gagal yang menyertakan request dan response body.
User dapat terhubung via OAuth melalui proses sign-in berbasis browser, sehingga tidak perlu menyalin token secara manual. Server ini dihosting secara remote, dan tim dapat memilih antara URL multi-project default, URL spesifik proyek, atau versi read-only yang mencegah agent menggunakan write tools seperti report_progress atau mark_issue_resolved. Untuk lingkungan headless atau script CI, autentikasi ditangani melalui API token.
Selain sekadar membaca, server ini menyediakan tools untuk menemukan issue, mengambil riwayat terkait dari perbaikan sebelumnya, dan mengelola siklus resolusi. Server ini juga menyertakan skill bawaan untuk membantu agent melakukan triage pada issue yang terbuka atau membuka pull request pada branch tertentu setelah perbaikan siap.
Apa yang bisa Anda lakukan dengannya
- 1Automate bug reproductionBerikan konteks bug secara lengkap kepada AI agent, termasuk elemen yang rusak dan langkah-langkah reproduksinya.
- 2Debug network failuresIzinkan agent untuk memeriksa data spesifik yang menyebabkan kegagalan pada request atau response.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal SnagRelay MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal SnagRelay MCP di Claude Code
$ claude mcp add --transport http agent-plugin https://mcp.snagrelay.com/v1Instal SnagRelay MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agent-plugin": {
"url": "https://mcp.snagrelay.com/v1"
}
}
}Instal SnagRelay MCP di VS Code
.vscode/mcp.json
{
"servers": {
"agent-plugin": {
"type": "http",
"url": "https://mcp.snagrelay.com/v1"
}
}
}Instal SnagRelay MCP di VS Code CLI
$ code --add-mcp '{"name":"agent-plugin","type":"http","url":"https://mcp.snagrelay.com/v1"}'Instal SnagRelay MCP di Codex
$ codex mcp add agent-plugin --url https://mcp.snagrelay.com/v1Instal SnagRelay MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.agent-plugin] url = "https://mcp.snagrelay.com/v1"
Instal SnagRelay MCP di Gemini CLI
$ gemini mcp add -s user --transport http agent-plugin https://mcp.snagrelay.com/v1Instal SnagRelay MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"agent-plugin": {
"url": "https://mcp.snagrelay.com/v1",
"type": "http"
}
}
}Tool SnagRelay MCP 7
Terdeteksi dari READMEget_issue_contextget_issue_payloadget_related_historyfind_issueswhoamireport_progressmark_issue_resolved
| get_issue_context | — | |
| get_issue_payload | — | |
| get_related_history | — | |
| find_issues | — | |
| whoami | — | |
| report_progress | — | |
| mark_issue_resolved | — |
Pengecekan otomatis
Berjalan 15 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkausnagrelay/agent-plugin is public and reachablegithub.com/snagrelay/agent-plugin ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-10-11github.com/snagrelay/agent-plugin ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model7 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelNo tool named like delete, drop or execLolos
- Endpoint remote merespons handshake MCPHTTPS endpoint answered 401 (sign-in required)Lolos
README
Lihat di GitHubSnagRelay 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>
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.
Pertanyaan tentang SnagRelay MCP
Bagaimana cara menambahkan SnagRelay MCP ke Claude Code?
Jalankan claude mcp add --transport http agent-plugin https://mcp.snagrelay.com/v1 di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan SnagRelay MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Tool apa yang disediakan SnagRelay MCP?
Server ini menyediakan 7 tool, termasuk get_issue_context, get_issue_payload, get_related_history, find_issues, whoami.
Bisakah saya membatasi agent agar hanya bisa membaca bug report tanpa mengizinkannya melakukan modifikasi?
Bisa, Anda dapat menggunakan URL readonly yang akan menghapus write tools seperti report_progress dan mark_issue_resolved.
Apakah agent dapat melihat informasi sensitif seperti password atau API key?
Tidak, data rahasia seperti authorization headers, cookies, dan token akan dihapus di sisi server sebelum data sampai ke agent.
Bukti debugging seperti apa yang diterima oleh agent?
Agent akan menerima elemen yang rusak, error console lengkap dengan nomor file dan baris, network request beserta body-nya, langkah-langkah reproduksi, dan link screenshot.