Applitools MCP Server for Cursor 10 tools — connect in under 2 minutes
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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.
{
"mcpServers": {
"applitools": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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.
Cursor's Agent mode turns Applitools into an in-editor superpower. Ask Cursor to generate code using live data from Applitools and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
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 Cursor 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 Cursor via MCP
Follow these steps to integrate the Applitools MCP Server with Cursor.
Open MCP Settings
Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
Add the server config
Paste the JSON configuration above into the mcp.json file that opens
Save the file
Cursor will automatically detect the new MCP server
Start using Applitools
Open Agent mode in chat and ask: "Using Applitools, help me...". 10 tools available
Why Use Cursor with the Applitools MCP Server
Cursor AI Code Editor provides unique advantages when paired with Applitools through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Applitools + Cursor Use Cases
Practical scenarios where Cursor combined with the Applitools MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Applitools MCP Tools for Cursor (10)
These 10 tools become available when you connect Applitools to Cursor via MCP:
delete_baseline
Use when a baseline is outdated or a page has been redesigned. Delete an Applitools test baseline
delete_batch
Does NOT affect baselines. Use with caution — this is irreversible. Delete an Applitools test batch
get_batch
Use batch ID from list_batches. Get full details of an Applitools batch
get_batch_stats
Returns passed/failed/unresolved/new counts without full test data. Get summary statistics for an Applitools batch
get_session
Provide batch ID and session ID. Get details of a test session within an Applitools batch
list_baselines
Returns baseline IDs, names, and env configs. Filter by app name. List visual baselines for an app on Applitools
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
list_branch_baselines
Use to inspect branch-specific visual states. List baselines for a specific branch on Applitools
list_results
List all test results in an Applitools batch
validate_key
Use to verify connectivity before running tests. Validate the Applitools API key
Example Prompts for Applitools in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Applitools immediately.
"List the most recent visual test batches in Applitools."
"Get me the exact session results for our unresolved batch ID b_991x."
"List the baselines assigned specifically to fixing the 'feature/dark-mode-header' branch."
Troubleshooting Applitools MCP Server with Cursor
Common issues when connecting Applitools to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Applitools + Cursor FAQ
Common questions about integrating Applitools MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.Can Cursor use MCP tools in inline edits?
How do I verify MCP tools are loaded?
Connect Applitools with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Applitools to Cursor
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.