How to Use the ContextQA MCP in VS Code Copilot

Q: Can my whole team use ContextQA tools inside VS Code Copilot?

Yes. You commit the MCP Server config to .vscode/mcp.json, and every team member gets access to the 10 tools automatically.

Q: How does VS Code Copilot fetch ContextQA environments?

Copilot calls listenvironments to find your target layers. It uses this mapping to ensure you are running tests against the correct staging or production setups.

Q: Can VS Code Copilot trigger a ContextQA run?

Yes. Copilot uses triggerrun to execute live testing commands against your pipelines directly from the chat pane.

Share ContextQA test statuses and run configurations across your team inside VS Code Copilot.

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 VS Code Copilot

Create your Vinkius account to connect ContextQA to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Share test configurations across your team

The `list_api_tests` tool extracts your REST and OpenAPI testing configurations directly into VS Code Copilot. By committing this MCP setup to your repository, your entire team instantly gains access to these test definitions. Copilot uses this shared context to write valid API requests. It matches your code to the exact endpoints defined in your active test suites.

Audit test suites inside this VS Code Copilot MCP Server

The `list_suites` tool retrieves your GUI test suite payloads directly into your Copilot chat interface. This lets your team inspect asynchronous test layouts without leaving the editor. Combining this with `list_cases` allows Copilot to map out the entire routing limit tree. It shows your engineers exactly where their code changes might break existing suites.

Monitor self-healing runs in real-time

The `get_execution` tool pulls specific run states to show how ContextQA healed failing tests. Copilot displays these transitions directly in your workspace panel. Your team can use `list_executions` to track global run chunks. This keeps everyone aligned on build health without switching to an external dashboard.

Setup guide

Set up ContextQA MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the ContextQA MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the ContextQA tools listed. Try asking: "List my recent ContextQA transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Yes. You commit the MCP Server config to `.vscode/mcp.json`, and every team member gets access to the 10 tools automatically.

Copilot calls `list_environments` to find your target layers. It uses this mapping to ensure you are running tests against the correct staging or production setups.

Yes. Copilot uses `trigger_run` to execute live testing commands against your pipelines directly from the chat pane.

You need VS Code 1.96 or newer. Make sure Copilot Chat is set to Agent mode to allow tool execution.

Your GUI test suites and case trees remain private. Vinkius isolates all tool execution inside ephemeral V8 MCP sandboxes, meaning your test payloads never persist on external servers.

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