Argus
Run automated web QA—JS errors, accessibility, security, visuals, and env diffs—from your agent before merge or release.
Overview
io.github.ironclawdevs27/argus is an MCP server for the Ship phase that runs automated web QA via Chrome DevTools MCP including a11y, security, visual, and env-diff reporting.
What is this MCP server?
- npm stdio package argusqa-os v9.6.6 wired to Chrome DevTools MCP
- Covers JS console, accessibility, security, visual, and environment diff checks
- Requires TARGET_DEV_URL; optional TARGET_STAGING_URL for dev vs staging compare
- Optional Figma token enables design fidelity audit with 13 finding types
- Slack bot token posts reports; omit token for local report.html output
- Version 9.6.6; npm identifier argusqa-os; stdio transport
- Required env TARGET_DEV_URL; optional staging, Figma, and Slack tokens
- Design fidelity audit documents 13 finding types when FIGMA_API_TOKEN is set
Community signal: 5 GitHub stars.
What problem does it solve?
Manual pre-release checks miss console errors, accessibility regressions, and staging drift until users or CI catch them after deploy.
Who is it for?
Indie devs shipping web apps who want Chrome-backed QA, optional Figma fidelity checks, and Slack or HTML reports from the same agent session.
Skip if: Pure API backends with no browser surface, or teams unwilling to run Chrome DevTools MCP and required TARGET_DEV_URL setup.
What do I get? / Deliverables
After you configure Argus MCP with your dev and staging URLs, your agent can execute structured audits and deliver Slack or local HTML reports before you ship.
- Multi-category web audit passes (JS, a11y, security, visual, env diff)
- Slack-posted QA summaries or local report.html
- Optional Figma-vs-DOM fidelity findings (13 types when token set)
Recommended MCP Servers
Journey fit
Argus is a pre-release quality gate for web apps, which belongs on ship rather than initial product research or growth analytics. Testing is the primary shelf because it drives Chrome DevTools-based audits, comparisons, and CI-style reporting workflows.
How it compares
Browser QA automation MCP, not a unit-test runner skill for isolated functions.
Common Questions / FAQ
Who is io.github.ironclawdevs27/argus for?
Solo builders and small frontend teams who need agent-triggered web audits covering JS, a11y, security, visuals, and environment diffs before release.
When should I use io.github.ironclawdevs27/argus?
Use it in ship testing when a dev or staging URL is live and you want automated Argus reports in Slack or report.html before merging or deploying.
How do I add io.github.ironclawdevs27/argus to my agent?
Install npm package argusqa-os v9.6.6 as a stdio MCP server, set required TARGET_DEV_URL, optional TARGET_STAGING_URL, FIGMA_API_TOKEN, and SLACK_BOT_TOKEN, with Chrome DevTools MCP available.