Qase MCP server

Qase MCP Server provides integration with the Qase test management platform. It offers functionality for creating and retrieving test cases, managing test suites, and executing test runs through a Model Context Protocol (MCP) server interface.

Prerequisites

Before installation, ensure you have:

• Node.js v23.5.0
• Qase API token
• TypeScript

Installation

Install and build the server with the following commands:

# Install packages
npm install

# Build the server
npm run build

Configuration

Add the following settings to your MCP configuration file (cline_mcp_settings.json):

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

Make sure to replace "your-api-token" with your actual Qase API token.

Available Tools

get_projects

Retrieves a list of all projects.

Input Parameters: None

Example Usage:

{
  "name": "get_projects"
}

get_test_cases

Retrieves test cases for a specified project.

Input Parameters:

• project_code: Project code (required)
• suite_id: Suite ID (optional) - retrieves only test cases belonging to the specified suite

Example Usage:

{
  "name": "get_test_cases",
  "arguments": {
    "project_code": "DEMO",
    "suite_id": 123
  }
}

create_test_case

Creates a new test case.

Input Parameters:

• project_code: Project code (required)
• title: Test case title (required)
• description: Test case description (optional)

Example Usage:

{
  "name": "create_test_case",
  "arguments": {
    "project_code": "DEMO",
    "title": "Login Functionality Test",
    "description": "Verification of user login functionality"
  }
}

create_suite

Creates a new test suite.

Input Parameters:

• project_code: Project code (required)
• title: Test suite title (required)
• description: Test suite description (optional)
• preconditions: Test suite preconditions (optional)
• parent_id: Parent suite ID (optional)

Example Usage:

{
  "name": "create_suite",
  "arguments": {
    "project_code": "DEMO",
    "title": "Authentication Test Suite",
    "description": "All test cases related to authentication",
    "preconditions": "Test database must be initialized"
  }
}

create_test_run

Creates a new test run.

Input Parameters:

• project_code: Project code (required)
• title: Test run title (required)
• description: Test run description (optional)
• cases: List of test case IDs to include in the run (optional)

Example Usage:

{
  "name": "create_test_run",
  "arguments": {
    "project_code": "DEMO",
    "title": "Regression Test Run",
    "description": "Verification tests before v1.2.0 release",
    "cases": [1, 2, 3]
  }
}

create_test_cases_in_bulk

Creates multiple test cases in a single operation.

Input Parameters:

• project_code: Project code (required)
• cases: Array of test cases to create (required)
  • title: Test case title (required)
  • description: Test case description (optional)
  • suite_id: ID of the suite where the test case belongs (optional)

Example Usage:

{
  "name": "create_test_cases_in_bulk",
  "arguments": {
    "project_code": "DEMO",
    "cases": [
      {
        "title": "Login Success Pattern",
        "description": "Verification with valid credentials",
        "suite_id": 123
      },
      {
        "title": "Login Failure Pattern",
        "description": "Verification with invalid credentials",
        "suite_id": 123
      }
    ]
  }
}

Error Handling

The tools may return the following types of errors:

• Authentication errors: Invalid or missing API token
• Parameter errors: Missing required parameters or invalid values
• API errors: Error responses from the Qase API

Error messages will include specific information about the problem and how to resolve it.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.