Skip to main content
MCP server CX Codex

argus — Claude Code MCP server: audits and setup

Argus runs browser QA against a live Chrome instance, covering accessibility, security, network, and visual issues. Use it to inspect a local app through MCP.

Install into Claude Code · Platform CLI All methods and platforms ↓
claude mcp add --env TARGET_DEV_URL=<TARGET_DEV_URL> --env TARGET_STAGING_URL=<TARGET_STAGING_URL> --env SLACK_BOT_TOKEN=<SLACK_BOT_TOKEN> --env FIGMA_API_TOKEN=<FIGMA_API_TOKEN> --env ARGUS_REDACT_SENSITIVE=<ARGUS_REDACT_SENSITIVE> --transport stdio argus -- npx -y argusqa-os
Open on GitHub

What argus does

Argus gives an AI coding agent a Chrome-based QA pass through Chrome DevTools MCP. It inspects the rendered application rather than source files, checking the DOM, console output, network activity, and screenshots. The server covers 67 audit categories and 149 finding types, including JavaScript failures, API errors, accessibility gaps, SEO issues, CSS problems, form defects, memory growth, and visual regressions.

Its workflow is built around repeated checks: run an audit, fix the reported issues, then compare the next result. argus_get_context uses the earlier snapshot to separate resolved, new, and still-open findings. No test files are required for these audits. Aegis redacts sensitive findings before they reach the agent by default.

You need Chrome, Chrome DevTools MCP, and a running application URL such as http://localhost:3000. The server is launched with npx; connection settings can include TARGET_DEV_URL, SLACK_BOT_TOKEN, and FIGMA_API_TOKEN. Without Chrome DevTools MCP, Argus cannot perform its browser audit.

What it helps with

  • inspect JavaScript failures in a rendered app
  • trace API errors and repeated network calls
  • check accessibility and form requirements
  • compare findings across audit runs
  • redact sensitive details before agent review

Example prompts for the agent

  • Run argus_audit on http://localhost:3000 and group the findings by severity.
  • Audit the checkout page with argus_audit and check its network and accessibility issues.
  • After the fixes, call argus_get_context to compare this run with the previous snapshot.

How to install argus

Platform CLI

claude mcp add --env TARGET_DEV_URL=<TARGET_DEV_URL> --env TARGET_STAGING_URL=<TARGET_STAGING_URL> --env SLACK_BOT_TOKEN=<SLACK_BOT_TOKEN> --env FIGMA_API_TOKEN=<FIGMA_API_TOKEN> --env ARGUS_REDACT_SENSITIVE=<ARGUS_REDACT_SENSITIVE> --transport stdio argus -- npx -y argusqa-os

Replace <…> with your own values

Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more

Questions about argus

How do I install argus in Claude Code?

Run `claude mcp add argus -e TARGET_DEV_URL=<TARGET_DEV_URL> -e SLACK_BOT_TOKEN=<SLACK_BOT_TOKEN> -e FIGMA_API_TOKEN=<FIGMA_API_TOKEN> -- npx -y argusqa-os`.

What does argus do?

Argus audits a rendered web application in Chrome and returns structured findings for JavaScript, network, accessibility, security, performance, and visual behavior. A later call can compare the result with an earlier snapshot.

What does argus need to run?

It needs Chrome, Chrome DevTools MCP, and a URL for the running application. The Claude Code setup uses npx and the environment variables shown in the install command.

Similar MCP servers

All MCP servers for Testing and QA →

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor