How to Use the ContextQA MCP in Cursor

Q: How does Cursor use ContextQA to fix broken tests?

Cursor calls listexecutions to find failures, then reads the specific run state with getexecution. It edits your local files to fix the underlying code issues.

Q: Can I run a ContextQA test suite directly from Cursor?

Yes. In Agent mode, Cursor calls triggerrun to execute your test suites and tracks the output in the terminal panel.

Q: How do I configure my ContextQA project UUIDs in Cursor?

Cursor uses listprojects and getproject to automatically discover your project mapping UUIDs. You don't have to copy-paste them manually.

Q: How do I install this MCP Server in my editor?

Add the server configuration to your .cursor/mcp.json file in your project root or global directory. Cursor will load the 10 tools instantly.

Q: Does Cursor have access to my ContextQA OpenAPI configurations?

No. Your OpenAPI configurations and API tests fetched by listapitests are processed locally within Cursor's sandbox. Vinkius ensures zero-trust transport through its MCP gateway, preventing external data leaks.

Ingest live ContextQA test results and project structures directly into your Cursor editor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect ContextQA MCP to Cursor

Create your Vinkius account to connect ContextQA to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup ContextQA with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Write code against live test executions

The `list_executions` tool pulls your active ContextQA test runs directly into Cursor. Instead of guessing why a test failed, Cursor reads the exact global run chunks via this MCP integration while you edit your code. Cursor uses this live context to modify your codebase. It writes fixes based on real execution data, not stale logs or mock responses.

Map project architectures inside Cursor using this MCP Server

The `list_projects` tool identifies your active ContextQA testing environments to let Cursor map your workspaces. It grabs your project groupings so the editor knows exactly where your code lives. With `get_project` active, Cursor extracts specific project mapping UUIDs. This lets the editor tie your local directories to the correct remote testing spaces automatically.

Debug self-healing run states

The `get_execution` tool targets specific AI-healing run states to pinpoint failing steps. Cursor reads these states to understand how the self-healing engine resolved an issue. You can then use `get_case` to inspect the exact boundaries of those steps. Cursor uses this data to write permanent fixes for flaky tests.

Setup guide

Set up ContextQA MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the ContextQA MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent ContextQA transactions." If the MCP tools are loaded correctly, Cursor will call the ContextQA tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ContextQA. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect ContextQA now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about ContextQA MCP in Cursor

Cursor calls `list_executions` to find failures, then reads the specific run state with `get_execution`. It edits your local files to fix the underlying code issues.

Yes. In Agent mode, Cursor calls `trigger_run` to execute your test suites and tracks the output in the terminal panel.

Cursor uses `list_projects` and `get_project` to automatically discover your project mapping UUIDs. You don't have to copy-paste them manually.

Add the server configuration to your `.cursor/mcp.json` file in your project root or global directory. Cursor will load the 10 tools instantly.

No. Your OpenAPI configurations and API tests fetched by `list_api_tests` are processed locally within Cursor's sandbox. Vinkius ensures zero-trust transport through its MCP gateway, preventing external data leaks.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript