Qase

You run a dedicated MCP server to manage Qase test cases, suites, runs, and related actions from your own tooling. This MCP server exposes endpoints you can invoke to create, read, and update test artifacts, enabling automated workflows and integrations with the Qase platform.

How to use

You interact with the MCP server through an MCP client that communicates with the local or remote server. Use the available tools to fetch projects, list or create test cases, manage suites, and run test executions. Each operation is designed to be composable in your automation pipelines, letting you build end-to-end test management flows that align with your release cycles.

How to install

Prerequisites: Node.js v22.17.0, a Qase API token, and TypeScript.

{
  "mcpServers": {
    "qase": {
      "command": "node",
      "args": ["path/to/qase-mcp-server/build/index.js"],
      "env": {
        "QASE_API_TOKEN": "your-api-token"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Configuration and startup

Install dependencies and build the MCP server, then configure the MCP settings to point at the built server and provide your API token.

# Install dependencies
npm install

# Build the MCP server
npm run build

Notes on usage

The MCP server enables you to perform actions such as getting projects, listing and creating test cases, creating suites, and creating test runs. Ensure your QASE_API_TOKEN is kept secret and is provided in a secure environment where the MCP server runs.

Security and maintenance

Keep your API token secret, rotate credentials periodically, and limit MCP server access to trusted networks. Monitor logs for unauthorized requests and update dependencies regularly to keep the stack secure.

Troubleshooting

If you encounter authentication errors, verify that QASE_API_TOKEN is correctly set in the environment where the MCP server runs. For parameter errors, check that required fields are supplied for each operation and that your project codes and IDs are valid.

Available tools

get_projects

Fetches the list of projects available in your Qase account.

get_test_cases

Retrieves test cases for a specified project, optionally filtered by suite.

create_test_case

Creates a new test case in a specified project, with optional description, preconditions, postconditions, suite, and steps.

create_suite

Creates a new test suite within a specified project, with optional description, preconditions, and parent hierarchy.

create_test_run

Creates a test run for a set of test cases within a project, with optional description and title.

create_test_cases_in_bulk

Creates multiple test cases in a single operation, supporting per-item titles, descriptions, steps, and suite assignments.

update_test_case

Updates an existing test case with new details such as title, description, severity, priority, steps, and suite membership.