How to Use the Applitools MCP in Cursor

Q: How do I install the Applitools MCP server in Cursor?

Create an mcp.json file in your project root directory. Paste the server configuration inside, save it, and enable Agent mode in your chat panel.

Q: How do I see which visual tests failed?

Tell your AI to check your recent runs. It will execute listresults to gather the outcomes and show you exactly which tests caught UI deviations.

Q: Will this setup work for multiple frontend apps?

Yes. You can filter the results by application name. The listbaselines tool accepts app names as arguments so you only see reference images for the project you are currently editing.

Fix UI regressions while you code by connecting Cursor to your Applitools MCP Server.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Applitools MCP to Cursor

Create your Vinkius account to connect Applitools to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Applitools with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug visual failures inside Cursor

Writing frontend code means constantly breaking visual tests. Switching between your editor and a CI dashboard breaks your concentration. You need test feedback right next to the React components you are actively modifying. Agent mode fixes this context switch. Cursor calls `list_batches` to find your latest test run and pulls the failure breakdown via `get_batch_stats`. You see exactly which UI elements failed the visual check before you even commit your changes.

Inspect branch-specific baselines

Applitools feature branches often have completely different visual states than main. Trying to figure out which reference images apply to your current branch gets confusing fast. You end up chasing phantom test failures that only exist because the baseline is wrong. The Applitools MCP Server gives your AI direct access to this routing logic. It runs `list_branch_baselines` to see exactly what the current branch expects. If you find outdated references blocking your PR, the agent removes them with `delete_baseline`.

Drill down into test sessions

A massive Applitools test suite failure usually traces back to a single bad commit. Finding that root cause requires digging into individual test sessions to see what actually happened. Doing this manually takes forever. Ask Cursor to investigate the failed run. It uses `get_batch` to grab the overarching details, then fires `get_session` to pinpoint the exact browser and viewport that triggered the visual mismatch. It can even verify your API connection first using `validate_key`.

Setup guide

Set up Applitools MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Applitools MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Applitools transactions." If the MCP tools are loaded correctly, Cursor will call the Applitools tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "applitools-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 Applitools. 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 Applitools 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 Applitools MCP in Cursor

Create an `mcp.json` file in your project root directory. Paste the server configuration inside, save it, and enable Agent mode in your chat panel.

It can, but you must be careful. The agent has access to the `delete_batch` tool, which permanently removes the test run from your account.

Tell your AI to check your recent runs. It will execute `list_results` to gather the outcomes and show you exactly which tests caught UI deviations.

Yes. You can filter the results by application name. The `list_baselines` tool accepts app names as arguments so you only see reference images for the project you are currently editing.

Your visual test metrics stay strictly bounded. The MCP integration only reads batch IDs, environment configs, and pass/fail counts. Vinkius routes this traffic through ephemeral, zero-trust endpoints that forget your session the second the tool call completes.

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