The QASE MCP Server allows you to interact with the Qase test management platform directly through Model Context Protocol (MCP) integration. This server implements tools to manage various Qase entities such as projects, test cases, runs, results, plans, suites, and shared steps.
Before installing the QASE MCP Server, ensure you have:
Start by installing the package:
npm install mcp-qase
To use the server with Claude Desktop, add the server configuration to your Claude Desktop config file:
On MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
On Windows:
%APPDATA%/Claude/claude_desktop_config.json
Add the following configuration:
{
"mcpServers": {
"mcp-qase": {
"command": "/path/to/mcp-qase/build/index.js",
"env": {
"QASE_API_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
Replace <YOUR_TOKEN> with your actual Qase API token.
To use the server with Cursor, register the command as follows:
env QASE_API_TOKEN=<YOUR_TOKEN> /path/to/mcp-qase/build/index.js
The QASE MCP Server provides various tools to interact with Qase entities. Below are the available functions categorized by entity type.
// List all projects
list_projects()
// Get a specific project by code
get_project(code)
// Create a new project
create_project(name, code, description)
// Delete a project by code
delete_project(code)
// Get all test cases in a project
get_cases(projectCode)
// Get a specific test case
get_case(projectCode, caseId)
// Create a new test case
create_case(projectCode, title, description, priority, severity, type, ...)
// Update an existing test case
update_case(projectCode, caseId, updatedData)
// Get all test runs in a project
get_runs(projectCode)
// Get a specific test run
get_run(projectCode, runId)
// Get all test run results for a project
get_results(projectCode)
// Get test run result by code and hash
get_result(projectCode, hash)
// Create test run result
create_result(projectCode, runId, caseId, status, comment)
// Create multiple test run results in bulk
create_result_bulk(projectCode, runId, results)
// Update an existing test run result
update_result(projectCode, resultId, updatedData)
// Get all test plans in a project
get_plans(projectCode)
// Get a specific test plan
get_plan(projectCode, planId)
// Create a new test plan
create_plan(projectCode, title, description, cases)
// Update an existing test plan
update_plan(projectCode, planId, updatedData)
// Delete a test plan
delete_plan(projectCode, planId)
// Get all test suites in a project
get_suites(projectCode)
// Get a specific test suite
get_suite(projectCode, suiteId)
// Create a new test suite
create_suite(projectCode, title, description, preconditions)
// Update an existing test suite
update_suite(projectCode, suiteId, updatedData)
// Delete a test suite
delete_suite(projectCode, suiteId)
// Get all shared steps in a project
get_shared_steps(projectCode)
// Get a specific shared step
get_shared_step(projectCode, sharedStepId)
// Create a new shared step
create_shared_step(projectCode, title, action, expectedResult)
// Update an existing shared step
update_shared_step(projectCode, sharedStepId, updatedData)
// Delete a shared step
delete_shared_step(projectCode, sharedStepId)
Since MCP servers communicate over stdio, you can use the MCP Inspector for debugging:
npx -y @modelcontextprotocol/inspector -e QASE_API_TOKEN=<YOUR_TOKEN> ./build/index.js
This will help you see the communication between the client and the server, making it easier to identify any issues.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "mcp-qase" '{"command":"/path/to/mcp-qase/build/index.js","env":{"QASE_API_TOKEN":"<YOUR_TOKEN>"}}'See the official Claude Code MCP documentation for more details.
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.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:
{
"mcpServers": {
"mcp-qase": {
"command": "/path/to/mcp-qase/build/index.js",
"env": {
"QASE_API_TOKEN": "<YOUR_TOKEN>"
}
}
}
}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.
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 explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.json2. Add this to your configuration file:
{
"mcpServers": {
"mcp-qase": {
"command": "/path/to/mcp-qase/build/index.js",
"env": {
"QASE_API_TOKEN": "<YOUR_TOKEN>"
}
}
}
}3. Restart Claude Desktop for the changes to take effect