For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.mcpbundles.com/bundle/qase
Skill page: https://www.mcpbundles.com/skills/qase
Tools: 25
Live probe refreshed Nov 21, 2026 · Endpoint host mcp.mcpbundles.com
AI Skill
SKILL.md
Domain knowledge for Qase — workflow patterns, data models, and gotchas for your AI agent.
Qase
Qase organizes test management under Projects. All entities (cases, defects, runs, plans, suites) are project-scoped.
Data Model
Projects — top-level container; each has a code used as the scope for all child entities.
Cases — test cases with steps, priority, severity; belong to Suites.
Defects — bugs linked to cases or runs.
Runs — test execution runs; contain Results per case.
Plans — test plans grouping cases for execution.
Suites — hierarchical organization of cases.
Milestones — release/sprint markers for grouping.
Environments — test environments (staging, prod, etc.).
Shared Steps — reusable step sequences across cases.
Users — team members with roles.
Gotchas
project_code required: Almost all operations require a project code. Enumerate projects first to obtain it.
Rate limit: Hundreds of calls per minute per token are normal—still backoff when responses signal throttling.
Explore capabilities (25)
read 13
write 12
Qase
23
Other capabilities
2
Delete
write
delete
Universal delete tool that removes any Qase resource (project, case, defect, run, plan, suite, etc.) using smart ID routing. Returns confirmation of deletion. Deletion is permanent and cannot be undone for most resources.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms
Qase
Add to your AI client, then sign in once when you connect.
Qase is a full-featured test management platform for QA teams to organize test cases, plan test runs, track defects, and generate testing reports. Manage test suites, execute test plans, track quality metrics, and collaborate on software testing workflows with centralized test documentation.
This listing identifies a third-party integration. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
Delete — Universal delete tool that removes any Qase resource (project, case, defect, run, plan, suite, etc.) using smart ID routing. Returns confirmation of deletion. Deletion is permanent and cannot be undone for most resources.
Fetch — Universal fetch tool that retrieves ANY Qase resource using smart ID routing with colon-separated format. Supports projects, test cases, defects, runs, results, plans, suites, milestones, environments, shared steps, custom fields, and users. Returns complete resource details with metadata.
Qase Create Result — Add a test result to a test run. Records the outcome of executing a specific test case (passed, failed, blocked, etc.). Includes time spent, comments, stacktraces, and attachments. This is how you report test execution outcomes.
Qase List Cases — List test cases in a Qase project with rich filtering, sorting, and pagination. Shows case ID, title, description, steps, severity, priority, status, and more. The workhorse tool for exploring test cases in a project.
Qase List Custom Fields — List custom fields in Qase workspace with pagination. Shows custom field ID, title, type, entity, and project assignments. Custom fields extend standard Qase entities (cases, defects, runs) with additional structured data.
Qase List Defects — List defects/bugs in a Qase project with filtering, sorting, and pagination. Shows defect ID, title, actual result, severity, status, and linked test runs. The workhorse tool for tracking bugs found during testing.
Qase List Environments — List test environments in a Qase project with pagination. Shows environment ID, title, description, slug, and host. Environments represent different testing contexts like staging, production, dev, QA, etc.
Qase List Milestones — List milestones in a Qase project with filtering and pagination. Shows milestone ID, title, description, status, and due date. Milestones represent releases, sprints, or versions to organize testing efforts.
Frequently Asked Questions
What is the Qase MCP server?
Qase is a full-featured test management platform for QA teams to organize test cases, plan test runs, track defects, and generate testing reports. Manage test suites, execute test plans, track quality metrics, and collaborate on software testing workflows with centralized test documentation. It provides 25 tools that AI agents can use through the Model Context Protocol (MCP).
How do I connect Qase to my AI agent?
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/qase. Authentication is handled automatically.
Standard connector25 free calls every 30 days, then from $19/month
$19 / month
Subject to fair usage limits
Qase List Plans — List test plans in a Qase project with pagination. Shows plan ID, title, description, and count of test cases. Test plans are templates/collections of test cases that can be used to create test runs.
Qase List Projects — List Qase projects with filtering and pagination. Shows project code, title, and counts of cases, suites, milestones, runs, and defects.
Qase List Results — List test results for a specific test run with filtering and pagination. Shows individual test case execution results including status (passed/failed/blocked), time spent, comments, stacktraces, and attachments. Use this to see how each test case performed in a run.
Qase List Runs — List test runs in a Qase project with filtering, sorting, and pagination. Shows run ID, title, status, stats (passed/failed/blocked), time spent, and environment. The workhorse tool for tracking test execution sessions.
Qase List Shared Steps — List shared test steps in a Qase project with pagination. Shows shared step hash, title, action, expected result, and usage count. Shared steps are reusable test step templates that can be included in multiple test cases.
Qase List Suites — List test suites (folders) in a Qase project with pagination. Shows suite ID, title, description, preconditions, and hierarchy. Test suites organize test cases into folders/categories for better structure.
Qase List Users — List team members in Qase workspace with pagination. Shows user ID, name, email, title, and status. Use this to get user IDs for assigning test cases, plans, and defects. Read-only - users can only be managed through the Qase web UI.
Qase Upsert Case — Create new test case or update existing test case. Provide id for update mode, omit for create mode. Test cases define what to test, expected results, and test steps. Supports external issue linking (Jira, GitHub, etc.) via external_issues parameter.
Qase Upsert Custom Field — Create new custom field or update existing custom field. Provide id for update mode, omit for create mode. Custom fields add structured metadata to test cases, defects, and runs. Examples: Browser (dropdown), Test Data (text), Environment Variable (string).
Qase Upsert Defect — Create new defect or update existing defect. Provide id for update mode, omit for create mode. Defects track bugs found during testing. Status parameter handles resolve/reopen operations - set to 'resolved' to mark fixed, 'open' to reopen.
Qase Upsert Environment — Create new test environment or update existing environment. Provide id for update mode, omit for create mode. Environments represent testing contexts like staging, production, dev, QA. Link test runs to environments to track where tests were executed.
Qase Upsert Milestone — Create new milestone or update existing milestone. Provide id for update mode, omit for create mode. Milestones represent releases, sprints, or versions. Use them to organize test cases, runs, and defects by target release.
Qase Upsert Plan — Create new test plan or update existing test plan. Provide id for update mode, omit for create mode. Test plans are collections of test cases with optional assignees. Use plans to create test runs with predefined case selections.
Qase Upsert Project — Create new project or update existing project settings. Provide code for update mode, omit for create mode. Projects are top-level containers for test cases, runs, and defects in Qase.
Qase Upsert Run — Create new test run or update existing test run. Provide id for update mode, omit for create mode. Test runs track execution of test cases. Set status to 'completed' to mark run as finished. Supports external issue linking (Jira, GitHub, etc.) via external_issues parameter.
Qase Upsert Shared Step — Create new shared step or update existing shared step. Provide hash for update mode, omit for create mode. Shared steps are reusable test step templates (e.g., 'Login as admin', 'Navigate to checkout') that can be included in multiple test cases for consistency and maintainability.
Qase Upsert Suite — Create new test suite or update existing test suite. Provide id for update mode, omit for create mode. Test suites are folders that organize test cases into hierarchical categories (e.g., Login, Checkout, Admin Panel).
Qase provides 25 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
What authentication does Qase require?
Qase uses API Key. Qase requires credentials. Connect via MCPBundles and authentication is handled automatically.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.
More in project management
Other MCP servers in this category from the directory index