Model Context Protocol

Assertive.tech MCP Server — Give your coding agents autonomous QA superpowers

One endpoint turns Claude, Cursor or any MCP client into a QA operator: it can read your scenarios, inspect failing runs and act on real evidence instead of guesswork.

https://assertive.tech/mcpOne-click connect

Setup guides

Add to claude_desktop_config.json, then restart Claude. Claude Code users can run the CLI instead.

claude_desktop_config.json

{
  "mcpServers": {
    "assertive": {
      "type": "http",
      "url": "https://assertive.tech/mcp",
      "headers": {
        "Authorization": "Bearer ${ASSERTIVE_API_KEY}"
      }
    }
  }
}

Claude Code CLI

claude mcp add --transport http assertive https://assertive.tech/mcp \
  --header "Authorization: Bearer $ASSERTIVE_API_KEY"

Tool reference

Tools are exposed per authenticated user — an agent only ever sees the projects and runs your account is allowed to read.

list_projectsAvailable

Enumerate the projects your account can reach, with app URL and scenario counts.

list_scenariosAvailable

List every scenario in a project — the canonical way for an agent to see current coverage.

get_scenarioAvailable

Read one scenario's full step list, persona binding and assertions.

list_runsAvailable

Browse recent runs with status, duration and run reference (RUN-000123).

get_runAvailable

Fetch a single run: per-step results, traces, screenshots and failure context.

list_failing_resultsAvailable

Pull only the failing steps across recent runs so the agent can go straight to the fix.

trigger_scenario_runPlanned

Dispatch a scenario (or a set) and stream progress back to the agent.

create_scenarioPlanned

Author a new scenario from a natural-language description of the flow.

get_failure_patchPlanned

Return a suggested remediation diff for a failing step from the remediation engine.

Authentication

Option 1 — Bearer token

Send your key on every request as Authorization: Bearer <ASSERTIVE_API_KEY>. Keep it in an environment variable — never commit it to .cursor/mcp.json.

shell

export ASSERTIVE_API_KEY="ak_live_..."   # from Settings → API keys

Option 2 — OAuth 2.1 (recommended)

Omit the header and the client registers itself automatically: it discovers the authorization server from the protected-resource document, opens the Assertive consent screen in your browser, and you approve the connection once. Tokens refresh silently and every call runs as your user with the same permissions you have in the app.

discovery

curl https://assertive.tech/.well-known/oauth-protected-resource
# → { "resource": "https://assertive.tech/mcp", "authorization_servers": [ ... ] }

Prefer not to hand-edit config files?

The Connect page runs the same setup in one click, and API Reference covers the REST surface behind these tools.