Coding agents and access

Codex integration

TesterArmy's hosted MCP server lets Codex create, run and read tests from its own session after one OAuth sign-in.

START TESTING FOR FREE READ THE SETUP DOCS

[01] Session

Checkout group run from Codex

A Codex session runs the regression prompt. The agent lists the project's groups, queues Checkout against Staging in TesterArmy cloud, polls each run and reads the failing transcript.

Codex · testerarmy MCP

Run the "Checkout" group against the staging environment and summarize which tests failed and why.

list_groups "test groups in the project"Checkout group found

run_group "every enabled test, staging environment"batch queued in TesterArmy cloud

get_run "status and result of each run"guest checkout failed

get_run_transcript "reasoning, tool calls and outputs"failing assert step read

The Checkout group ran in TesterArmy cloud against Staging. Every test passed except guest checkout, where the transcript shows an assert step failed because the confirmation page never showed the order summary.

Config file
The [mcp_servers.testerarmy] entry in ~/.codex/config.toml registers the same server as codex mcp add.
Batch of runs
run_group returns a batch id with one run per enabled test, and get_batch reports every run's verdict.
Environment target
run_group targets a saved project environment, a named environment such as staging, or an override URL.

[02] Setup

How it works

Setup is one codex mcp add command or an entry in ~/.codex/config.toml, and every tool answers No authorization provided until codex mcp login completes in the browser.

Add the server to Codex

Run codex mcp add testerarmy --url https://tester.army/mcp, or add a [mcp_servers.testerarmy] entry with that url to ~/.codex/config.toml.

Run codex mcp login

Run codex mcp login testerarmy to complete the TesterArmy sign-in in the browser over OAuth 2.1, with no API key to create, paste or rotate.

Ask Codex in plain language

Once connected, Codex creates saved tests with create_test, queues a group against a saved environment with run_group, polls get_run and reads failures with get_run_transcript.

Read the setup docsThe MCP Server page covers the Codex commands, the agent's tools, starting prompts, teams, security and troubleshooting.

See it on your own app

START TESTING FOR FREE

[03] Related

Works with

Claude Code and Cursor reach the same hosted server, the MCP server page has the VS Code and mcp-remote routes, and CI webhooks queue saved groups after a deploy.

Claude CodeClaude Code creates, runs and reads TesterArmy tests from its own session.CursorCursor writes, runs and triages TesterArmy tests without leaving the editor.MCP serverClaude, Cursor, Codex and VS Code create tests, start runs and debug failures.CI webhooksJenkins, Buildkite, CircleCI or a shell script triggers a group with one request.

[04] FAQ

Questions

Over the hosted MCP server, Codex creates saved tests in plain language, queues a test or a group against a saved environment such as Staging, polls each run and reads the transcript when one fails.

The codex mcp login testerarmy command opens the browser for the TesterArmy sign-in over OAuth 2.1, so no key is created or pasted. Codex can also drive the ta CLI with an API key.

The tester-army/cli repository ships a .codex-plugin manifest bundling the testerarmy-cli skill with the MCP server, and its plugin.json lists three default prompts: test a pull request, write a signup test, explain the latest failed run.

The pull request testing docs include an AGENTS.md excerpt. With it in the repository, Codex ends every pull request description with testing instructions the exploration agent's planner reads before it plans.

[05] Start in Codex

Connect Codex to TesterArmy

Create a TesterArmy account, run codex mcp add testerarmy --url https://tester.army/mcp, then codex mcp login testerarmy and sign in when the browser opens.