- Home
- MCP servers
- QASE
QASE
- javascript
12
GitHub Stars
javascript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"rikuson-mcp-qase": {
"command": "/path/to/mcp-qase/build/index.js",
"args": [],
"env": {
"QASE_API_TOKEN": "<YOUR_TOKEN>"
}
}
}
}This MCP server provides an interface to interact with the Qase API, enabling you to manage projects, test cases, runs, results, plans, suites, and shared steps through MCP clients. It translates Qase’s data and actions into MCP entities so you can automate test management from your preferred MCP tooling.
How to use
You can connect an MCP client to this server to perform common Qase operations. Use the client to list, fetch, create, update, or delete Qase entities such as projects, test cases, runs, results, plans, suites, and shared steps. The server exposes functions that map directly to Qase API actions, allowing you to orchestrate your test management workflows from your MCP setup.
How to install
Prerequisites: you need Node.js installed on your system. Ensure npm is available to install dependencies and run build scripts.
npm install
Build the server to produce the runtime files.
npm run build
For development with automatic rebuilds, run the watch task.
npm run watch
Use with Claude Desktop by adding the MCP server configuration to your Claude desktop config file.
{
"mcpServers": {
"mcp-qase": {
"command": "/path/to/mcp-qase/build/index.js",
"env": {
"QASE_API_TOKEN": "<YOUR_TOKEN>"
}
}
}
}
Or use Cursor by launching the MCP server with the API token in the environment.
env QASE_API_TOKEN=<YOUR_TOKEN> /path/to/mcp-qase/build/index.js
Additional sections
Debugging tip: MCP servers communicate over stdio, which can be tricky to diagnose. Consider using the MCP Inspector during development to monitor runtime behavior and environment variables.
Server configurations
The following example shows how to connect this MCP server to your MCP client using stdio. You can adapt the command to your environment.
{
"type": "stdio",
"name": "qase_mcp",
"command": "/path/to/mcp-qase/build/index.js",
"args": [],
"env": [{"name": "QASE_API_TOKEN", "value": "<YOUR_TOKEN>"}]
}
Available tools
list_projects
Retrieve all projects available in the Qase account.
get_project
Fetch details for a project by its code.
create_project
Create a new project in Qase.
delete_project
Delete a project by its code.
get_cases
Retrieve all test cases within a specific project.
get_case
Fetch a single test case by its identifier.
create_case
Create a new test case in a project.
update_case
Update an existing test case.
get_runs
List all test runs in a project.
get_run
Fetch a specific test run.
get_results
Get all test run results for a project.
get_result
Get a specific test run result by code and hash.
create_result
Create a new test run result.
create_result_bulk
Create multiple test run results in bulk.
update_result
Update an existing test run result.
get_plans
List 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.
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.
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.