Qase Connector for AI agents.
10 live capabilities
Manage test cases and defect tracking directly from your chat.
Waiting for input…
Why people use Qase
Qase for Faster QA Defect Tracking
With the Qase MCP, that loop disappears. You just ask your agent to pull the details for a specific case. You get the steps, the pre-conditions, and the expected results right in your chat. You stay in your flow, and the QA data comes to you.
What Vinkius changes
You get your QA data in your chat instead of a browser tab.
Use it from Claude, ChatGPT, Cursor or another AI client you already have.
One account · 5,900+ Connectors
- Real-world use case 01
Writing automation scripts
A QA engineer asks for the steps of a specific test case to write a script, using `get_case` to ensure every step is captured correctly.
- Real-world use case 02
Debugging a failed deployment
A developer asks for all defects linked to a failed test run in the web project to see what's breaking immediately.
- Real-world use case 03
Reporting project status
A PM asks for a summary of milestones and test counts for a new release to provide a quick update without opening a dashboard.
Complete set · 10capabilities
The complete Qase capability set.
These are the exact actions your AI can choose when you ask it to work with Qase.
01—04
4 capabilities in this set.
Part of 10 available through Qase.
- 01 Capability
List plans
Shows all test plans in a project. Use it to see how tests are organized.
- 02 Capability
List projects
Lists all projects in your Qase workspace. Use it to get an overview of your testing landscape.
- 03 Capability
List cases
Lists test cases in a project. Use it to find specific tests quickly.
- 04 Capability
Get project
Retrieves details for a specific project. Use it to see project-level metrics.
05—07
3 capabilities in this set.
Part of 10 available through Qase.
- 05 Capability
Get case
Retrieves details for a specific test case. Use it to see steps and expected results.
- 06 Capability
List suites
Lists test suites in a project. Use it to navigate your test hierarchy.
- 07 Capability
List runs
Lists all test runs in a project. Use it to see the history of your executions.
08—10
3 capabilities in this set.
Part of 10 available through Qase.
- 08 Capability
Get run
Retrieves details for a specific test run. Use it to see the results of a specific execution.
- 09 Capability
List milestones
Lists all milestones in a project. Use it to track high-level progress.
- 10 Capability
List defects
Lists all defects linked to test case failures. Use it to see what's breaking.
Set up in minutes
One URL. Then ask Qase to work.
Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use Qase from the conversation.
Choose your client
Live previewAdvanced clients IDE · CLI
Claude · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp - Step 01
Open Connectors
In Claude Web or Claude Desktop, open Settings and choose Connectors.
- Step 02
Add the URL
Choose Add custom connector, name it Qase, and paste the URL above.
- Step 03
Turn it on in chat
Select +, open Connectors, and enable Qase for the conversation.
ChatGPT · Web + desktop
Connector URL · ready to paste
Streamable HTTPhttps://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp - Step 01
Open MCP settings
On desktop, open Settings and MCP servers. On web, open your workspace app or connector settings.
- Step 02
Add the URL
Choose Add server with Streamable HTTP, or create a custom MCP app, then paste the Qase URL.
- Step 03
Save and start
Save the connection and enable Qase in your conversation. Desktop may ask you to restart once.
Cursor · IDE configuration
Advanced setup
{
"mcpServers": {
"qase": {
"url": "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"
}
}
}- Step 01
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
- Step 02
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
- Step 03
Save the file
Cursor will automatically detect the new Connector
- Step 04
Start using Qase
Open Agent mode in chat and ask: "Using Qase, help me...". 10 tools available
VS Code Copilot · IDE configuration
Advanced setup
{
"mcpServers": {
"qase": {
"url": "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"
}
}
}- Step 01
Create MCP config
Create a .vscode/mcp.json file in your project root
- Step 02
Add the server config
Paste the JSON configuration above
- Step 03
Enable Agent mode
Open GitHub Copilot Chat and switch to Agent mode using the dropdown
- Step 04
Start using Qase
Ask Copilot: "Using Qase, help me...". 10 tools available
Windsurf · IDE configuration
Advanced setup
{
"mcpServers": {
"qase": {
"url": "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"
}
}
}- Step 01
Open MCP Settings
Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"
- Step 02
Add the server
Paste the JSON configuration above into mcp_config.json
- Step 03
Save and reload
Windsurf will detect the new server automatically
- Step 04
Start using Qase
Open Cascade and ask: "Using Qase, help me...". 10 tools available
Cline · IDE configuration
Advanced setup
{
"mcpServers": {
"qase": {
"url": "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"
}
}
}- Step 01
Open Cline MCP Settings
Click the Connectors icon in the Cline sidebar panel
- Step 02
Add remote server
Click "Add Connector" and paste the configuration above
- Step 03
Enable the server
Toggle the server switch to ON
- Step 04
Start using Qase
Ask Cline: "Using Qase, help me...". 10 tools available
Claude Code · Terminal command
Advanced setup
claude mcp add qase --transport http "https://edge.vinkius.com/vk_preview_DmxFjwi8voxH7zM7sJq9mvaS2UF2jcPQlNrC5P0K/mcp"- Step 01
Install Claude Code
Run npm install -g @anthropic-ai/claude-code if not already installed
- Step 02
Add the Connector
Run the command above in your terminal
- Step 03
Verify the connection
Run claude mcp to list connected servers, or type /mcp inside a session
- Step 04
Start using Qase
Ask Claude: "Using Qase, show me...". 10 tools are ready
Where the request belongs
Work Qase can move forward.
This is for the QA engineer tired of context switching, the developer who needs to know why a test failed without leaving the IDE, and the PM who needs a quick status pulse on milestones.
QA Engineer
Pulls up specific test case steps while writing automation scripts to ensure the code matches the requirements.
Developer
Queries recent defects and failed runs for a specific feature to identify blockers during a sprint.
Product Manager
Gets instant summaries of milestone completion and test coverage to update stakeholders without manual reporting.
Build the capability set
Add more capabilities.
Each Connector adds new actions and data without changing how you work.
Browse ConnectorsTestMonitor
List QA projects, extract test runs, read user assignments, and fetch tracked issues strictly from your AI chat.
PractiTest
Manage your PractiTest projects, tests, and runs directly using AI Agents.
Testim
Trigger automated AI tests, inspect execution logs, and manage branches natively via your AI agent.
Mabl (AI-Powered Test Automation)
Manage E2E testing via Mabl. trigger test plans, monitor execution results, and perform AI-driven failure analysis.
TestLink
Navigate your self-hosted TestLink instance to inspect test plans, suites, cases, and builds natively via your AI agent.
Katalon TestOps (AI Test Management)
Manage test orchestration via Katalon TestOps. rerun test runs, monitor execution results, and audit software releases.
Bring your own AI
Change the model, client or framework. Keep Qase connected.
-
Claude -
ChatGPT -
Gemini -
Cursor -
VS Code -
Windsurf -
ZCode -
Cline -
Zed -
Continue -
Kiro -
Roo Code -
Zencoder -
Goose -
Void -
Augment Code -
Amp -
Qodo -
Tabnine -
Pieces -
Sourcegraph Cody -
JetBrains -
Warp -
Amazon Q -
Antigravity -
BoltAI -
Raycast -
Jan -
LM Studio -
AnythingLLM -
Open WebUI -
Msty -
Cherry Studio -
LibreChat -
TypingMind -
Chorus -
5ire -
n8n -
LangChain -
LlamaIndex -
CrewAI -
Vercel AI SDK
Before you connect
Questions about Qase.
The practical details behind the request, access and result.
How does Qase MCP help with QA automation?
It lets your AI agent pull specific test case steps directly into your workspace. This means you can write automation scripts faster by having the requirements right where you're coding.
Can I see test results with Qase MCP?
Yes, you can use it to list all test runs in a project and get specific details for any individual run to see what passed or failed.
How do I connect Qase to my AI client?
Just subscribe to the Connector on Vinkius and provide your Qase API Token. Once connected, your agent can access your test cases, runs, and defects.
Can Qase MCP track my project milestones?
Yes, it can list all milestones in a project, making it easy to ask your agent for a summary of high-level progress and completion metrics.
Does Qase MCP show me defect severity?
It does. When you pull defects linked to test failures, the Connector retrieves the severity levels and issue links so you can prioritize them.
Can I use Qase MCP to find specific test steps?
Absolutely. You can ask your agent to fetch details for any specific test case, and it will return the pre-conditions and execution steps.
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 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.
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.
One connection away
Give your agent a direct line to Qase.
Connect Qase once. Keep it beside 5,900+ managed Connectors when the next task needs more.
Explore every Connector No credit card required · Free tier available