@testmaze/mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@testmaze/mcpverify test scenario for login feature"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@testmaze/mcp
Thin stdio wrapper for the Test Maze MCP verifier. Connects Claude Code, Cursor, Cline, and any other MCP-compatible coding agent to a hosted Test Maze instance with a one-line claude mcp add.
Status:
v0.1.0— first public release on npm under the@testmazescope (MIT). The stdio↔HTTP proxy is implemented and field-tested against the live HTTP transport. As an early 0.x release the API may still shift.
What it does
Reads your space-scoped MCP token (
tmt_*) and the Test Maze backend URL from env vars or CLI flags.Exchanges the token against
${url}/api/v1/mcp/tokens/exchange→ resolves yourspaceId + userId.Opens an MCP-over-HTTP connection to
${url}/api/v1/mcp.Pipes stdio frames between your coding agent and the remote MCP server.
The verifier you connect to has:
43 tools across 13 families (pdlc, testcase, testrun, product, feature, testplan, release, product-metrics, media, workflow, coverage, regression, activity) — including the marquee
pdlc.verify(deterministic verdict envelope).11 resources under the
testmaze://URI scheme (product, feature, case, testrun, release, …).4 prompts that drive the PDLC loop client-side (
product-init,feature-spec,ac-to-testcase,find-coverage-gaps).
What this lets your agent do: docs/functionality.md.
Related MCP server: MCP HTTP Proxy
Install
claude mcp add testmaze \
--env TESTMAZE_MCP_TOKEN=tmt_xxx \
--env TESTMAZE_MCP_URL=https://testmaze.com \
-- npx -y @testmaze/mcpThe same shape works with Cursor / Cline / any MCP client — substitute the client's MCP-add equivalent.
CLI
testmaze-mcp [--token tmt_xxx] [--url https://testmaze.com]
Flags:
--token, -t Per-space MCP token. Env fallback: TESTMAZE_MCP_TOKEN.
--url, -u Backend URL. Env fallback: TESTMAZE_MCP_URL. Default: https://testmaze.com.
--version, -v Print version and exit.
--help, -h Print this help and exit.Versioning
The wrapper's major version tracks the MCP protocol version it supports, not the Test Maze app version. A wrapper at 1.x will work against any backend that speaks MCP-protocol-1.x, regardless of the backend's Test Maze version.
License
MIT — see LICENSE.
Documentation
docs/usage.md — setup for Claude Code / Cursor / Cline, tokens, CLI, self-hosting, troubleshooting.
docs/functionality.md — what the verifier lets your agent do: the verify loop, capabilities, resources, and prompts.
For the product and to issue a token, see testmaze.com.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zcalo/testmaze-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server