Argus vs Jshookmcp
A side-by-side look at the Argus and Jshookmcp MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Argus for developer tools work as a local process; choose Jshookmcp 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?
Choose 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.
Choose Jshookmcp when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 57/100 · Good | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 2,060 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 9 | Not listed |
| Full listing | View Argus | View Jshookmcp |
Tools & capabilities
Argus tools 9
argus_auditFast pass — JS, network, accessibility, SEO, security, CSS, contentargus_audit_fullDeep pass — adds Lighthouse, responsive checks, memory leak detection, hover-state bugsargus_compareDiff dev vs staging — screenshots, findings delta, environment regressionsargus_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-runningargus_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 }
Jshookmcp tools
No tool names declared yet. Check the project README from the listing page.
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": {
"argus-2": {
"command": "npx",
"args": [
"-y",
"chrome-devtools-mcp@latest"
]
}
}
}
Jshookmcp
{
"mcpServers": {
"jshookmcp": {
"command": "npx",
"args": [
"-y",
"@jshookmcp/jshook@latest"
]
}
}
}
Frequently asked questions
Argus is categorized under Developer Tools and uses a local stdio subprocess. Jshookmcp belongs to Developer Tools and uses a local stdio subprocess. Pick Argus for developer tools work and Jshookmcp 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. Jshookmcp 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 jshookmcp 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. Jshookmcp has 52/100 (Good) with 2 views, 0 installs and 2,060 GitHub stars.