{
  "markdown": "# Qase MCP Server\n\nOfficial [Model Context Protocol](https://modelcontextprotocol.io) (MCP) server for [Qase Test Management Platform](https://qase.io) — connect AI assistants to your test cases, runs, defects, and more.\n\n[![npm version](https://img.shields.io/npm/v/@qase/mcp-server)](https://www.npmjs.com/package/@qase/mcp-server)\n[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)\n[![MCP Registry](https://img.shields.io/badge/MCP_Registry-io.qase%2Fmcp--server-blue)](https://registry.modelcontextprotocol.io/v0/servers?search=io.qase%2Fmcp-server)\n\n## Table of Contents\n\n- [Overview](#overview)\n- [Use Cases](#use-cases)\n- [Quick Start](#quick-start)\n  - [Use the hosted Qase MCP (recommended)](#use-the-hosted-qase-mcp-recommended)\n  - [Run it yourself](#run-it-yourself)\n- [Building on top of this server](#building-on-top-of-this-server)\n- [Upgrading from v1](#upgrading-from-v1)\n- [Tools](#tools)\n- [Documentation](#documentation)\n- [Contributing](#contributing)\n- [License](#license)\n- [Support](#support)\n- [Links](#links)\n\n## Overview\n\nThe Qase MCP Server lets AI assistants (Claude, Cursor, Codex, and any other MCP client) read and write Qase test cases, runs, results, defects, suites, milestones, and more — through a standardized protocol, with no custom integration code.\n\n**Features:**\n\n- **36 task-oriented tools** (37 total, including `qase_discover_tools`) — consolidated from 83 v1 tools for lower token usage and better LLM accuracy\n- **Composite tools** — multi-step workflows in a single call: CI reporting, defect triage, regression run setup\n- **QQL support** — Qase Query Language for advanced searches across cases, runs, results, defects, and plans\n- **Project context bootstrap** — one call returns full project structure (suites, milestones, environments, users, custom fields)\n- **Test case review** — propose new cases or changes for review, assign reviewers, and track status (approving and merging remain UI-only)\n- **Tool discovery** — secondary tools stay hidden until needed, keeping the default tool list small\n- **Hosted or self-run** — connect to `https://mcp.qase.io/mcp` with just your Qase login, or run the server locally with your own API token\n- **Tenant-safe caching & HTTP resilience** — two-tier cache (in-memory + optional Redis), connection pooling, retry with backoff\n- **Escape hatch** — direct REST API access for any endpoint via `qase_api`\n\n## Use Cases\n\n| Scenario | Example prompt | Tool |\n| --- | --- | --- |\n| Bootstrap project context | \"Show me the structure of project DEMO — suites, milestones, environments\" | `qase_project_context` |\n| Create or update a test case | \"Create a high-priority smoke test case in project DEMO titled 'Login with valid credentials'\" | `qase_case_upsert` |\n| Report CI results | \"Report these CI results for project DEMO: case 1 passed, case 2 failed with 'timeout error'\" | `qase_ci_report` |\n| Triage a failed test | \"Create a critical defect for the login timeout failure in run #42\" | `qase_triage_defect` |\n| Search with QQL | \"Find all failed test results from the last 7 days in project DEMO\" | `qql_search` |\n\nSee [Tools](#tools) and [docs/tools.md](docs/tools.md) for the full reference.\n\n## Quick Start\n\n### Use the hosted Qase MCP (recommended)\n\nNo install, no API token — connect to the Qase-hosted server and sign in with your Qase account.\n\n> **Note:** The hosted Qase MCP requires the **Enterprise** plan *and* a workspace on Qase's main cloud (`qase.io`). On another plan, or on a dedicated instance, [run the server yourself](#run-it-yourself) with your own API token — that works everywhere.\n\n- **Claude** — open **Settings → Connectors**, find **Qase Test Management**, click **Connect**.\n- **Cursor** — add `{\"mcpServers\": {\"qase\": {\"url\": \"https://mcp.qase.io/mcp\"}}}` to `.cursor/mcp.json`.\n- **Codex** — add the URL `https://mcp.qase.io/mcp` in **Settings → MCPs → Add server**, or configure `~/.codex/config.toml` for the CLI.\n- **VS Code** — add `{\"servers\": {\"qase\": {\"type\": \"http\", \"url\": \"https://mcp.qase.io/mcp\"}}}` to `.vscode/mcp.json`, or run **MCP: Add Server**.\n\nFull per-client steps, other clients, and the active-workspace model: **[docs/connect.md](docs/connect.md)**.\n\n### Run it yourself\n\nInstall the package and provide your own API token:\n\n```bash\nnpm install -g @qase/mcp-server\nexport QASE_API_TOKEN=your_api_token_here\n```\n\nThen point your MCP client's stdio config at the `@qase/mcp-server` binary. Full install options, client configs (Claude Desktop, Cursor, Claude Code, Codex, OpenCode), environment variables, and transports (stdio/SSE/streamable-HTTP): **[docs/self-run.md](docs/self-run.md)**.\n\n## Building on top of this server\n\nFor **integration authors** only — if you use the server directly, nothing here applies to you.\n\nIf your product drives this server (a plugin, an agent, a wrapper CLI), it can identify itself so its usage is attributable in Qase analytics, independently of which AI host is connected:\n\n```bash\nQASE_MCP_INTEGRATION=quality-supervisor/1.4.0   # <name>/<version>, version optional\n```\n\nThe name must be on the allowlist in [`src/utils/integration-marker.ts`](src/utils/integration-marker.ts) — add yours in a PR. Anything unlisted or malformed is ignored, and the API call still succeeds. HTTP transports also accept the marker per request (`X-Qase-Integration` header or `?integration=`). Details: **[docs/self-run.md](docs/self-run.md#integration-marker-for-integration-authors)**.\n\n## Upgrading from v1\n\nv2 consolidated 83 v1 tools into **29 task-oriented tools** (30 total, including a discovery tool), and has since grown to 36 (37 total). Tool names and response shapes have changed. See **[docs/migration.md](docs/migration.md)** for the complete tool mapping table, response format changes, and before/after examples.\n\n## Tools\n\n37 tools across 6 groups (36 task-oriented tools plus `qase_discover_tools` for on-demand activation of secondary tools):\n\n| Group | Count | Description |\n| --- | --- | --- |\n| Read | 2 | Fetch any entity by type/ID, or bootstrap full project context in one call |\n| QQL | 2 | Search across cases, runs, results, defects, and plans with Qase Query Language |\n| Write | 28 | Create, update, and delete cases (single or up to 100 at once), runs, results, defects, suites, milestones, plans, shared steps, environments, and attachments; link cases and runs to Jira issues; propose and manage test case reviews |\n| Composite | 3 | Multi-step workflows in one call: CI reporting, defect triage, regression run setup |\n| Escape hatch | 1 | Direct REST API access for any endpoint not covered by the tools above |\n| Meta | 1 | `qase_discover_tools` — find and activate secondary tools on demand |\n\nFull tool-by-tool reference with parameters and the discovery model: **[docs/tools.md](docs/tools.md)**.\n\n## Documentation\n\n- **[docs/connect.md](docs/connect.md)** — connect to the hosted Qase MCP (Claude, Cursor, Codex, other clients)\n- **[docs/self-run.md](docs/self-run.md)** — install and run the server yourself (config, clients, transports)\n- **[docs/tools.md](docs/tools.md)** — full tool reference, groups, and the discovery model\n- **[docs/troubleshooting.md](docs/troubleshooting.md)** — auth, OAuth/connector, and SSL issues\n- **[docs/migration.md](docs/migration.md)** — v1 → v2 tool mapping and migration guide\n\n## Contributing\n\nContributions are welcome! See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, testing, and linting guidelines.\n\n## License\n\nMIT License — see [LICENSE](LICENSE) for details.\n\n## Support\n\n- **Documentation**: https://docs.qase.io/en/articles/14984302-qase-mcp-server\n- **Email**: support@qase.io\n- **GitHub Issues**: https://github.com/qase-tms/qase-mcp-server/issues\n\n## Links\n\n- **Qase Platform**: https://qase.io\n- **Qase Documentation**: https://help.qase.io\n- **API Documentation**: https://developers.qase.io\n- **MCP Protocol**: https://modelcontextprotocol.io\n- **Issue Tracker**: https://github.com/qase-tms/qase-mcp-server/issues\n",
  "bytes": 8058,
  "sha": "bfe6ea42f9ca05a118fa11ddb64af829c5520ac3469dea395b2ce056cd222b8a",
  "repo_slug": "qase-tms/qase-mcp-server",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_qase_mcp_server_e13f205e/readme"
}