BugScout MCP Server
Integrates with GitHub Actions to run bug scans on PR preview deployments and comment findings directly on PRs.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BugScout MCP Serverscan example.com for bugs"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
🐛 BugScout — Autonomous Web QA Agent
Point it at a URL. It finds your bugs. It writes the regression tests.
BugScout is an AI-powered web QA agent that autonomously explores any web application, maps its user flows, detects bugs (console errors, broken links, a11y violations, layout issues, dead buttons), and generates production-ready Playwright regression suites — all from a single command.
Why BugScout?
One command — point it at a URL and get a markdown report with screenshots
Finds real bugs — console errors, 4xx/5xx, broken links, a11y violations, dead buttons, layout overflow
Generates Playwright tests — deterministic, self-validating specs from discovered user flows
Plays well with CI — GitHub Action for PR previews, regression diffing
MCP-native — browser control exposed as MCP tools (works with Claude, Cursor, any MCP client)
Accessibility-first — snapshot via accessibility tree, not raw DOM (cheaper + more robust)
Related MCP server: MCP Playwright Server
Quick Start
git clone https://github.com/mhmdtaha091/bugscout.git
cd bugscout
npm install
npx playwright install chromium
# Scan a site
npm run dev -- https://example.com
# With options
npm run dev -- https://example.com \
--output ./qa-results \
--max-pages 30 \
--agentic \
--generate-testsNot on npm yet — the
bugscoutname on the registry belongs to an unrelated package, so this will ship under a scoped name. Until then, clone and run.
How It Works
Target URL
│
▼
Explorer agent ──── Playwright (CDP) — crawls same-origin pages
│ accessibility-tree-first, screenshot on ambiguity
▼
Flow map ─── pages, interactive elements, forms, links
│
├──► Bug detector — console errors, 4xx/5xx, broken links,
│ a11y violations, dead buttons, layout overflow
│
├──► Test generator — deterministic Playwright specs per flow
│ (role/label > testid > CSS selector strategy)
│
└──► Reporter — markdown report + screenshotsCLI Options
Flag | Description | Default |
| Output directory |
|
| Max pages to crawl | 50 |
| Max crawl depth | 5 |
| Show browser window |
|
| Page timeout in seconds | 30 |
| LLM-driven agentic exploration (v1) |
|
| Generate Playwright specs (requires |
|
| LLM provider: |
|
| LLM model |
|
| API base URL for openai-compatible providers | — |
| API key (or | env var |
Architecture
src/
├── cli.ts — CLI entry point (commander)
├── explorer.ts — Playwright crawler + flow map builder
├── bug-detector.ts — Cheap bug detectors (no LLM required)
├── reporter.ts — Markdown report + console summary
├── agent.ts — LLM-driven agentic exploration (v1)
├── mcp-server.ts — MCP server: browser as tools
├── test-generator.ts — Deterministic Playwright spec generation
├── ci.ts — GitHub Action + regression diff + security stub
└── types.ts — Shared TypeScript typesMCP Server
BugScout exposes a Playwright browser as MCP tools:
npx tsx src/mcp-server.tsTools: navigate, snapshot (a11y tree + screenshot), click, fill, evaluate, console_logs, network_errors, close
Use it directly with Claude Code or any MCP-compatible client.
CI Integration
# Generate a GitHub Actions workflow
npx bugscout ci --init
# Compare two scan results for regressions
npx bugscout diff baseline.json current.jsonThe generated workflow runs on PR preview deployments, comments findings directly on the PR.
Roadmap
Version | What | Status |
v0 | Explorer + cheap bug detection + markdown reports | ✅ Done |
v1 | Agentic exploration + Playwright test generation | ✅ Done |
v2 | Real-world OSS testing + repro GIFs + upstream bugs | 🔜 Pending |
v3 | CI mode + regression diffing + security extension | ✅ Done |
Real-World Scans
BugScout has been tested against real, high-traffic production sites:
Site | Pages | Bugs Found | High | Medium | Low | Duration |
Hacker News (news.ycombinator.com) | 10 | 194 | 13 | 174 | 7 | 57s |
Reddit (old.reddit.com) | 20 | 445 | 40 | 405 | — | 214s |
Bugs detected include: missing accessible labels (a11y), layout overflow on narrow viewports, broken intra-site links, and console errors.
Run the agentic mode (
--agentic) to enable LLM-driven exploration and automatic Playwright test generation from discovered flows.
Metrics
All numbers published are real and verifiable:
639 total bugs found across 2 production sites (30 pages, 3,600+ links)
Pages crawled per scan, cost + wall-clock time, and bug severity breakdown
Upcoming: bugs filed → confirmed by upstream maintainers; test flake rate
Tech Stack
TypeScript end-to-end
Playwright for browser automation (Chromium via CDP)
MCP SDK (
@modelcontextprotocol/sdk) for tool exposureMulti-provider LLM layer for agentic exploration + test generation (v1+) — Anthropic, OpenAI, Gemini, or any OpenAI-compatible endpoint (DeepSeek, Ollama)
axe-core for accessibility violation detection
Responsible Use
Only scan sites you own or have explicit authorization to test. The default
crawl is navigation-only — it stays same-origin, maps forms without submitting
them, and clicks nothing. Agentic mode (--agentic) does interact with pages,
so reserve it for targets you control. Crawling still generates real traffic;
the public-site scans above were navigation-only crawls of publicly served
pages.
License
MIT — Muhammad Taha Khan
639 bugs found across 2 production sites. Real numbers, real scans.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseBqualityDmaintenancePlaywright wrapper for MCP that enables LLM-powered clients to control a browser for automation tasks.Last updated101
- Alicense-qualityDmaintenanceEnables AI assistants to control web browsers through Playwright automation, providing 50+ tools for navigation, interaction, testing, accessibility audits, and visual testing across Chromium, Firefox, and WebKit.Last updated14MIT
- Flicense-qualityCmaintenanceExposes Playwright browser automation as MCP tools, enabling AI assistants to control a real browser tab-by-tab for form filling, navigation, and more, while preserving the user's active session.Last updated
- Alicense-qualityDmaintenanceProvides browser automation capabilities using Playwright, allowing LLMs to interact with web pages through structured accessibility snapshots without needing vision models.Last updated6,116,0751Apache 2.0
Related MCP Connectors
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
Live browser debugging for AI assistants — DOM, console, network via MCP.
Browser-backed QA with evidence and fix-ready reports for coding agents.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mhmdtaha091/bugscout'
If you have feedback or need assistance with the MCP directory API, please join our Discord server