Argus — Testing for Coding Agents

Name: Argus — Testing for Coding Agents
Author: chriswu727

作者：chriswu727版本 0.12.1i★ –i在你的电脑上运行

注册名称io.github.chriswu727/argus

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

claude mcp add argus -- uvx argus-testing

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 chriswu727 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32673 个服务器的 0%
发布到注册中心的时间比此分类中其他 32673 个服务器的 96% 更新
基础检查结果等于或优于此分类中其他 32673 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Argus — Testing for Coding Agents 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.12.1）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Systemdox

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

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

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

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

在云端运行★ 211前天更新

安装

Systemdox

作者：puglieseweb

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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