An official Qase MCP server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"qase-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Official Model Context Protocol (MCP) server for Qase Test Management Platform.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
MCP server for Spanning Cloud Backup — M365/GWS/Salesforce backups, restores, audit.
AI agent control of 3D printers — 432 tools for OctoPrint, Moonraker, Bambu, Prusa, Elegoo
MCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.
On-chain provenance lookup for AnchorRegistry. Resolve AR-IDs, hashes, and full trees. Authless.
MCP Security Weekly
Get CVE alerts and security updates for Qase Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Official Model Context Protocol (MCP) server for Qase Test Management Platform.
The Qase MCP Server provides seamless integration between AI assistants (Claude, Cursor, etc.) and the Qase Test Management Platform. It enables AI assistants to interact with your test cases, test runs, defects, and other Qase entities through a standardized protocol.
The server provides tools for managing:
npm install -g @qase/mcp-server
# Clone the repository
git clone https://github.com/qase-tms/qase-mcp-server.git
cd qase-mcp-server
# Install dependencies
npm install
# Build the server
npm run build
Create a .env file or set environment variables:
# Required: Your Qase API token
QASE_API_TOKEN=your_api_token_here
# Optional: Custom API domain for enterprise customers
QASE_API_DOMAIN=api.qase.io
Get your API token from: https://app.qase.io/user/api/token
If you're using Qase Enterprise with a custom domain:
QASE_API_DOMAIN=api.yourcompany.qase.io
Add to your Claude Desktop configuration file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"qase": {
"command": "npx",
"args": ["-y", "@qase/mcp-server"],
"env": {
"QASE_API_TOKEN": "your_api_token_here"
}
}
}
}
Or, if installed from source:
{
"mcpServers": {
"qase": {
"command": "node",
"args": ["/absolute/path/to/qase-mcp-server/build/index.js"],
"env": {
"QASE_API_TOKEN": "your_api_token_here"
}
}
}
}
{
"mcpServers": {
"qase": {
"command": "npx",
"args": ["-y", "@qase/mcp-server"],
"env": {
"QASE_API_TOKEN": "your_api_token_here"
}
}
}
}
You can add the Qase MCP server to Claude Code using the CLI command:
claude mcp add qase -- npx -y @qase/mcp-server
Set the required environment variable:
export
... [View full README on GitHub](https://github.com/qase-tms/qase-mcp-server#readme)