TesterArmy — Claude Code MCP server: app checks on every pull request
Hooks cloud runs of your saved tests into a coding agent: browser and mobile checks with plain-language steps, results back as JSON.
claude mcp add --transport http testerarmy https://tester.army/mcpWhat TesterArmy does
The server sits at https://tester.army/mcp and speaks Streamable HTTP. Sign-in goes through your TesterArmy account with OAuth, so there is no API key to make or paste. From the agent you build and group saved tests whose steps are written in ordinary words, then fire them in TesterArmy cloud against a stored environment.
Runs can be awaited and transcripts read, which gives the agent a concrete failure to act on. A CLI ships alongside: testerarmy, shortened to ta. It lists projects and their tests and puts runs in the queue. Without --wait, a successful call means only that the run was queued — pass the flag when you want validation.
For a run to hit your latest build, keep the preview or tunnel address in a project environment and pick it with --env <nameOrSlug>. That address has to be reachable from the cloud; otherwise the check runs against something other than your changes. The repository doubles as a plugin that brings the server and the testerarmy-cli skill together. Codex asks you to log in once with codex mcp login testerarmy.
What it helps with
- Run a saved browser test set against a fresh preview build
- Fire mobile app checks in the cloud and wait for the transcript
- Write a test scenario in plain language and keep it in the dashboard
- Hand a coding agent the exact failure instead of a raw log
- Re-run a smoke group before merging
Example prompts for the agent
- Find my TesterArmy project and run the saved test, then wait for the result
- Save a test: open the landing page, log in, check the profile heading
- Run the smoke group on the preview environment and list what broke
How to install TesterArmy
Platform CLI: remote server
claude mcp add --transport http testerarmy https://tester.army/mcpPlatform CLI: remote server
codex mcp add testerarmy --url https://tester.army/mcpConfig file
{
"mcpServers": {
"testerarmy": {
"url": "https://tester.army/mcp"
}
}
}Config file
{
"servers": {
"testerarmy": {
"type": "http",
"url": "https://tester.army/mcp"
}
}
}Platform CLI: remote server
gemini mcp add -t http testerarmy https://tester.army/mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about TesterArmy
How do I install TesterArmy in Claude Code?
Register the hosted server with claude mcp add --transport http testerarmy https://tester.army/mcp, then confirm the TesterArmy OAuth sign-in.
What does TesterArmy do?
It keeps your QA coverage in the TesterArmy dashboard and queues cloud runs: browser and mobile checks driven by saved tests.
Do I need an API key for the server?
No. The hosted server signs you in with OAuth through your TesterArmy account. An API key belongs to the CLI flow, where ta auth uses it.
