Qase
Interact with the Qase API for test management. Requires a QASE_API_TOKEN for authentication.
Note: An official Qase MCP server is now available at 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 projectsget_project- Get project by codecreate_project- Create new projectdelete_project- Delete project by code
Test Cases
get_cases- Get all test cases in a projectget_case- Get a specific test casecreate_case- Create a new test caseupdate_case- Update an existing test case
Test Runs
get_runs- Get all test runs in a projectget_run- Get a specific test run
Test Results
get_results- Get all test run results for a projectget_result- Get test run result by code and hashcreate_result- Create test run resultcreate_result_bulk- Create multiple test run results in bulkupdate_result- Update an existing test run result
Test Plans
get_plans- Get all test plans in a projectget_plan- Get a specific test plancreate_plan- Create a new test planupdate_plan- Update an existing test plandelete_plan- Delete a test plan
Test Suites
get_suites- Get all test suites in a projectget_suite- Get a specific test suitecreate_suite- Create a new test suiteupdate_suite- Update an existing test suitedelete_suite- Delete a test suite
Shared Steps
get_shared_steps- Get all shared steps in a projectget_shared_step- Get a specific shared stepcreate_shared_step- Create a new shared stepupdate_shared_step- Update an existing shared stepdelete_shared_step- Delete a shared step
Development
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
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
{
"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:
npx -y @modelcontextprotocol/inspector -e QASE_API_TOKEN=<YOUR_TOKEN> ./build/index.js
Servidores relacionados
Scout Monitoring MCP
patrocinadorPut performance and error data directly in the hands of your AI assistant.
Alpha Vantage MCP Server
patrocinadorAccess financial market data: realtime & historical stock, ETF, options, forex, crypto, commodities, fundamentals, technical indicators, & more
Interactive Feedback MCP
An MCP server for AI-assisted development tools like Cursor and Claude, supporting interactive feedback workflows with AI.
ApostropheCMS
Interact with ApostropheCMS, a Node.js-based content management system, to manage content snippets.
Cargo MCP Server
Tools for managing Rust projects using the cargo command-line tool.
Local MCP Test
A test server for local MCP development and setup.
graphql-to-mcp
Turn any GraphQL API into MCP tools. Auto-introspection, flat schemas.
ScreenHand
Native desktop + browser automation MCP server with 82 tools — accessibility APIs (macOS/Windows), Chrome DevTools Protocol, anti-detection, memory, jobs, and reusable playbooks.
MCP Developer Name
Returns the current developer's information.
MCP Server Starter
A TypeScript starter template for building Model Context Protocol (MCP) servers.
MCP Remote Machine Control
Provides remote machine control capabilities, eliminating SSH overhead for token-efficient system operations.
Tether MCP
Prevents AI coding agents from drifting off your architecture — blocks wrong dependencies, enforces file structure, and gives agents persistent memory of your project's rules.