Log inSubmit server
Argus logo

Argus

Audits rendered web apps in Chrome for JavaScript, accessibility, security, performance, visual, and environment issues.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Argus

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "argus-2": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y chrome-devtools-mcp@latest

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.

Overview

The argus MCP server audits rendered web applications through Chrome DevTools, returning structured, severity-ranked findings across JavaScript, network, accessibility, SEO, security, CSS, content, and performance. It supports fast and deep audits, snapshot-based fix tracking, visual comparisons, development-versus-staging diffs, Figma design checks, and GitHub pull request validation. Use it when an agent needs to evaluate browser behavior rather than only inspect source code. Aegis redacts findings at egress boundaries, and the server can run through npx with a Chrome DevTools connection.

Use cases

  • Audit a local web application before committing changes
  • Track resolved and persisting browser findings during an agent fix loop
  • Compare development and staging environments for regressions
  • Validate a GitHub pull request against affected routes
  • Check implementation details against a Figma design

Key features

  • Chrome DevTools-based browser audits
  • Accessibility, security, SEO, performance, and network checks
  • Snapshot-based finding diffs
  • Visual and environment regression comparisons
  • Figma design-token audits
  • GitHub pull request validation

Tools9

What Argus lets your agent do. Expand a tool for its parameters.

Self-reported~247 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 40d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 2Low 0

Scanned 13d ago via OSV.dev · chrome-devtools-mcp@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads7.9MPackage downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed9Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Argus works

What argus MCP server does

The argus MCP server evaluates the application as it appears and behaves in Chrome. It inspects the DOM, console output, network activity, screenshots, performance signals, and other browser-observable data instead of requiring test files. Results are returned as structured findings with critical, warning, or info severity.

Coverage includes uncaught JavaScript errors, failed requests, duplicate API calls, accessibility rules, SEO metadata, insecure browser behavior, CSS problems, visible placeholder content, broken images, responsive layout issues, memory growth, form labeling, font loading, motion preferences, dark-mode gaps, and visual regressions. The server also supports design checks from a Figma URL and comparisons between development and staging environments.

How it works

Argus connects to a running Chrome or Chromium instance through the Chrome DevTools Protocol. The companion chrome-devtools-mcp entry is configured alongside Argus so an MCP client can work with the browser. A typical run points an audit at a local or deployed URL, after which the server gathers browser evidence and returns findings.

The fix loop uses snapshots. argus_watch_snapshot captures the current tab without navigation, preserving authentication and form state. argus_get_context compares the current state with the previous snapshot and separates resolved, new, and persisting findings. argus_last_report returns the previous JSON report without starting another audit.

Aegis redacts findings at egress boundaries.

Setup and configuration

The documented quick start uses npm’s npx, so no package installation is required beforehand. Add an argus MCP entry running npx -y argusqa-os, and add the Chrome DevTools MCP entry running npx -y chrome-devtools-mcp@latest. Launch Chrome with the provided argus-chrome command or start it manually with remote debugging enabled.

After Chrome and the MCP configuration are ready, ask the connected agent to run an audit against a URL such as http://localhost:3000. The argus-doctor command diagnoses setup problems. Optional behavior includes disabling the noise filter with ARGUS_NOISE_FILTER=0 or root-cause annotations with ARGUS_ROOT_CAUSE=0.

Tools and capabilities

The argus MCP server exposes these tools:

  • argus_audit for a fast browser audit.
  • argus_audit_full for deeper checks, including Lighthouse, responsive behavior, memory leaks, and hover states.
  • argus_compare for development-versus-staging screenshots, findings, and environment regressions.
  • argus_get_context, argus_watch_snapshot, and argus_last_report for iterative debugging and report retrieval.
  • argus_design_audit for comparing an implementation with Figma design tokens.
  • argus_visual_diff for screenshot baseline comparisons and baseline updates.
  • argus_pr_validate for mapping GitHub pull request changes to routes, running targeted audits, and producing a baseline-aware block decision, PR comment, and Check Run.

Limitations and notes

It evaluates what the page exposes through the browser, not source code directly. Some checks depend on a reachable local or deployed application, a running Chrome instance, or available GitHub, Figma, and baseline data. The README identifies MIT licensing and describes optional noise filtering and root-cause processing.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Argus

argus is an MCP server that connects an AI agent to Chrome through the Chrome DevTools Protocol and audits rendered web applications. Its main tools cover fast and deep audits, snapshots, visual diffs, development-versus-staging comparisons, Figma design checks, and GitHub pull request validation with structured findings.

Install it through npx by adding `npx -y argusqa-os` as the Argus MCP command. Configure the companion Chrome DevTools MCP entry, then launch Chrome with `npx -y -p argusqa-os argus-chrome` or a remote-debugging command.

Ask the connected MCP agent to run `argus_audit` against the local URL, such as `http://localhost:3000`. Chrome must be running with remote debugging available, and the returned findings are structured and severity-ranked.

Yes. Use `argus_compare` to compare development and staging screenshots, findings, and environment regressions. The comparison is intended to identify differences between the two environments.

Use `argus_pr_validate` to fetch the pull request diff, map changed files to affected routes, run targeted audits, and make a baseline-aware block decision. It also supports an idempotent pull request comment and GitHub Check Run.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewArgus AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/argus-2?style=directory)](https://allmcps.com/mcp/argus-2)
HTML Embed
<a href="https://allmcps.com/mcp/argus-2"><img src="https://allmcps.com/api/badge/argus-2?style=directory" alt="Argus on AllMCPs" /></a>