Lets an AI client create and run browser and mobile QA tests, wait for results, and inspect run transcripts and reports.
Also known as e2e-inc/cli, cli
- Stars
- 75
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.0
- Last commit
- Nov 12, 2026
- License
- MIT
What is TesterArmy MCP?
TesterArmy lets an AI client create and run browser and mobile QA tests, wait for results, and inspect run transcripts and reports.
Summary generated from the project's README
About TesterArmy MCP server
Queuing browser and mobile QA runs against saved tests from inside an AI client is what TesterArmy handles. It manages QA coverage in a TesterArmy dashboard and sends runs to execute in TesterArmy cloud, then reports back on what happened. Saved tests are written in plain-language steps and run against saved environments, and results include run transcripts, recordings and JUnit reports. Scheduled groups, discovery runs and issue triage are also part of the flow.
It is available as a hosted MCP server over Streamable HTTP, so the client connects to a remote endpoint rather than running anything locally. Sign-in happens through your TesterArmy account with OAuth, which means no API key has to be created or pasted for the MCP route. Setup examples are given for Claude Code, Codex and Cursor, and the repository doubles as a plugin that installs both the server and a testerarmy-cli skill. The same features are reachable through the `testerarmy` or `ta` command line tool, installed globally with npm, which authenticates via `ta auth` and offers commands such as `ta projects list`, `ta tests list` and `ta tests run --wait --json`.
One distinction is the emphasis on feeding concrete validation back to coding agents. To check development changes, a cloud-reachable preview or tunnel URL is saved as a project environment and picked with `--env`. Without a wait flag, a successful run command only confirms the run was queued.
What you can do with it
- 1Verify a preview build end to endHave the agent save a tunnel URL as a project environment, run the saved smoke group against it and wait for the outcome.
- 2Read transcripts after a failed runPull up the transcript, recording and JUnit report for a finished run so the agent can point at what broke.
- 3Create tests from plain-language stepsAsk the client to author a new saved dashboard test written in plain-language steps, using the example markdown scenarios as references.
- 4Find projects before running testsList the available projects and their saved tests in JSON so the agent can pick the right IDs before queuing anything.
- 5Schedule grouped regression coverageQueue a saved group of tests on a schedule or on demand and triage the issues the group surfaces.
Written from the project's README. Every use case is checked against a quote from it.
How to install TesterArmy MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall TesterArmy MCP in Claude Code
$ claude mcp add --transport http cli https://tester.army/mcpInstall TesterArmy MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"cli": {
"url": "https://tester.army/mcp"
}
}
}Install TesterArmy MCP in VS Code
.vscode/mcp.json
{
"servers": {
"cli": {
"type": "http",
"url": "https://tester.army/mcp"
}
}
}Install TesterArmy MCP in VS Code CLI
$ code --add-mcp '{"name":"cli","type":"http","url":"https://tester.army/mcp"}'Install TesterArmy MCP in Codex
$ codex mcp add cli --url https://tester.army/mcpInstall TesterArmy MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.cli] url = "https://tester.army/mcp"
Install TesterArmy MCP in Gemini CLI
$ gemini mcp add -s user --transport http cli https://tester.army/mcpInstall TesterArmy MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"cli": {
"url": "https://tester.army/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubAgents that test your app like real users.
TesterArmy CLI (testerarmy / ta) manages QA coverage in the TesterArmy dashboard
and queues runs that execute in TesterArmy cloud.
- Create and organize saved tests with plain-language steps.
- Run browser and mobile checks against saved environments.
- Wait for results and inspect run transcripts, recordings, and JUnit reports.
- Schedule groups, explore with discovery runs, and triage the issues they find.
- Feed concrete validation back to coding agents.
Start here:
- Docs: tester.army/docs
- Platform: tester.army
- API keys: tester.army/dashboard/profile/api-keys
https://github.com/user-attachments/assets/f7524c3f-018e-46eb-9bae-cb69335fda64
Quickstart
Install globally:
npm install -g testerarmy
Then create API key:
tester.army/dashboard/profile/api-keys
Authenticate (pick one):
ta auth
Or run without install:
npx testerarmy --help
Find a project and its saved tests, then wait for a cloud run:
ta projects list --json
ta tests list --project <projectId> --json
ta tests run <testId> --wait --json
Use IDs returned by the list commands. Without --wait, a successful command
only confirms that the run was queued. To validate development changes, save a
cloud-reachable preview or tunnel URL as a project environment and select it
with --env <nameOrSlug>.
Skill Installation
Use skills CLI install:
npx skills add e2e-inc/cli
MCP server and plugins
TesterArmy also runs as a hosted MCP server at https://tester.army/mcp (Streamable HTTP). It signs you in with your TesterArmy account through OAuth, so there is no API key to create or paste. MCP and the CLI cover the same features; pick whichever your agent drives more easily.
Claude Code:
claude mcp add --transport http testerarmy https://tester.army/mcp
Codex:
codex mcp add testerarmy --url https://tester.army/mcp
Or add it to ~/.codex/config.toml and run codex mcp login testerarmy:
[mcp_servers.testerarmy]
url = "https://tester.army/mcp"
Cursor: open Customize and search for testerarmy, or click Add to Cursor on the marketplace listing. If the plugin is not listed yet, add the server by hand to ~/.cursor/mcp.json:
{
"mcpServers": {
"testerarmy": {
"url": "https://tester.army/mcp"
}
}
}
This repo is also a plugin that installs the MCP server and the testerarmy-cli skill together.
Claude Code: run /plugin marketplace add e2e-inc/cli, then /plugin install testerarmy@testerarmy-agent-skills.
Codex: the repo is a plugin marketplace too, so until TesterArmy appears in the Plugins Directory you can add it from here:
codex plugin marketplace add e2e-inc/cli
codex plugin add testerarmy@testerarmy-agent-skills
The plugin registers the hosted server for you; sign in once with codex mcp login testerarmy, or accept the sign-in prompt the ChatGPT app shows at install. In the ChatGPT desktop app, open this repository in Codex and the marketplace appears as a source in the Plugins tab.
Full reference for the server and its tools: https://docs.tester.army/cli/mcp
Examples
Use the markdown scenarios in examples/ as authoring
references when creating saved dashboard tests with ta tests create.
examples/TESTER.mdexamples/tests/01-landing-page.mdexamples/tests/02-auth-smoke.mdexamples/tests/03-project-create.mdexamples/prompts/ad-hoc-regression.md
Run a saved smoke group:
ta groups list --project <projectId> --json
ta tests run --group <groupId> --project <projectId> --wait --json
Contributing
PRs welcome, especially for:
- improving skill quality and references
- better issue templates and triage process
- better real-world test examples
License
MIT
TesterArmy MCP questions
How do I add TesterArmy MCP to Claude Code?
Run claude mcp add --transport http cli https://tester.army/mcp in your terminal. Add --scope user to make it available in every project.
How do I add TesterArmy MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I authenticate with the TesterArmy MCP server?
The hosted MCP server signs you in with your TesterArmy account through OAuth, so no API key is needed. The CLI alternative uses API keys created in the dashboard.
How do I add TesterArmy to Claude Code?
Register the HTTP transport with the testerarmy name pointing at the hosted MCP URL.
Can I run a saved test group and wait for results?
List groups for a project, then run the group with --wait and JSON output to get results back.
What kinds of tests can TesterArmy run?
It runs browser and mobile checks against saved environments and can report results as transcripts, recordings, and JUnit reports.