Call any Qase REST endpoint directly when no dedicated tool exists. Send method, path, optional body or query for cases not covered by specialized tools.
MIT
675,664 tools. Updated 2026-10-19 08:20
"Qase" matching MCP tools:
- Upload files to Qase and receive hashes. Pass these hashes in an attachments field to attach the files; uploading alone does not attach.MIT
- Fetch a Qase project's details, suite tree, milestones, environments, custom fields, and users in one call to build initial context before test work.MIT
- Delete an attachment by its hash permanently. References remain but the file is removed, and confirmation is required first.MIT
- Delete a test case by project code and ID. This action is irreversible and removes execution history; consider marking it deprecated instead.MIT
- Delete a custom field by ID workspace-wide, removing it from every project and deleting its values permanently; asks for confirmation first.MIT
Matching MCP Servers
Qase MCP Serverofficial
AlicenseAqualityAmaintenanceOfficial MCP server for Qase Test Management Platform. Enables AI assistants to manage test cases, test runs, defects, and other Qase entities through natural language.424,394 npm37MIT- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates with the Qase test management platform, allowing users to create and retrieve test cases, manage test runs, and interact with Qase projects.15 npm1-
Matching MCP Connectors
- Qase Test ManagementOAuth
Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
Onchain DeFi intelligence API for Base, payable per call with x402 (USDC). Live MCP tools: get_bot_status (Telegram bot health), get_market_stats (market snapshot), get_onchain_sales (proven revenue from live x402 routes). Built for agents that need verifiable onchain data — whale flow, signals, and sales evidence at $0.003/call.
- Delete a Qase defect permanently by project code and ID, including its linked results. Use only when removal is intended; resolve via upsert to preserve the record.MIT
- Deletes a Qase test run and all its results using a project code and run ID, after user confirmation; this action cannot be undone.MIT
- Delete a shared step by project code and hash, affecting every case that references it. Check references first; this action cannot be undone.MIT
- Fetch a single Qase record by entity type and ID when you already know its identifier. Use it for one specific case, suite, run, defect, or similar record.MIT
- Create a Qase project with a unique 2–10 character code plus deliberate title and access level, since these fields cannot be changed through the API later.MIT
- List a project's reviews with their current state and filter by status to see open ones. The API has no endpoints for approving or merging, so this is the only way to check a review's status.MIT
- Create or update Qase defects: include an ID to update an existing defect, or omit it and supply title, actual result, and severity to create one.MIT
- Delete a milestone by project code and ID. This irreversible action unlinks test runs and cases, breaking release reporting, and asks for confirmation first.MIT
- Delete a Qase test plan by project code and ID after confirmation. This cannot be undone; cases and runs remain, but ID references break.MIT
- Permanently delete an entire Qase project by code, including all cases, suites, runs, results, defects, and milestones. This irreversible action requires confirmation and cannot be undone.MIT
- Delete one test run result by run ID and result hash to correct pass rates without affecting the test case or other results. Requires confirmation and cannot be undone.MIT
- Open a test case review to propose edits to an existing case or draft a new one; pass case_id for changes, omit it for new cases.MIT
- Delete a Qase review by project code and review ID, permanently removing the proposal when it has not been merged. The referenced test case is not affected.MIT
- Update an open Qase review by ID: change proposed test case fields or reviewers. Changing case fields resets approvals; updating only reviewers keeps existing approvals.MIT
- Mark a Qase test run as finished for reporting. This sets the run's state to complete; later results can still update counts.MIT