Qase test management over MCP: 36 task-oriented tools for cases, runs, results, defects and QQL search, hosted at mcp.qase.io or self-run with your own API token.
Summary
Snag's official remote MCP server — hands a coding agent the session replay, console logs, network trace and annotated screenshots captured for a bug, then takes the fix PR link back.
Features
- Remote streamable-HTTP endpoint at mcp.snag.ac/mcp — nothing to host
- Seven tools: six read-only evidence readers plus one PR-link writer
- Session replay, console logs, network requests and reporter annotations per bug
- Test-harness analysis to verify a proposed fix
- Works with Claude Code, Cursor, Windsurf, VS Code, Codex and Gemini CLI
- Deduplicated Jira and GitHub tickets as the source of each bug
- Commits and PRs stay in your own repo — the server never writes code
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
The slowest part of fixing a user-reported bug is usually reconstructing it. Snag's MCP server removes that step: when a user files a bug in one click, Snag captures the session replay, console output, network requests and the reporter's annotated screenshot, and this server hands all of it to whichever coding agent you already use.
It is a remote server over standard streamable HTTP — in Snag's words, "no SDK, no webhook, nothing to host." Point Claude Code, Cursor, Windsurf, VS Code, Codex or Gemini CLI at it, generate a workspace token in Settings and connect.
Seven tools, six of them read-only
get_bug_context— the full captured evidence for a reportget_console_logs— browser console output from the sessionget_network_requests— the network activity around the failureget_bug_annotations— the screenshot regions the reporter marked upget_test_harness_analysis— verification of a proposed fixpost_pr_link— the single write tool, which attaches a pull-request URL back to the ticket
That split is the design point. The server is an evidence feed, not a code-writing agent with commit rights: branches, commits and the pull request all happen in your own repository and infrastructure, and Snag never reaches into it.
Where it sits in the workflow
Snag files deduplicated tickets into Jira and GitHub on capture, so the MCP server picks up from an existing ticket rather than introducing a parallel tracker. Snag's own fix agent runs in a sandbox destroyed after each run and is never trained on customer source code — but this server exists so you can skip it and use your own agent instead.
Pricing runs across five tiers from a free plan with 15 captures a month up to Business at $299/month with 150 fix-runs. Billing is per workspace, with unlimited members and reporters on every plan — so putting the bug reporter in front of non-engineers does not cost extra.
Built by Drew Stockler and operated by Digital Ventures Conglomerate Limited. Best suited to product teams whose testers and support staff file the bugs that engineers then have to reproduce.
Related MCP Servers
Arm's official MCP server for porting and tuning software on Arm — semantic docs search, codebase migration scanning, container architecture checks and LLVM-MCA assembly analysis.
Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.
Context-compression MCP server that shrinks tool outputs, logs, files and RAG chunks before they reach the model, cutting 60-95% of tokens on JSON payloads.