Argus vs Chatpack MCP

A side-by-side look at the Argus and Chatpack MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Argus logoArgusDeveloper Tools · Local subprocess (stdio)Automated web QA via Chrome DevTools MCP — a11y, security, visual, env diff, CI; Aegis redaction.57GoodAuth: not declaredChatpack MCP logoChatpack MCPDeveloper Tools · Local subprocess (stdio)Read-only MCP server for Chatpack documentation, framework setup guides, and React UI block source. Runs locally over stdio with npx -y @chatpack/mcp. Node.js 20 or later; MIT license; no account or API key required.87ExcellentAuth: no auth required

Verdict: choose Argus for developer tools work as a local process; choose Chatpack MCP for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Argus logoChoose Argus when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like argus_audit, argus_audit_full, argus_compare.
Explore Argus

Chatpack MCP logoChoose Chatpack MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like search_docs, get_document, get_integration_guide.
Explore Chatpack MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecArgus logoArgusChatpack MCP logoChatpack MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal57/100 · Good87/100 · Excellent
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listing Verified
GitHub stars5224
Directory activity 1 views 0 installs 0 upvotes 4 views 0 installs 0 upvotes
Tools95

Tools & capabilities

Argus tools 9

  • argus_auditFast pass — JS, network, accessibility, SEO, security, CSS, content
  • argus_audit_fullDeep pass — adds Lighthouse, responsive checks, memory leak detection, hover-state bugs
  • argus_compareDiff dev vs staging — screenshots, findings delta, environment regressions
  • argus_get_contextCapture everything broken on the open tab — with `resolved / new / persisting` diff vs the last snapshot (the fix loop)
  • argus_watch_snapshotSnapshot the open tab without navigating (preserves auth/form state)
  • argus_last_reportReturn last JSON report without re-running
  • argus_design_auditFigma URL → 13 design-token finding types (color, spacing, typography, shadows, etc.)
  • argus_visual_diffScreenshot baseline comparison. Pass `updateBaseline: true` to reset.
  • argus_pr_validateFetch GitHub PR diff → map changed files to affected routes → targeted audit → baseline-aware block decision (blocks on findings the PR *introduces*) + idempotent PR comment + Check Run → `{ blocked, findings, baseline, reporting }

Chatpack MCP tools 5

  • search_docsSearch bundled Chatpack documentation and the authoritative llms reference. Returns document ids, links and matching excerpts with package versions.
  • get_documentRead a complete bundled Chatpack document by id. Use llms for the authoritative integration contract or concepts/errors for troubleshooting.
  • get_integration_guideRetrieve the repository's framework setup guide with authentication guidance and the authoritative llms reference. Examples match the bundled package versions.
  • list_ui_blocksList public runtime exports of @chatpack/ui, including components, providers and utilities. Returns names accepted by get_ui_block.
  • get_ui_blockRetrieve a public @chatpack/ui export's source module and usage guide. Optionally include supporting UI modules and stylesheet. Files are reference source, not a standalone copy-and-paste component.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Argus

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "argus-2": {
      "command": "npx",
      "args": [
        "-y",
        "chrome-devtools-mcp@latest"
      ]
    }
  }
}

Chatpack MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chatpack-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@chatpack/mcp"
      ]
    }
  }
}

Frequently asked questions

Argus is categorized under Developer Tools and uses a local stdio subprocess. Chatpack MCP belongs to Developer Tools and uses a local stdio subprocess. Pick Argus for developer tools work and Chatpack MCP for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Argus has no declared pricing — check the project's own site. Chatpack MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add argus-2 and chatpack-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Argus has a quality signal of 57/100 (Good) with 1 views, 0 installs and 5 GitHub stars. Chatpack MCP has 87/100 (Excellent) with 4 views, 0 installs and 224 GitHub stars.