Argus — Testing for Coding Agents

Name: Argus — Testing for Coding Agents
Author: chriswu727

by chriswu727version 0.12.1i★ –iRuns on your computer

Registry nameio.github.chriswu727/argus

Install

Overview

Description from the maker (original English)

Testing MCP for coding agents: exercise real user journeys, find bugs, verify them with evidence.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "argus": {
      "command": "uvx",
      "args": [
        "argus-testing"
      ]
    }
  }
}

Run this in your terminal

claude mcp add argus -- uvx argus-testing

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "argus": {
      "command": "uvx",
      "args": [
        "argus-testing"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "argus": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "argus-testing"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account chriswu727, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32655 servers in this category
Published to the registry more recently than 96% of the other 32655 servers in this category
Basic checks equal to or better than 100% of the other 32655 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Argus — Testing for Coding Agents safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.12.1) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, SuperCollider

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago

Install

SuperCollider

by Tok

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Argus

Browser testing for your coding agent.

Quick start · What you get · Engineering · Documentation · Product page

Argus is an MCP testing server for Claude Code, Codex, Cursor and other coding agents. It gives your existing agent browser tools to exercise your app, check suspected bugs and produce reports with evidence. The agent decides what to test; Argus handles browser actions, repeatable checks and the results.

Test my web app at http://localhost:3000 and look for bugs.

Your agent can explore user flows, inspect what changed after each action and recheck suspected failures on a fresh page load. You can also give it specific goals, such as testing account settings or checking whether saved data survives a refresh.

What you get

A report you can act on. Findings include expected and actual behavior, reproduction steps, screenshots and verification results. Reports also show which testing goals were exercised, blocked or left unfinished.
A separate verification step. Argus rechecks the specified symptom before marking it reproduced. Observations and inconclusive checks remain distinct from reproduced findings.
A regression test to keep. Supported findings can be exported as standalone Playwright tests. Confirm that the test fails on the bug before adding it to your suite; it should pass after the behavior is fixed.

For example, a task may disappear after deletion but return after a refresh. Argus can check that behavior on fresh loads, retain the evidence and export a test for the persistence failure. The receipt confirms that symptom; it does not identify the root cause or fix the application.

Reports are available as HTML, JSON, JUnit and SARIF. Test exports currently support findings verified through fresh-load text checks. Uploads, restored browser state and other unsupported steps require manual translation.

Quick start

Requires Python 3.11+, Chromium and an MCP-capable coding agent. With uv:

uvx --from argus-testing python -m playwright install chromium

uvx --from argus-testing argus-mcp --doctor

Connect it to Claude Code:

claude mcp add argus -- uvx --from argus-testing argus-mcp

Or Codex:

codex mcp add argus -- uvx --from argus-testing argus-mcp

Then ask your agent to test your app. Use test accounts and data you can change: replaying a journey can repeat its writes.

Cursor, other MCP clients and troubleshooting · Claude plugin · Codex plugin

0.12.1: generated tests keep application values in private parameters and stop before execution when steps or configuration are incomplete. Upgrade from 0.12.0 for these protections. See the releases and changelog.

Engineering

Where to start reading the code:

Verification with explicit outcomes. A completed tool call is not a passed application test. Checks return evidence and a reproduced, not reproduced or inconclusive outcome. HTTP errors and login walls stop exported checks from treating a missing symptom as a fix.
Recorded actions become reusable tests. Exports use the controls resolved during the session, preserve iframe and row scope, and check the symptom on a fresh load. The export tests exercise both buggy and fixed versions of local fixtures.
Separated runtime and adapters. Session lifecycle, browser operations, verification and reporting are separated. The host agent supplies the model; Argus does not run its own model loop or require another API key. See the architecture and design decisions.

Argus is still an alpha project. A fresh load normally retains authentication and browser storage; it is not a reset of the backend. A reproduced symptom is not proof of complete coverage or of a requirements violation. Generated tests and screenshots should be reviewed before sharing, especially with sensitive application data. Privacy details.

Evaluation

The deterministic fixtures cover 34 seeded scenarios. That measures what the tools can exercise with scripted steps, not an agent's bug-discovery rate. In a small paired Codex evaluation, both Argus and the browser baseline found all 5 predeclared defects. Argus also found one fixture defect identified after the run and used more time and tokens. These results do not establish general superiority.

The evaluation guide documents the method, limits and reproduction commands. Browser and unit tests run locally without model calls; model-based evaluations are separate and opt-in.

Documentation

Usage and tool reference — client setup, profiles, configuration and regression workflows.
Agent protocol — structured results, evidence and coverage tracking.
Contributing — local checks and implementation boundaries.
Changelog · Security · Privacy.

Built by Yichen Wu · yichenwu.dev

Argus — Testing for Coding Agents

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

SuperCollider

README from the maker

Argus

Browser testing for your coding agent.

What you get

Quick start

Engineering

Evaluation

Documentation