MCP Integration

What is MCP?

The Model Context Protocol is an open standard that lets AI tools like Claude Code connect to external services. TestOps exposes a remote MCP server at /api/mcp — once connected, Claude Code can fetch work items, generate tests, sync results, and link coverage to backlog items using natural language.

Setup

claude mcp add --scope user --transport http testops \
  https://app.testops.calimatic.com/api/mcp \
  --header "Authorization: Bearer ttok_YOUR_TOKEN"

// Option A: x-api-key header (recommended)
{
  "mcpServers": {
    "testops": {
      "type": "http",
      "url": "https://app.testops.calimatic.com/api/mcp",
      "headers": {
        "x-api-key": "${TESTOPS_TOKEN}"
      }
    }
  }
}

// Option B: token in URL (no env var needed)
{
  "mcpServers": {
    "testops": {
      "type": "http",
      "url": "https://app.testops.calimatic.com/api/mcp?token=ttok_YOUR_TOKEN"
    }
  }
}

Admin: Connect Calimatic Engineering

For the get_work_item_context tool to work, an admin must configure the Calimatic Apps integration on the project:

1. 1.In Calimatic → Settings → Integrations → TestOps → generate a Work Items API key
2. 2.In TestOps → Projects → Edit → Calimatic Apps Integration → paste the cali_sk_... key
3. 3.Save — the token is encrypted at rest (AES-256-GCM)

Tool Reference

Example Workflow

After connecting, just tell Claude Code what you need. For example:

Full test coverage for STORY-123 in project calimatic-edtech.

1. Fetch the work item context
2. Generate manual tests covering feature, security, and edge cases
3. Sync them to TestOps and link to STORY-123
4. Create Playwright API + UI tests
5. Run the tests and link results to STORY-123
6. Create a share link and print summary

Claude Code will automatically use the MCP tools: get_work_item_context → sync_manual_tests → link_work_items → create_share_link — no curl commands, no env vars for API calls.

Data Flow

Developer (Claude Code)
    │
    ├── get_work_item_context("STORY-123")
    │       └── TestOps ──► Calimatic Engineering API
    │                           └── Returns: title, description, criteria
    │
    ├── sync_manual_tests([...generated tests])
    │       └── TestOps DB: upsert manual_test_cases
    │
    ├── link_work_items([{STORY-123 → test UUIDs}])
    │       └── TestOps DB: insert work_item_links
    │
    ├── create_test_launch("STORY-123")
    │       └── TestOps DB: insert test_runs
    │
    ├── Playwright runs locally → results via reporter
    │       └── POST /api/v1/ingest/launches/{id}/results
    │
    └── create_share_link(runId)
            └── Returns: https://app.testops.calimatic.com/share/abc123
                    │
                    ▼
            Calimatic Apps → STORY-123 → Testing tab
            (shows manual tests, runs, coverage badge)

Running Playwright Tests

MCP handles all TestOps API interactions. However, the Playwright reporter still needs env vars at runtime to stream results during test execution:

export TESTOPS_URL=https://app.testops.calimatic.com
export TESTOPS_TOKEN=ttok_YOUR_TOKEN
export TESTOPS_PROJECT=your-project-slug

These are only needed for the Playwright reporter plugin. All other TestOps interactions go through MCP with the token baked into the connection config.

Technical Details