Connect your coding agent in two commands

One token per project, one package from npm. init stores the token, installs the Claude Code and git hooks for spec-based development and the testmaze-verifier subagent, and every MCP-speaking agent gets a spec, a verifier and a gate.

WIRE IT UP

Two commands. Your agent now has a spec, a verifier and a gate.

Create an MCP token in your workspace, then run two commands in your project folder. init checks the token, shows which workspace and user it maps to, and stores it in .env.testmaze (git-ignored). Your agent can confirm the workspace any time with project.whoami. Stdio and stateless HTTP both share the same tool surface.

@testmaze/mcp is live on npm — setup for Cursor, Cline, Gemini CLI and Codex CLI is in the app
terminal · zsh
npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project \
  -- npx -y @testmaze/mcp
@testmaze/mcp is a thin stdio wrapper that exchanges your token and forwards to your Test Maze backend (defaults to https://testmaze.com; override with TESTMAZE_MCP_URL). Published on npm.
COMPATIBILITY

Speaks MCP. So it speaks every coding agent.

One canonical contract — tools/list, resources/read, prompts/get — that every modern coding agent already speaks. No plugins to maintain. No bespoke integrations.

CClaude Code
◉Cursor
clCline
GGemini CLI
{}Codex CLI
✦Any MCP client
"The coding agent never grades its own work."— TestMaze design contract

Spec it. Build it.
Prove it. Ship it.

Five minutes to install. Your agent drafts the story, a person approves it, a separate verifier grades the work and the release ships on the results. Test Maze never reads your repository. Start on the free Basic plan; upgrade when your team scales.