QASE MCP Server
> **Note:** An official Qase MCP server is now available at [qase-tms/qase-mcp-server](https://github.com/qase-tms/qase-mcp-server). Consider using the official server for production use.
# 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:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
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`
```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](https://github.com/modelcontextprotocol/inspector):
```bash
npx -y @modelcontextprotocol/inspector -e QASE_API_TOKEN=<YOUR_TOKEN> ./build/index.js
```
TDQS
Scored across 26 tools
Each tool has a clearly distinct purpose targeting specific resources (cases, plans, projects, results, shared steps, suites, runs) with unambiguous actions (create, get, update, list). No overlapping functionality exists between tools, making selection straightforward for an agent.
All tools follow a consistent verb_noun pattern with perfect uniformity (e.g., create_case, get_cases, update_suite). The naming convention is predictable across all 26 tools, using snake_case consistently without any deviations or mixed styles.
With 26 tools, the count is borderline high for typical MCP servers, which often have 3-15 tools. While the tools are well-organized, the number may feel heavy and could overwhelm agents, though it aligns with comprehensive test management coverage.
The tool set provides complete CRUD/lifecycle coverage for test management, including create, get, update, and list operations for all core resources (cases, plans, projects, results, shared steps, suites, runs). No obvious gaps exist, ensuring agents can handle full workflows without dead ends.