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.

Qase MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Qase
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Qase and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "qase": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Qase MCP Server

Connect your Qase workspace to any AI agent and integrate test management deeply into your development workflow.

GitHub Copilot Agent mode brings Qase data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Project Overviews — Retrieve all active projects, view health metrics, and get total counts of test cases, runs, and defects instantly
Test Cases & Suites — Explore your test hierarchy, pull specific test steps, and check case automation statuses without opening the Qase dashboard
Test Runs & Execution — List all test runs, monitor execution status (passed, failed, blocked), and dive deep into test run analytics
Defects & Milestones — Track project milestones and extract all logged defects linked to failed test cases, complete with severity levels and issue links

The Qase MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Qase to VS Code Copilot via MCP

Follow these steps to integrate the Qase MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Qase

Ask Copilot: "Using Qase, help me...". 10 tools available

Why Use VS Code Copilot with the Qase MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Qase through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Qase + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Qase MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Qase MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Qase to VS Code Copilot via MCP:

get_case

Retrieves details for a specific test case

get_project

Retrieves details for a specific project

get_run

Retrieves details for a specific test run

list_cases

Lists test cases in a project

list_defects

Lists all defects linked to test case failures

list_milestones

Lists all milestones in a project

list_plans

Lists all test plans in a project

list_projects

Lists all projects in Qase

list_runs

Lists all test runs in a project

list_suites

Lists test suites in a project

Example Prompts for Qase in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Qase immediately.

"List all Qase projects and show me their overall health."

"Fetch the details of test case ID 45 in the WEB project."

"Are there any recent defects added for the WEB project?"

Troubleshooting Qase MCP Server with VS Code Copilot

Common issues when connecting Qase to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Qase + VS Code Copilot FAQ

Common questions about integrating Qase MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.