MCP Server

The QA.tech MCP server exposes your test cases, runs, and applications to any AI client that speaks the Model Context Protocol. Once connected, your assistant can answer questions like “what runs failed today?” or “rerun the failed cases from run UkxK” without you leaving the chat.

Accessing the MCP

The MCP is available at:

https://api.qa.tech/v1/mcp

Authentication is handled via OAuth.

On first connect you sign in to QA.tech and pick an organization (and optionally specific projects).
You can only access data you have permission to view in that organization, limited to the projects you approved.

API keys still work for CI and clients that don’t speak OAuth yet. Open the dashboard at Organization Settings → MCP Server for copy-paste client snippets.

Pick Your Client

Most modern clients have a one-click or one-line install. Clients that support MCP OAuth (Claude Code, Cursor, Codex, Linear Agent) only need the URL above. API keys still work for CI and clients that don’t do OAuth yet.

Claude Code
Cursor
Codex
Linear
Continue (VS Code)

Run this in any project where you use Claude Code. Requires the Claude Code CLI.

claude mcp add --transport http qatech \
  'https://api.qa.tech/v1/mcp'

Then run /mcp in Claude Code (or claude mcp login qatech) and complete the browser sign-in. Claude Code reloads MCP servers automatically.Prefer a static key instead? Add --header 'Authorization: Bearer <API_KEY>' from Organization Settings → API Keys.

Go to Settings → Cursor Settings → Tools & MCPs → New MCP server. Cursor opens ~/.cursor/mcp.json. Paste this in — Cursor will open a browser window for you to sign in to QA.tech and approve access:

{
  "mcpServers": {
    "qatech": {
      "type": "http",
      "url": "https://api.qa.tech/v1/mcp"
    }
  }
}

Prefer a static key instead? Add an Authorization header with Bearer <API_KEY> from Organization Settings → API Keys.

Run this command to add the MCP server to Codex. Requires the Codex CLI. Codex starts the OAuth browser flow when the server supports it; you can also run codex mcp login qatech.

codex mcp add qatech \
  --url 'https://api.qa.tech/v1/mcp'

Prefer a static key instead? Add --header 'Authorization: Bearer <API_KEY>'.First time using an MCP server in Codex? Add experimental_use_rmcp_client = true under [features] in ~/.codex/config.toml.

Add a custom MCP server in Linear Agent with URL https://api.qa.tech/v1/mcp (OAuth, or a Bearer API key if Linear cannot complete OAuth).Full workspace enablement, Agent personalization steps, and how this differs from exporting issues are on Linear. Linear’s own UI is in Connect MCP Servers to Linear Agent.

Continue uses a static API key. Add this snippet to ~/.continue/config.yaml, then reload the Continue extension.

mcpServers:
  - name: qatech
    type: streamable-http
    url: https://api.qa.tech/v1/mcp
    requestOptions:
      headers:
        Authorization: Bearer <API_KEY>

Or Use the QA.tech CLI

The QA.tech CLI can write the config for any supported client in one command. Useful if you switch machines often or want the same setup scripted.

Don’t have the QA.tech CLI? Install it with npm install -g @qadottech/cli.

For Cursor and Claude Desktop, the default is a URL-only OAuth entry (no API key):

qatech mcp configure --client cursor
qatech mcp configure --client claude-desktop

Clients that still need a Bearer token (Continue, Goose) require an API key first:

qatech configure -k <your-api-key>
qatech mcp configure --client continue

Pass --api-key to force a static Bearer entry for Cursor/Claude Desktop. Add --print to dump the snippet without writing it. See qatech mcp configure --help for all flags.

What Your Assistant Can Do

These tools are exposed. Tools requiring write scope are hidden from read-only API keys. OAuth grants include both read and write. MCP clients that group tools by risk (Claude Desktop Tool Permissions, ChatGPT) read the protocol annotations (readOnlyHint / destructiveHint) derived from those scopes — not the scopes themselves.

Tool	Scope	What it does
`list_applications`	read	Lists applications under test in the project the API key is bound to.
`list_test_cases`	read	Lists test cases, optionally filtered by application, labels, or enabled state.
`get_run`	read	Fetches a run by short ID. Include nested results with `testCases: "all"` or `"failed"`.
`list_issues`	read	Lists issues QA.tech found in the project, newest first, with `severity`/`status` filters.
`get_issue`	read	Fetches one issue by short ID, including the run test cases where it was detected.
`create_test_case`	write	Creates a new test case in draft. Burn-in runs start automatically.
`rerun_run`	write	Reruns a previous run. Optional `failedOnly`, or a specific `projectTestCaseIds` subset.

Example prompts

“Which of my test cases failed in the last run?”

“Rerun run UkxK, but only the failed cases.”

“List the critical issues QA.tech found this week, then help me fix the first one.”

“Create a test case titled ‘Checkout with expired card’ for the frontend app.”

“List all enabled test cases tagged ‘critical’.”

Authentication

Two options:

OAuth (recommended for interactive clients)

Claude Code, Cursor, Codex, Linear Agent, and other MCP clients that support OAuth discover QA.tech’s authorization server automatically. On first connect you sign in with your QA.tech account, pick an organization, and approve access. Tokens refresh in the background. OAuth grants include both read and write tools for that organization.

API key

Same Bearer tokens as the REST API. Useful for CI and clients that don’t speak OAuth yet.

Where to find your key: Organization Settings → API Keys in the dashboard.
Scopes: A read key gives access to the four read tools. A write key adds create_test_case and rerun_run.
Project binding: Keys may be org-scoped or project-scoped. Org-scoped keys need a projectShortId on tool calls.

Treat API keys as confidential credentials. Anyone with the token can read your test data and, with a write key, create and rerun tests. Rotate keys from the dashboard if one leaks.

Endpoint Details

Field	Value
URL	`https://api.qa.tech/v1/mcp`
Transport	Streamable HTTP (JSON-RPC 2.0), stateless
Methods supported	`initialize`, `tools/list`, `tools/call`
Auth	OAuth (MCP discovery) or `Authorization: Bearer <API_KEY>`
Protocol version	`2025-06-18`
Server name	`qatech`

Batch JSON-RPC requests and GET upgrades are not supported. Each call is a single POST with a JSON body.

Smoke test with curl

curl -sS -X POST 'https://api.qa.tech/v1/mcp' \
  -H 'Authorization: Bearer <API_KEY>' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

A successful response lists the tools your key has access to.

Troubleshooting

Symptom	Likely cause
Client lists no QA.tech tools	Restart the client after editing config. Verify the JSON or YAML parses.
Browser never opens for OAuth	Confirm the client supports MCP OAuth and the config has no `Authorization` header (URL only). Retry from the client’s MCP login / `/mcp` UI.
`401` or `403` from the server	OAuth consent not completed, wrong org, or API key missing/revoked. Re-auth or re-copy the key.
Some tools missing	API key lacks `write` scope. Generate a write key, or use OAuth (includes write).
`405 Method Not Allowed`	The client sent a `GET`. QA.tech MCP is `POST`-only and stateless.
`qatech mcp configure` says no API key	Continue/Goose need a key: run `qatech configure -k <key>` or pass `--api-key`. Cursor/Claude Desktop default to OAuth and do not need one.

For anything else, contact support.

Get Started

Core Concepts

Configuration

Best Practices

Test Features

Integrations

Applications

CLI

Accessing the MCP

Pick Your Client

Or Use the QA.tech CLI

What Your Assistant Can Do

Example prompts

Authentication

OAuth (recommended for interactive clients)

API key

Endpoint Details

Smoke test with curl

Troubleshooting

​Accessing the MCP

​Pick Your Client

​Or Use the QA.tech CLI

​What Your Assistant Can Do

​Example prompts

​Authentication

​OAuth (recommended for interactive clients)

​API key

​Endpoint Details

​Smoke test with curl

​Troubleshooting

Accessing the MCP

Pick Your Client

Or Use the QA.tech CLI

What Your Assistant Can Do

Example prompts

Authentication

OAuth (recommended for interactive clients)

API key

Endpoint Details

Smoke test with curl

Troubleshooting