Can the AI provide the exact step where a test case failed?

Yes. If an execution failed, the agent uses `list_runs` for the instance. Since an instance maps directly to test steps, the AI inherently decodes the exact execution traces to show you the failing parameters.

Is PractiTest's requirement and issue tracing accessible to the AI?

Yes. Tools like `list_requirements` and `list_issues` expose full traceability trees. You can ask exactly how many QA instances are mapped to Requirement 5.

Do I need to copy the project ID separately?

Yes. In PractiTest, APIs execute cleanly isolated within specific Project instances. You must provide the numeric Project ID alongside your Personal Token so the underlying `pt-engine` binds queries strictly to that project.

PractiTest MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: PractiTest
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install PractiTest and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About PractiTest MCP Server

Connect your PractiTest workspaces to any AI agent and empower it to orchestrate the entire QA lifecycle from physical requirements tracing to defect mapping natively via chat conversations.

GitHub Copilot Agent mode brings PractiTest data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Test Cases & Sets — Tell the AI to investigate any Test Case or Test Set, discovering exact preconditions and expected results (list_tests, get_test, list_sets)
Test Instances & Runs — Retrieve deep execution histories pinpointing exactly which step caused a regression bounding PASSED/FAILED statuses (list_runs)
Requirements Tracking — Audit physical system compliance extracting arrays dictating QA delivery thresholds (list_requirements)
Issue Mapping — Find exact Software Defects bound natively to QA traces verifying complex failure logic (list_issues)

The PractiTest MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect PractiTest to VS Code Copilot via MCP

Follow these steps to integrate the PractiTest MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using PractiTest

Ask Copilot: "Using PractiTest, help me...". 10 tools available

Why Use VS Code Copilot with the PractiTest MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with PractiTest through the Model Context Protocol.

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 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the PractiTest MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

PractiTest MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect PractiTest to VS Code Copilot via MCP:

get_set

Get full details of a PractiTest test set including name, status, instances count, and execution summary

get_test

Get full details of a PractiTest test case including name, description, preconditions, steps, expected results, custom fields, and requirement links

list_custom_fields

List all custom fields in a PractiTest project. Returns field names, types, applicable entities, and possible values

list_instances

List all test instances in a PractiTest test set. Instances are test-set-specific copies of test cases. Returns instance IDs, test references, and last run statuses

list_issues

List all issues (defects) in a PractiTest project. Returns issue names, statuses, severities, and linked test references

list_requirements

List all requirements in a PractiTest project. Requirements provide traceability to test cases and defects. Returns names, statuses, and linked test counts

list_runs

List all runs for a PractiTest test instance. Runs record actual test execution results. Returns run IDs, statuses (PASSED/FAILED/BLOCKED/NOT_RUN/N_A), durations, and timestamps

list_sets

List all test sets in a PractiTest project. Test sets group test instances for execution. Returns set names, statuses, planned/actual dates, and assigned testers

list_tests

List all test cases in a PractiTest project. PractiTest is an end-to-end test management platform with traceability from requirements to defects. Returns test names, IDs, statuses, custom fields, and traceability links. Uses JSON:API format

list_users

List all users in the PractiTest account. Returns user names, emails, roles, and statuses

Example Prompts for PractiTest in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with PractiTest immediately.

"List all tests inside our active QA regression instance and find the ones mapped as failed."

"Do we have any new custom fields we should be aware of inside the requirements area?"

"Are there any open defects (issues) linked directly to testing scenarios surrounding multi-currency operations?"

Troubleshooting PractiTest MCP Server with VS Code Copilot

Common issues when connecting PractiTest to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

PractiTest + VS Code Copilot FAQ

Common questions about integrating PractiTest MCP Server with VS Code Copilot.

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.