What is Mcp Qase

mcp-qase is an MCP server implementation designed for integration with the Qase test management platform. It is built using TypeScript and provides tools for managing various Qase entities such as projects, test cases, test runs, and more.

Use cases

Use cases for mcp-qase include managing test cases for software projects, tracking test run results, creating and updating test plans and suites, and collaborating on testing efforts across teams using the Qase platform.

How to use

To use mcp-qase, install the necessary dependencies with ‘npm install’, build the server using ‘npm run build’, and configure it with your Qase API token. For integration with applications like Claude Desktop or Cursor, specific configuration steps are provided in the README.

Key features

Key features of mcp-qase include tools for managing projects, test cases, test runs, test results, test plans, test suites, and shared steps. It allows users to create, update, delete, and retrieve information about these entities through the Qase API.

Where to use

mcp-qase can be used in software development and testing environments where Qase is utilized for test management. It is particularly useful for teams that need to automate and streamline their testing processes.

QASE MCP Server

MCP server implementation for Qase API

This is a TypeScript-based MCP server that provides integration with the Qase test management platform. It implements core MCP concepts by providing tools for interacting with various Qase entities.

Features

Tools

The server provides tools for interacting with the Qase API, allowing you to manage the following entities:

Projects

• list_projects - Get all projects
• get_project - Get project by code
• create_project - Create new project
• delete_project - Delete project by code

Test Cases

• get_cases - Get all test cases in a project
• get_case - Get a specific test case
• create_case - Create a new test case
• update_case - Update an existing test case

Test Runs

• get_runs - Get all test runs in a project
• get_run - Get a specific test run

Test Results

• get_results - Get all test run results for a project
• get_result - Get test run result by code and hash
• create_result - Create test run result
• create_result_bulk - Create multiple test run results in bulk
• update_result - Update an existing test run result

Test Plans

• get_plans - Get all test plans in a project
• get_plan - Get a specific test plan
• create_plan - Create a new test plan
• update_plan - Update an existing test plan
• delete_plan - Delete a test plan

Test Suites

• get_suites - Get all test suites in a project
• get_suite - Get a specific test suite
• create_suite - Create a new test suite
• update_suite - Update an existing test suite
• delete_suite - Delete a test suite

Shared Steps

• get_shared_steps - Get all shared steps in a project
• get_shared_step - Get a specific shared step
• create_shared_step - Create a new shared step
• update_shared_step - Update an existing shared step
• delete_shared_step - Delete a shared step

Development

Install dependencies:

npm install

Build the server:

npm run build

For development with auto-rebuild:

npm run watch

Installation

Claude Desktop

To use with Claude Desktop, add the server config:

• On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• On Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-qase": {
      "command": "/path/to/mcp-qase/build/index.js",
      "env": {
        "QASE_API_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

Cursor

To use with Cursor, register the command as follows:

env QASE_API_TOKEN=<YOUR_TOKEN> /path/to/mcp-qase/build/index.js

Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector:

npx -y @modelcontextprotocol/inspector -e QASE_API_TOKEN=<YOUR_TOKEN> ./build/index.js