Bring Qa Testing
to VS Code Copilot
Learn how to connect PractiTest to VS Code Copilot and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the PractiTest MCP Server?
Empower your AI Agents with full access to your PractiTest workspace. This MCP Server allows AI to manage quality assurance processes, fetching project details, tests, runs, instances, and requirements in real-time. Whether you need to run specific tests or aggregate QA metrics, this integration seamlessly connects PractiTest to AI Agents.
What you can do
List and get details of PractiTest projects. Create and manage tests, test runs, and test instances directly from AI. Fetch requirements to ensure full QA coverage. Automate report generation by pulling live QA data.How it works
1. Subscribe and install the PractiTest integration. 2. Provide your PractiTest API Token. 3. Your AI Agent instantly gains the ability to query, analyze, and manage your testing data.Who is this for?
QA Engineers looking to automate test management through chat. Project Managers tracking software quality without leaving their AI interface. * Developers validating requirements and run results on the fly.Built-in capabilities (11)
Provide the data as a JSON string. Create a new instance in a PractiTest project
Provide the data as a JSON string. Create a new run in a PractiTest project
Provide the data as a JSON string. Create a new test in a PractiTest project
Get details of a specific PractiTest project
Get details of a specific requirement in a PractiTest project
Get details of a specific test in a PractiTest project
List instances within a specific PractiTest project
List all PractiTest projects accessible by the API token
List requirements within a specific PractiTest project
List runs within a specific PractiTest project
List tests within a specific PractiTest project
Why VS Code Copilot?
GitHub Copilot Agent mode brings PractiTest data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
- —
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
- —
Project-scoped MCP configs (
.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access - —
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
- —
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
PractiTest in VS Code Copilot
PractiTest and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect PractiTest to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for PractiTest in VS Code Copilot
The PractiTest MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
PractiTest for VS Code Copilot
Every tool call from VS Code Copilot to the PractiTest MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can the AI Agent execute tests inside PractiTest?
While the agent cannot run automated testing scripts directly in PractiTest, it can create Test Runs, log results into Instances, and manage the administrative side of QA efficiently.
Are custom fields supported when creating new tests?
Yes! The AI agent formats API requests dynamically. If your workspace requires custom fields, simply instruct the agent on which attributes to include during the test creation.
Is there a limit on how many tests the agent can list at once?
The agent adheres to PractiTest API pagination limits. By default, it returns a single page of results, but you can explicitly ask the AI to query a different page number or limit.
Which VS Code version supports MCP?
MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
How do I switch to Agent mode?
Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
Can I restrict which MCP tools Copilot can access?
Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
Does MCP work in VS Code Remote or Codespaces?
Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.