QA Wrap bridge runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 24 Oct 2026.
Read-only MCP server: a coding agent reads test sessions recorded in QA Wrap. Local only.
What the code does
We read the source, 3 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
return subprocess.run(args, capture_output=True, text=True,
const read = (rel) => fs.readFileSync(path.join(ROOT, rel), 'utf8');
return subprocess.run(args, capture_output=True, text=True,
const r = spawnSync(bin, args, {
const maths = new Function(
assert.match(body, /btn\.disabled = true;/, `#${id} can be pressed twice while the first delete is in flight`);
assert.match(body, /btn\.textContent = 'Deleting…';/, `#${id} says nothing while it works`);
const base = String(destination.url || 'https://api.telegram.org').trim().replace(/\/+$/, '');
k.box.innerHTML = svg;
out({ homedir: os.homedir(), tmpdir: os.tmpdir(), credRead, realCredRead, secretVars: ['OPENROUTER_API_KEY', 'HTTPS_PROXY', 'QAW_JIRA_ENV', 'JIRA_TOKEN', 'GITHUB_TOKEN'].filter((k) => process.env[k] !== undefined), keys: Object.keys(process.env).length, nodeOptions: process.env.NODE_OPTIONS });
for (const f of fs.readdirSync(path.join(EXT, dir)).filter((x) => x.endsWith('.js'))) if (read(EXT, dir, f).includes('reviewUrl')) hits.push(`${dir}/${f}`);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check QA Wrap bridge every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add qa-wrap-bridge -- npx -y qa-wrap-bridge{
"mcpServers": {
"qa-wrap-bridge": {
"command": "npx",
"args": [
"-y",
"qa-wrap-bridge"
]
}
}
}[mcp_servers.qa-wrap-bridge]
command = "npx"
args = ["-y", "qa-wrap-bridge"]{
"mcpServers": {
"qa-wrap-bridge": {
"command": "npx",
"args": [
"-y",
"qa-wrap-bridge"
]
}
}
}{
"servers": {
"qa-wrap-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"qa-wrap-bridge"
]
}
}
}Alternatives to QA Wrap bridge
same job, measured the same wayRead-only lookup of tested agent tools and MCP servers: scores, test evidence, deprecation.
MCP server for visual regression testing: triage a PR's UI diffs from your coding agent.
Read-only tools to inspect your agent setup: list MCP servers, flag unpinned ones, test a policy.
Read-only evidence for the tools agents run: MCP server records, coverage and policy.
Internal test MCP server for local dev and Bifrost integration testing.
A local MCP server with full Figma REST API coverage.
MCP server index: newest agent tools listed. $0.01/query. Register in-session — free testnet funds.
Local test execution and coverage summaries for onboarding agents.
QA Wrap bridge — questions
Answers built from our own checks of this server.