Argus vs Jcodeharness MCP

A side-by-side look at the Argus and Jcodeharness 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 declaredJcodeharness MCP logoJcodeharness MCPDeveloper Tools · Remote HTTP/SSEA paid remote MCP for OpenAI Codex harness MCP, built to return verdicts, receipts, usage logs, and48FairAuth: not declared

Verdict: choose Argus for developer tools work as a local process; choose Jcodeharness MCP for developer tools over a hosted endpoint. 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

Jcodeharness MCP logoChoose Jcodeharness MCP when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like plan_coding_task, suggest_safe_command, record_test_verdict.
Explore Jcodeharness MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecArgus logoArgusJcodeharness MCP logoJcodeharness MCP
CategoryDeveloper ToolsDeveloper Tools
Quality signal57/100 · Good48/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars50
Directory activity 2 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools94

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 }

Jcodeharness MCP tools 4

  • plan_coding_task
  • suggest_safe_command
  • record_test_verdict
  • read_run_history

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"
      ]
    }
  }
}

Jcodeharness MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "jcodeharness-mcp": {
      "url": "https://jcodeharness.clauxel.com/mcp"
    }
  }
}

Frequently asked questions

Argus is categorized under Developer Tools and uses a local stdio subprocess. Jcodeharness MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Argus for developer tools work and Jcodeharness 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. Jcodeharness MCP has no declared pricing — check the project's own site. 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 jcodeharness-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 2 views, 0 installs and 5 GitHub stars. Jcodeharness MCP has 48/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.