2,500+ MCP servers ready to use
Vinkius

Applitools 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 Applitools 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": {
    "applitools": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Applitools
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 Applitools MCP Server

Connect your Applitools Eyes testing suite to your AI agent and manage your entire visual regression pipeline without opening the dashboard. Allow your agent to spot UI changes, validate baselines, and assess testing health dynamically.

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

  • Batch Observability — Query active test batches to view aggregated statuses (Passed, Failed, Unresolved) and completion rates
  • Session & Results analysis — Drill down into specific test sessions to examine failed step images, match levels, and browser differences
  • Baseline Management — List your "golden" graphical baselines bound to applications or specific Git branches
  • Actionable Maintenance — Authorize the agent to delete outdated baselines or discard legacy batches to keep your workspace clean
  • Key Validation — Ensure connectivity against your visual AI engine before pipeline triggers

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

Follow these steps to integrate the Applitools 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 Applitools

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

Why Use VS Code Copilot with the Applitools MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Applitools 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

Applitools + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Applitools 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

Applitools MCP Tools for VS Code Copilot (10)

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

01

delete_baseline

Use when a baseline is outdated or a page has been redesigned. Delete an Applitools test baseline

02

delete_batch

Does NOT affect baselines. Use with caution — this is irreversible. Delete an Applitools test batch

03

get_batch

Use batch ID from list_batches. Get full details of an Applitools batch

04

get_batch_stats

Returns passed/failed/unresolved/new counts without full test data. Get summary statistics for an Applitools batch

05

get_session

Provide batch ID and session ID. Get details of a test session within an Applitools batch

06

list_baselines

Returns baseline IDs, names, and env configs. Filter by app name. List visual baselines for an app on Applitools

07

list_batches

Batches group related test sessions. Returns batch IDs, names, statuses (Passed/Unresolved/Failed), and test counts. Each batch has a unique ID used to query its results. List all test batches on Applitools Eyes

08

list_branch_baselines

Use to inspect branch-specific visual states. List baselines for a specific branch on Applitools

09

list_results

List all test results in an Applitools batch

10

validate_key

Use to verify connectivity before running tests. Validate the Applitools API key

Example Prompts for Applitools in VS Code Copilot

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

01

"List the most recent visual test batches in Applitools."

02

"Get me the exact session results for our unresolved batch ID b_991x."

03

"List the baselines assigned specifically to fixing the 'feature/dark-mode-header' branch."

Troubleshooting Applitools MCP Server with VS Code Copilot

Common issues when connecting Applitools 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.

Applitools + VS Code Copilot FAQ

Common questions about integrating Applitools 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 Applitools to VS Code Copilot

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