2,500+ MCP servers ready to use
Vinkius

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

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.

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 Percy and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "percy": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Percy
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 Percy MCP Server

Inject precision quality assurance workflows directly bounding LLM models via the Percy Visual Testing API (by BrowserStack). Programmatically verify pixel regressions executing queries evaluating visual boundaries natively across target projects. Inspect deep status arrays parsing CI build limits dynamically, extract metrics evaluating granular snapshot checkpoints asynchronously, and force immediate test baseline approvals seamlessly directly from explicit prompt commands naturally.

GitHub Copilot Agent mode brings Percy 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

  • Project Navigation — Read bounded parameters tracking Percy deployments isolating configurations determining explicitly specific active QA targets natively
  • Automated Build Oversight — Track specific arrays extracting dynamic checks returning pipeline checkpoints (approved/failed/unreviewed limits) explicitly seamlessly
  • Visual Snapshot Operations — Log natively extracting bounds verifying comparison properties logging rendering differences mapping exact explicit width constraints
  • Baseline Affirmations — Mutate bounding loops forcing active execution of JSON logic structurally bypassing native clicks allowing test approvals implicitly (approve_build or approve_snapshot)

The Percy 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 Percy to VS Code Copilot via MCP

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Percy

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

Why Use VS Code Copilot with the Percy MCP Server

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

01

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

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Percy + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Percy MCP Tools for VS Code Copilot (10)

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

01

approve_build

/approve` moving the test suite to green. Approve all unreviewed snapshots in a Percy build. Marks the entire build as visually approved for deployment

02

approve_snapshot

Approve a single Percy snapshot. Marks it as visually correct, updating the baseline for future comparisons

03

get_build_details

Get full details of a Percy build including state, total/unreviewed snapshot counts, approved/rejected snapshots, branch, commit SHA, and finalized timestamp

04

get_project_details

Get full details of a Percy project including name, slug, default branch, auto-approve enabled, browser targets, and build count

05

get_snapshot_details

Get full details of a Percy snapshot including name, review state, widths, fingerprint, and comparison count

06

list_browsers

List all supported browser families on Percy. Returns browser names, versions, and OS combinations for cross-browser visual testing

07

list_builds

List builds for a Percy project. Each build contains snapshots from a test run. Returns build IDs, states (processing/finished/failed), branch names, commit SHAs, and snapshot counts

08

list_comparisons

List visual comparisons for a Percy snapshot. Each comparison shows the diff between baseline and head at a specific width/browser. Returns diff images, diff percentages, and browser info

09

list_projects

List all projects on Percy (BrowserStack). Percy is the leading visual regression testing platform that captures snapshots and detects pixel-level UI differences across builds. Uses JSON:API format. Returns project names, slugs, and browser configs

10

list_snapshots

List snapshots in a Percy build. Each snapshot is a captured page/component at specific widths and browsers. Returns snapshot names, review states (unreviewed/approved/rejected), and diff percentages

Example Prompts for Percy in VS Code Copilot

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

01

"Log explicitly the builds targeting structural limits seamlessly isolating project 'org-slug/my-app' dynamically checking bounding states natively."

02

"Reverse check explicit structures extracting limits comparing properties cleanly bounding snapshot ID 'snap_778' natively efficiently."

03

"Force explicit validation mutating boundaries executing structurally an approval across build ID '8910' automatically natively flawlessly securely."

Troubleshooting Percy MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Percy + VS Code Copilot FAQ

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

01

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.
02

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.
03

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.
04

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.

Connect Percy to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.