qase

This MCP server provides integration with the Qase test management platform. It exposes tools to manage test projects, cases, suites, and test runs within the MCP framework. The available commands (get_projects, get_test_cases, create_test_case, create_suite, create_test_run, and create_test_cases_in_bulk) enable you to list projects, fetch test cases for a project (optionally filtering by suite), create new test cases or suites, and initiate test runs or bulk-create multiple test cases. Use these tools to model your QA workflows inside the MCP environment and keep Qase synchronized with your testing activities. To start, ensure the MCP is configured with your Qase API token in the environment (QASE_API_TOKEN) and that the server is reachable by the MCP runtime. Then invoke the desired tool by name with the required arguments as demonstrated in the examples provided in the documentation.

Prerequisites:

• Node.js v23.5.0
• npm (comes with Node.js)
• TypeScript (for local development/build)

Installation steps:

1. Install dependencies npm install

2. Build the MCP server npm run build

3. Configure the MCP settings to enable the qase server (example shown in the README): // Add to 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": [] } } }

4. Start or reload the MCP runtime so it picks up the new server configuration. If you’re running in development mode, you can use npm run dev as outlined in the repository’s development instructions.

Notes and tips:

• Ensure QASE_API_TOKEN is valid and has sufficient permissions for the actions you intend to perform (read projects, create cases, create runs, etc.).
• When using get_test_cases, provide project_code as mandatory and suite_id as an optional filter.
• For create_test_run and create_suite, provide the required fields (project_code and title) and any optional fields as needed.
• If you encounter authentication errors, verify that the QASE_API_TOKEN is correctly loaded by the MCP process (env variable name and value).
• If you’re behind a proxy or have network restrictions, ensure the MCP host can reach Qase’s API endpoints.
• The npm_package field identifies the package name for Node.js deployments; replace with the actual package name if you publish this MCP server.
• Check MCP’s logs for tool-specific error messages (parameter errors, API errors, etc.) which will include actionable details for remediation.