TestOps MCP Server

Model Context Protocol server for TestOps 5.25

Installation

npm install @syn7xx/testops-mcp-server

Or use directly via npx:

npx @syn7xx/testops-mcp-server --url <testops-url> --token <api-token>

Short flags: -u / -t / -h (same as --url, --token, --help).
Environment variables: TESTOPS_URL, TESTOPS_TOKEN (used when flags are omitted).

Build

npm run build

Run

npm start -- --url <testops-url> --token <api-token>

Or with npx (if not installed globally):

npx @syn7xx/testops-mcp-server --url <testops-url> --token <api-token>

TLS verification (optional)

If TestOps is served with a self-signed certificate or HTTPS is intercepted by a corporate proxy and Node.js fails TLS validation, you can disable certificate verification for that Node process by setting:

export NODE_TLS_REJECT_UNAUTHORIZED=0

Then start the server as usual (npm start, npx, or your MCP command). In MCP configs that support server environment variables, set the same name next to TESTOPS_URL / TESTOPS_TOKEN (e.g. OpenCode environment, or your client’s env field).

Security: this disables TLS peer verification for all HTTPS calls from that process. Prefer installing the correct CA in the system trust store; use NODE_TLS_REJECT_UNAUTHORIZED=0 only when necessary and in a trusted environment.

MCP setup in AI tools

Configs differ by product:

Do not commit real tokens; use env vars or local-only config.

Cursor, Windsurf, Kilo Code, Zed

These use top-level mcpServers, each entry has command (string) and args (array).

Cursor — ~/.cursor/mcp.json or project .cursor/mcp.json:

{
  "mcpServers": {
    "testops": {
      "command": "npx",
      "args": [
        "-y",
        "@syn7xx/testops-mcp-server",
        "--url",
        "https://your-testops.com",
        "--token",
        "your-token"
      ]
    }
  }
}

Windsurf — ~/.config/windsurf/mcp.json or project .windsurf/mcp.json (same structure).

Kilo Code — ~/.kilocode/mcp.json or project .kilocode/mcp.json (same structure).

Zed — ~/.config/zed/mcp.json (same structure).

Visual Studio Code

VS Code stores MCP config in mcp.json with top-level servers, not mcpServers (see Add and manage MCP servers in VS Code and the MCP configuration reference).

Workspace file: .vscode/mcp.json, or run MCP: Open User Configuration for a global file.

{
  "servers": {
    "testops": {
      "command": "npx",
      "args": [
        "-y",
        "@syn7xx/testops-mcp-server",
        "--url",
        "https://your-testops.com",
        "--token",
        "your-token"
      ]
    }
  }
}

For sensitive values, prefer input variables or env files as described in the reference.

OpenCode

OpenCode does not use mcpServers. Define servers under mcp, set type: "local", pass the process as a command array (e.g. npx, -y, @syn7xx/testops-mcp-server, …), and optional env in environment (not env). See OpenCode MCP servers.

Example — opencode.jsonc in the project root or in the global OpenCode config:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "testops": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@syn7xx/testops-mcp-server",
        "--url",
        "https://your-testops.com",
        "--token",
        "your-token"
      ],
      "enabled": true
    }
  }
}

Using environment variables instead of flags:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "testops": {
      "type": "local",
      "command": ["npx", "-y", "@syn7xx/testops-mcp-server"],
      "environment": {
        "TESTOPS_URL": "https://your-testops.com",
        "TESTOPS_TOKEN": "your-token"
      },
      "enabled": true
    }
  }
}

Claude Desktop

macOS — ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "testops": {
      "command": "npx",
      "args": [
        "@syn7xx/testops-mcp-server",
        "--url",
        "https://your-testops.com",
        "--token",
        "your-token"
      ]
    }
  }
}

On Windows, the config lives under %APPDATA%\Claude\ — see Anthropic’s Claude Desktop documentation for the exact path.

Global install (optional)

If you prefer a fixed binary path instead of npx:

npm install -g @syn7xx/testops-mcp-server

Then use "command": "testops-mcp-server" and "args": ["--url", "...", "--token", "..."] under mcpServers (Cursor, Claude, …) or servers (VS Code), or the command array in OpenCode.

Tools

Project

Launch (test run)

Test Plan

Test Case

Routing is defined in each tool’s description in tools/list. For step actions and expected results as scenario JSON, use testcase_get_scenario or testcase_get_step (same behavior).

Project Structure

src/
├── shared/openapi/   # HTTP DTOs (`common-dto`, `project-dto`, `test-plan-dto`, `test-case-dto`, `launch-dto`, `launch-test-result-dto`)
├── shared/           # Utilities, API client, pagination
├── domain/           # Business logic (project, launch, test-plan, test-case)
├── presentation/     # MCP tools (project, launch, test-plan, test-case)
├── index.ts          # Entry point
└── server.ts         # MCP server configuration

License

MIT