ContextQA MCP
MCP server that lets AI assistants create, run and debug ContextQA test automation
- Platforms
- API, Web
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About ContextQA MCP
ContextQA MCP is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
The README-style docs describe ContextQA MCP as a bridge between an AI client and ContextQA's test automation platform. Instead of switching to the web app, you can ask your assistant to author test cases, execute them, and look into failures from inside the chat. Access is through a hosted Streamable HTTP endpoint, so it works with cloud-based clients as well as local tools.
Sign-in is handled by OAuth in the browser, and the docs say tokens last eight hours and refresh automatically. Once connected, the server exposes areas such as test case authoring, test generation from code diffs and tickets, browser and mobile runs, failure evidence like logs and recordings, and Jira-linked requirements and coverage. Organization-level settings such as credits and integrations are also reachable through it, subject to your account permissions.
The server is aimed at QA engineers and developers who already use ContextQA and want to drive it conversationally. Setup guides cover ChatGPT, Claude, Codex, Claude Code and Cursor. A ContextQA account with an active workspace is required, and the docs note that some actions depend on your role within a managed organization.
Install
Run in a terminal
claude mcp add --transport http contextqa https://mcp.contextqa.com/mcpAdd to Settings → Connectors → Add custom connector
https://mcp.contextqa.com/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"contextqa": {
"url": "https://mcp.contextqa.com/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"contextqa": {
"type": "http",
"url": "https://mcp.contextqa.com/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"contextqa": {
"serverUrl": "https://mcp.contextqa.com/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"contextqa": {
"type": "http",
"url": "https://mcp.contextqa.com/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Hosted OAuth endpoint
- Connects through a single HTTPS URL with browser-based ContextQA sign-in.
- Test case authoring
- Create, edit, search and organize test cases and reusable step groups from chat.
- Test generation from sources
- Generates tests from code diffs, tickets, requirements, Figma, Swagger and other inputs.
- Run browser and mobile tests
- Executes cases and test plans and returns live links or completed results.
- Failure debugging
- Reads logs, traces and recordings to help reproduce bugs and verify fixes.
- Jira coverage visibility
- Reads requirements, linked tests, coverage totals and defects from Jira integration.
Good for
- Writing new regression tests from a ticket or code change without leaving the AI chat
- Triaging a failing test run by pulling its logs, traces and recordings
- Checking test coverage against Jira requirements before a release
- Exporting a test repository as a Playwright project for local saving
ContextQA MCP FAQ
How do I authenticate?
When you first connect, your browser opens a ContextQA login page. The docs say tokens last 8 hours and auto-refresh.
Can local-only clients connect?
Cloud connectors cannot reach localhost, so the hosted HTTPS endpoint is the one to use for those clients.
What do I need before using it?
A ContextQA account. The docs also recommend confirming your organization and active workspace after connecting.
How do I add ContextQA MCP to Claude Code?
Run this command in your terminal: claude mcp add --transport http contextqa https://mcp.contextqa.com/mcp
What are the best alternatives to ContextQA MCP?
The closest alternatives to ContextQA MCP are Qase Test Management, simplify3x-connect, MCP Server, Testiny Test Management and ComplexQA.
Where this comes from
- Description: written from the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.
