# Qase MCP > Qase MCP connects test management directly into your AI workflow. Ask your agent to pull project overviews, track failed test runs, or generate lists of open defects without ever opening the Qase dashboard. It brings critical QA data—from projects and milestones to individual test steps—right where you're coding. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** test-management, defect-tracking, qa-automation, test-reporting, milestone-tracking ## Description Need to know if a feature is ready? This MCP connects your Qase workspace so you can treat your entire testing suite like another source of truth for your agent. You stop copying URLs, digging through dashboards, or manually compiling failure reports. Instead, you ask questions about the state of your code base. Want an overview? Your agent pulls up active projects and gives instant metrics on test cases and open defects across all of them. Need to check a specific build? You can get detailed lists of recent test runs and pinpoint exactly which steps failed, or even track project milestones against current execution status. All this happens through natural conversation, making your development process faster and less prone to context switching. By connecting Qase via Vinkius, you keep all your QA data connected to the tools your team already uses. ## Tools ### list_plans Lists all the formal test plans associated with the project. ### list_projects Retrieves a comprehensive list of all projects currently set up in Qase. ### list_cases Lists all individual test cases contained within a specified project. ### get_project Pulls specific details and metrics for one identified project. ### get_case Retrieves full details, including preconditions and steps, for one specific test case ID. ### list_suites Lists the groupings of test cases that make up a larger test suite. ### list_runs Gathers an overview of all test runs conducted within a project timeframe. ### get_run Provides detailed results and metrics for a single, specific test execution run. ### list_milestones Retrieves a chronological list of key project milestones and their status. ### list_defects Lists all recorded defects that were directly linked to failed test cases. ## Prompt Examples **Prompt:** ``` List all Qase projects and show me their overall health. ``` **Response:** ``` I retrieved 3 active projects in your Qase instance. 1. Mobile App (Code: MOB) - 150 test cases, 3 active open defects. 2. Web Portal (Code: WEB) - 300 test cases, 12 test runs. 3. API V2 (Code: API) - 50 test cases, 0 defects. Should I inspect the defects on the Mobile App project? ``` **Prompt:** ``` Fetch the details of test case ID 45 in the WEB project. ``` **Response:** ``` Here are the details for WEB-45 ('User Login using SSO'): - Pre-conditions: User must have an active Google SSO account. - Step 1: Click 'Login with Google' - Expected: Google Auth modal opens. - Step 2: Enter valid credentials - Expected: Redirect to dashboard. Shall I write a Cypress test for this? ``` **Prompt:** ``` Are there any recent defects added for the WEB project? ``` **Response:** ``` Yes, I queried the `list_defects` capability. There are 2 new defects recorded today: 1. Defect #11: 'CSS layout breaks on mobile' (Severity: High) 2. Defect #12: 'API timeout during checkout' (Severity: Critical) Both are in 'open' status. Shall I pull the details for #12? ``` ## Capabilities ### Get Project Overviews Retrieve a list of active projects or gather specific details about one project's setup. ### Inspect Test Cases and Suites Explore your test hierarchy, pull up the full steps for any case, or check automation status across entire suites. ### Monitor Test Runs and Plans List all completed test runs, get deep analytics on execution outcomes (passed/failed), or view defined test plans. ### Track Milestones and Defects Get a list of project milestones or pull every defect logged against failed tests, including severity levels. ### List Specific Data Sets Fetch specific lists like test cases, runs, or defects that are linked to failures for review. ## Use Cases ### Need to know which features are blocked? A PM asks their agent, 'Show me all projects with open defects.' The agent runs `list_defects`, giving the PM a list of critical bugs and immediate visibility into release blockers. ### Debugging a failed build. A developer commits code. They ask their agent to 'Check recent test runs for project WEB.' The agent calls `list_runs` and then `get_run`, pinpointing the exact failing step so they can fix it fast. ### Preparing a status report. A QA engineer needs to summarize testing progress. They ask their agent to 'List current milestones.' The agent calls `list_milestones` and reports the completion percentage, giving an accurate view for the meeting. ### Onboarding a new team member. A new hire needs to see what's being tested. They ask their agent to 'List all projects.' The agent uses `list_projects` and provides a high-level overview of the entire testing portfolio. ## Benefits - You can immediately pull a list of active projects using `list_projects`, giving you an instant health check across the entire product line. No clicking through project dashboards needed. - When debugging, ask to retrieve details for a specific test case via `get_case`. You get all preconditions and step-by-step instructions in one go, perfect for writing unit tests or documentation. - Stop guessing about coverage. Use the combined tools to list runs and check milestones so you always know if the current build meets project requirements. - Don't waste time compiling bug reports. `list_defects` instantly surfaces every recorded defect linked to a failure, complete with severity levels and issue links. - Get full context on failures by using `get_run`. Instead of just seeing 'Failed,' you see the specific run details and can determine if it's an environment or code bug. ## How It Works The bottom line is you manage QA operations by chatting with your agent instead of clicking through multiple dashboards. 1. Subscribe to this MCP and provide your Qase API token. 2. Connect the service through your preferred AI client (Claude, Cursor, etc.). 3. Ask your agent a question like, 'List all projects with more than five open defects,' and it runs the query. ## Frequently Asked Questions **How do I check all the test cases using Qase MCP?** You can list available test cases by first asking to list projects, and then requesting specific test cases within a project via `list_cases`. **Can I find defects from failed runs with Qase MCP?** Yes. Use the `list_defects` tool. This function specifically pulls all logged defects that are linked to test case failures, so you never miss a critical bug. **What if I need details on one specific project in Qase MCP?** You use the `get_project` tool. This fetches detailed metrics for a single, identified project, giving you more than just the name and ID. **Does Qase MCP help me track feature readiness?** Absolutely. You can check progress by asking to list milestones (`list_milestones`) and cross-reference that with recent test runs using `get_run` for the latest status. **How do I get steps for a single test case in Qase MCP?** Use the `get_case` tool. This retrieves all the detailed information, including every step and its expected outcome, directly into your chat conversation. **How do I securely obtain my Qase Token?** Log in to Qase.io and click your profile icon to go to **Account settings**. Select **API Tokens** (or sometimes found under Apps for an integration token), and click **Create a new API token**. Add a name, click generate, and copy the string provided. It takes exactly 15 seconds. Paste it here to authenticate. Your token is encrypted at rest and injected securely at runtime. **Can my AI write test scripts using the case details?** Absolutely. Inside your IDE (like Cursor), you can ask the agent to 'Fetch case #12 from Qase project PROJ'. The tool retrieves the precise steps, preconditions, and expected results. The agent can then automatically generate Playwright, Cypress, or Selenium scripts based exactly on those Qase definitions. **How can I check the results of a recent QA cycle?** Ask your agent to `list_runs` for your project. This will surface your recent executions. If you notice a run with a high failure rate, ask the agent to pull `get_run` with that run's ID to dive into specifics and see which modules failed the automated checks. **Can it help me track Jira bugs linked to tests?** Yes. By using the `list_defects` capability, your AI can pull all registered defects in a Qase project. If your Qase is integrated with Jira or GitHub, the returned defect data includes external issue links, helping developers immediately map a failed test to the corresponding engineering ticket.