Create and improve tests
Turn requirements and product context into reviewable test cases, then save them into the right project.
Opening AxonQA
Opening AxonQABring Codex, Claude, VS Code, Cursor, or another MCP-compatible client into AxonQA. Ask for QA work in plain language while AxonQA provides the tools, permissions, execution, evidence, and audit trail.
AxonQA MCP session
Streamable HTTP · permission scoped
“Check release 4.2 and run what is still needed.”
axonqa.assess_release2 evidence gaps foundaxonqa.run_frameworksmoke · Chromeaxonqa.get_run_status18 of 24 passedaxonqa.assess_releasewaiting for evidenceOne connection, the whole QA workflow
MCP gives your chosen assistant a live catalog of AxonQA tools. It can discover what is available, choose the right operation, and return structured results to the conversation.
Turn requirements and product context into reviewable test cases, then save them into the right project.
Find the right framework or test, start local or cloud runs, and follow the result from the same conversation.
Inspect run evidence, group related failures, understand healing, and prepare the next action without copying details between tools.
Manage collections, requests, flows, environments, contracts, mocks, webhooks, and API run results.
Read the evidence behind a release assessment, identify blockers, and help close the gaps that remain.
Operate across projects, requirements, tests, automation, API checks, and results without losing traceability.
Designed for controlled access
An MCP connection does not bypass AxonQA’s safety model. Each client uses a revocable key, sees only the capabilities you enable, and operates within the user and workspace attached to that key.
Explore security and data protectionEnable projects, test management, automation, and API testing independently for each connection.
Every tool call runs as the authenticated AxonQA user and inside the correct organization boundary.
Delete, revoke, archive, and other destructive actions stop until the user explicitly confirms them.
See which clients initialized, when they were last active, the key they used, and every tool outcome.
Four steps to connect
Pick Codex, Claude, VS Code, Cursor, or the generic HTTP configuration.
Select the QA capability packs this client should be allowed to use.
Copy the one-time secret into the generated client configuration.
AxonQA detects the real initialize handshake and records the connection.
Choose the surface area
A developer’s editor may need automation and API testing. A release assistant may only need requirements and test results. Create separate keys for separate jobs.
Projects, stories, releases, reports
Cases, suites, plans, quality gates
Frameworks, runs, healing, discovery
Requests, flows, schemas, environments
Try asking
“Generate tests for STORE-204 and save them to the Checkout project.”
“Run smoke on Chrome. If it passes, start the full regression.”
“Why did the checkout tests fail last night?”
“Build an API flow that creates an order, then fetches it by ID.”
“What is blocking release 4.2, and which checks are still missing?”
“Show me the coverage gaps in the billing stories.”
Start with the sample project, create a scoped MCP key, and connect the client you already use.
14-day trial · No card required · Sample project included