Argus Testing

About

Argus adds autonomous QA to an MCP host such as Claude Code, Codex or Cursor. Given a URL, the agent explores user journeys in a browser, inspects what it sees and records bugs. Each finding is re-checked from a clean page load before it is marked verified. Tools are keyed by description, for example clicking "Login button". Reports can be written as HTML, JSON, JUnit and SARIF. A macOS screen profile tests native apps through the Accessibility tree.

It runs locally over stdio with uvx (package argus-testing, command argus-mcp). Chromium must be installed once through Playwright. The default core profile covers web testing; tool profiles screen and full are set with a flag or ARGUS_TOOL_PROFILE. No account is needed for MCP use.

What you can do

• Explore a web app from a URL and look for unscripted bugs
• Re-verify each bug from a clean page load before certifying it
• Start sessions with goals, constraints and a time budget
• Track goal coverage and discovered pages during a session
• Export reports as HTML, JSON, JUnit and SARIF
• Test native macOS apps with the screen tool profile
• Re-check known bugs in CI with argus-regression

Tools

Local servers list their tools once they’re running, so we can’t show them here. Look for the list in its documentation; your client shows them after you add it.

Example prompts

• Test my app at http://localhost:3000 and find real bugs.

• Run a QA pass on our checkout flow and report only verified bugs.

• Test the signup page with the goal of checking form validation.

• Test the Notes app on my Mac for usability bugs.

Set up

Every client starts Argus Testing on your machine with the same command. Pick yours; the page remembers your choice.

claude mcp add --transport stdio argus-testing -- uvx argus-testing

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

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

code --add-mcp '{"name":"argus-testing","type":"stdio","command":"uvx","args":["argus-testing"]}'

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

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

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

[mcp_servers.argus-testing]
command = "uvx"
args = ["argus-testing"]

gemini mcp add argus-testing uvx argus-testing

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

Embed

Show Argus Testing in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge Website card iframe JSON AI prompt

README badge

Markdown

[![Argus Testing on mcp.tc](https://mcp.tc/i/argus-testing/badge.svg)](https://mcp.tc/i/argus-testing)

HTML

<a href="https://mcp.tc/i/argus-testing"><img src="https://mcp.tc/i/argus-testing/badge.svg" alt="Argus Testing on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML

<script src="https://mcp.tc/w/argus-testing.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML

<iframe src="https://mcp.tc/embed/argus-testing" title="Argus Testing on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/argus-testing.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Argus Testing card to your site.

Markdown

Add the mcp.tc card for Argus Testing, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/argus-testing.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="argus-testing"><a href="https://mcp.tc/i/argus-testing">Argus Testing on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Argus Testing on mcp.tc](https://mcp.tc/i/argus-testing/badge.svg)](https://mcp.tc/i/argus-testing)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its PyPI package: each new version shows up here, with edits by its owner.

1. 6 Oct 2026, 21:21 UTC, Automatic check

   Tracking started: version 0.6.0.

FAQ