An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Qase to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Run QA operations without leaving your IDE or chat.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Qase.

  1. 01

    List plans

    This capability pulls a list of all test plans within a specific project.

  2. 02

    List projects

    Use this to get a list of every project in your Qase workspace.

  3. 03

    List cases

    This capability retrieves all test cases for a given project.

  4. 04

    Get project

    This capability fetches the full details of a specific Qase project.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Qase.

  1. 05

    List runs

    Use this to see all test runs currently in a project.

  2. 06

    Get case

    This capability pulls the specific details and steps for a single test case.

  3. 07

    List suites

    This capability returns the list of test suites in a project.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Qase.

  1. 08

    Get run

    Use this to get the specific status and details of a single test run.

  2. 09

    List defects

    This capability finds all defects that are linked to failed test cases.

  3. 10

    List milestones

    This capability lists all project milestones.

Real work

What teams actually run

01

Automated Scripting

An engineer asks the agent for the steps of a specific test case to quickly build a Playwright or Cypress script.

02

Deployment Verification

A developer checks the status of the latest test run to confirm a feature is stable before merging.

03

Bug Investigation

A team member asks for a list of open defects to understand why a specific milestone is blocked.

04

QA Status Reporting

A manager requests a summary of project health and test case counts to gauge release readiness.

Automate a task

Put Qase to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Qase works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Qase to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

972ms average. Fast in production.

Qase is checked daily against the live service.

Daily averagePeak 1170ms
Oct 3Today
Fastest day
792ms
Slowest day
1170ms
14-day trend
Slowing+30%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Qase, so you can see the experience inside your AI.

It does not authenticate your account with Qase. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Qase Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Qase capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "qase-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Qase in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Qase owners hand off.

This MCP is built for technical teams that use Qase to manage their testing lifecycle.

  • 01

    QA Engineers

    They use the agent to pull test case steps while writing automation scripts in an IDE.

  • 02

    Developers

    They ask the agent to find recent defects or failed runs related to their recent code changes.

  • 03

    Product Managers

    They request instant summaries of test coverage and milestone progress.

FAQ

Questions Qase owners ask.

  • 01

    How do I connect Qase to my AI client?

    You subscribe to the MCP on Vinkius and provide your Qase API Token. Once connected, you can use it immediately in any compatible client like Claude or Cursor.

  • 02

    Which AI clients can use this MCP?

    This MCP works with any client that supports the Model Context Protocol, including Claude, Cursor, and Windsurf.

  • 03

    Can I use this to write automation code?

    Yes. You can ask your agent to retrieve specific test case steps, which it can then use to help you write automation scripts.

  • 04

    Does this MCP support defect tracking?

    Yes. It includes capabilities to list defects that are specifically linked to failed test cases.

  • 05

    Do I need to host the MCP myself?

    No. Vinkius hosts and manages the MCP for you, so it is ready to use as soon as you connect.

  • 06

    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.

  • 07

    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 capability 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.

  • 08

    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.

  • 09

    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.

Explore

More in Developer Tools

Suggestions

Connect Qase to Claude, Cursor, ChatGPT & more