Applitools MCP Server
Visual test automation management for Applitools Eyes within AI-driven workflows.
Data last scanned today · Reviewed today
Overview
The Applitools MCP Server bridges your AI assistant with the Applitools Eyes platform, specifically targeting Playwright JavaScript and TypeScript environments. It is designed to assist developers and QA engineers in configuring test frameworks, injecting visual checkpoints, and managing cross-browser test coverage through the Ultrafast Grid.
Our verdict
This server carries a high-risk score of 24/100, largely because it is community-maintained rather than official vendor-supported and has not undergone an editorial review. Due to these security uncertainties and the lack of verification regarding its authentication or read-only modes, it is recommended only for developers evaluating test automation setups in non-sensitive, isolated project environments.
- Supports Playwright JavaScript and TypeScript test automation
- Streamlines visual test setup and checkpoint injection
- Includes nine direct dependencies for a smaller supply-chain footprint
- Provides documented instructions for manual and IDE-based installation
- High-risk security score based on lack of official maintenance
- No editorial review conducted on its internal operations
- Last commit occurred over six months ago
- Single-contributor project increases potential bus-factor risk
Setup
{
"mcpServers": {
"applitools-mcp": {
"args": [
"-y",
"@applitools/mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| eyes_verify_api_key | Checks your Applitools API key and optional Eyes server URL. | low |
| eyes_setup_project | Guides the setup of Applitools Eyes in your Playwright project (Fixtures variant). | medium |
| eyes_add_checkpoints_to_test | Adds Eyes visual checkpoints to your existing Playwright test in line with best practices. | medium |
| eyes_setup_ufg | Configures the Ultrafast Grid (UFG) for cross-browser and cross-device testing. | medium |
| eyes_fetch_visual_results | Retrieves structured visual test results. | low |
| eyes_get_batch_url | Extracts and converts Eyes test result URLs from console output. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the core technical requirements for running the Applitools MCP server?
You must have Node.js 18 or newer installed and a project that utilizes Playwright Test. The server is strictly compatible with Playwright JavaScript/TypeScript projects using the Applitools Playwright Fixtures SDK.
›Does the server require specific access to my local environment?
Yes, the MCP server requires read access to your project's source code to analyze configurations and suggest visual checkpoint implementations.
›Can I use this server with frameworks other than Playwright?
No, currently the Applitools MCP server supports only Playwright JavaScript/TypeScript projects with the Playwright Fixtures SDK.
›How does the server handle my Applitools API key?
The eyes_verify_api_key tool automatically searches for your API key and server URL within your .env files, applitools.config files, playwright.config files, and system environment variables.
Changelog
- ImprovedInitial Release
2026-03-10
Badge
Maintain this server? Add the live badge to your README.