How to Use the PractiTest MCP in VS Code Copilot

Q: How do I share the PractiTest MCP server configuration with my team in VS Code Copilot?

Create a .vscode/mcp.json file in your repository root and commit it to Git. Every developer on your team using VS Code Copilot will get access to the PractiTest tools.

Q: Can VS Code Copilot create new test instances in PractiTest?

Yes, Copilot can call createinstance to add tests to your active PractiTest test sets. You just need to specify the target project and test IDs in your VS Code Copilot chat.

Q: How do I list all my active PractiTest QA projects in VS Code Copilot?

Ask VS Code Copilot to run listprojects to see all workspaces your API token can access. You can then select the correct PractiTest project for your session.

Sync VS Code Copilot with PractiTest to manage your test suites and requirements right from your workspace.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect PractiTest MCP to VS Code Copilot

Create your Vinkius account to connect PractiTest to VS Code Copilot — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup PractiTest with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity Vinkius runs on Gemini

Gemini

Grok

Update test runs inside VS Code Copilot

The `create_run` tool lets VS Code Copilot update your PractiTest dashboard directly from your chat panel. You run your test suites in VS Code, and Copilot logs the results directly to PractiTest. Using `list_runs` in VS Code Copilot lets your team verify that the test results registered correctly in PractiTest. This prevents missing runs and keeps your PractiTest metrics accurate within VS Code.

Manage your test cases via this MCP Server

The `create_test` tool enables VS Code Copilot to generate and register new test cases directly in PractiTest. You highlight a function in VS Code, and Copilot builds the test case in your PractiTest project. Calling `get_test` in VS Code Copilot retrieves the details of any existing PractiTest test case to verify its steps. This helps your team maintain consistent PractiTest definitions across the VS Code workspace.

Pull requirements into VS Code Copilot

The `get_requirement` tool brings your PractiTest specifications directly into your VS Code Copilot chat window. You can write code in VS Code that aligns with your PractiTest requirements without switching apps. Running `list_requirements` in VS Code Copilot helps your team track which features still need PractiTest coverage. This keeps your VS Code development aligned with your PractiTest QA targets.

Setup guide

Set up PractiTest 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 PractiTest 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 PractiTest tools listed. Try asking: "List my recent PractiTest transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "practitest-alternative-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 PractiTest. 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 PractiTest 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 PractiTest MCP in VS Code Copilot

Create a `.vscode/mcp.json` file in your repository root and commit it to Git. Every developer on your team using VS Code Copilot will get access to the PractiTest tools.

Yes, Copilot can call `create_instance` to add tests to your active PractiTest test sets. You just need to specify the target project and test IDs in your VS Code Copilot chat.

You need VS Code version 1.96 or higher with the GitHub Copilot Chat extension installed. This setup allows the VS Code Copilot agent to execute the PractiTest server tools.

Ask VS Code Copilot to run `list_projects` to see all workspaces your API token can access. You can then select the correct PractiTest project for your session.

Yes, all communication with the API occurs locally through the VS Code Copilot connection. Your PractiTest test cases and API tokens are never cached or stored on any external servers, maintaining your team's compliance.

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