Applitools

Name: Applitools · @applitools/mcp
Availability: InStock

NPM · @APPLITOOLS/MCP · SCANNED AUG 3

The Applitools MCP server helps you create, update, and analyze visual tests using Applitools Eyes.

Available components

npm · @applitools/mcp 61

+11 this week 61 61 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security80

No malware found by supply-chain analysis.Pass
CVE check failed: a known high-severity CVE affects sharp 0.34.5, reached via @applitools/core-base > @applitools/image > sharp. A fixed version is available. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (155 of 156), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency32

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
Actively maintained (last published 10 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability57

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (fair).Partial
Context-footprint check failed: tool/resource definitions use about 2140 tokens (~267/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (43% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @applitools/mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add applitools-applitools -- npx -y @applitools/mcp

# add to Codex CLI

codex mcp add applitools-applitools -- npx -y @applitools/mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "applitools-applitools": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@applitools/mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add applitools-applitools --command npx --arg -y --arg @applitools/mcp

# ~/.hermes/config.yaml

mcp_servers:
  applitools-applitools:
    command: "npx"
    args: ["-y", "@applitools/mcp"]

// mcp.json

{
  "mcpServers": {
    "applitools-applitools": {
      "command": "npx",
      "args": [
        "-y",
        "@applitools/mcp"
      ]
    }
  }
}

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
2 Aug 26 +18
- GHSA-f88m-g3jw-g9cj affects this package: high ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: unverified → fair ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: SEE LICENSE IN LICENSE functional
1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
31 Jul 26 −8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
27 Jul 26 50

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@applitools/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding

ID	CVE	Severity	Vector	Fix available
GHSA-f88m-g3jw-g9cj		high		yes

Dependencies 155 packages

155 packages in the resolved dependency tree · 147 deprecated · 40 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~2,120 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

eyes_add_checkpoints_to_test ~213

Add visual checkpoints to existing Playwright tests following best practices

Input Output Examples

Name	Type	Req	Description
activeFile	string	—	Path to the currently active file or folder in the IDE (optional). Used to improve framework detection in Node.js monorepos by finding the nearest package.json relative to the active context.
fileContent	string	—	Test file content (optional if filePath provided or if IDE provides it)
filePath	string	—	Path to the test file that will be edited (optional if fileContent provided)
selection	object	—	Selected code range from IDE (pass if provided to get better context, optional if not provided will process entire file)
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory). If the workspace root is a Node.js monorepo (contains a package.json with a "workspaces" field), ask the user which package they wa…

No output schema declared.

No examples provided.

eyes_analyze_batch ~421

Fetch visual test results and textual diff descriptions from an Applitools Eyes batch URL. Use this tool when the user provides a batch URL from the Applitools dashboard (e.g. https://eyes.applitools.com/app/test-results/{batchId}) or a bare batch ID, and you need to analyze its visual test results without a Playwright HTML report on disk. This is the counterpart to `eyes_fetch_visual_results` for cases where: - The user is looking at results from a CI run or a previous run - There is no Playwright report available locally - The user pastes a batch URL from the Eyes dashboard The tool returns the same structured output as `eyes_fetch_visual_results`, including: - Per-test status (passed / failed / unresolved / new / aborted) - Textual diff descriptions for steps with visual differences - Aggregate summary statistics Note: Textual diff descriptions require DOM-based diff analysis on the server side. Steps without DOM capture (e.g. Figma, mobile native) may not have diff descriptions even when diffs are present.

Input Output Examples

Name	Type	Req	Description
activeFile	string	—	Path to the currently active file or folder in the IDE (optional). Used to improve framework detection in Node.js monorepos by finding the nearest package.json relative to the active context.
batchUrl	string	yes	The Applitools Eyes batch URL (e.g. https://eyes.applitools.com/app/test-results/{batchId}) or a bare batch ID.
serverUrl	string	—	Eyes server base URL (optional, auto-detected from batchUrl or defaults to https://eyes.applitools.com). Set this for on-premises Eyes deployments.
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory). If the workspace root is a Node.js monorepo (contains a package.json with a "workspaces" field), ask the user which package they wa…

Name	Type	Req	Description
message	string	yes	Human-readable summary of the visual test results
results	array	—	Detailed results grouped by batch
summary	object	—	Aggregated statistics summarizing test results across all batches. Counts tests by their visual comparison status.

No examples provided.

eyes_fetch_visual_results ~690

Fetch current up-to-date visual test results from the Playwright HTML report and the Eyes server. IMPORTANT: - This tool reads the Playwright HTML report directly from disk. - **Do NOT copy or move the report file.** Instead, always point this tool to the actual report location using the `reportPath` argument when it's not in the default location. - For standard Playwright runs, the default report is at `playwright-report/index.html` in the workspace root. - For the Eyes example (`npx eyes-setup run-example`), the report is generated at: `<workspaceRoot>/eyes-examples/eyes-playwright-report/index.html` In that case, call the tool with: - `reportPath: "<workspaceRoot>/eyes-examples/eyes-playwright-report/index.html"` - `workspaceRoot: "<workspaceRoot>"` **CRITICAL: Do NOT run Playwright with `--reporter=list`, `--reporter=dot`, `--reporter=line`, or any other `--reporter` flag that overrides the configured reporters. Doing so suppresses the Eyes reporter, preventing it from writing results to the HTML report. This tool will then read a stale report from a previous run and return outdated results.** Always run Playwright without reporter overrides, for example: - ✅ CORRECT: `npx playwright test` - ❌ INCORRECT: `npx playwright test --reporter=list` **Stale report detection (optional):** If you know the batch IDs from the current Playwright run output, pass them via the `expectedBatchIds` parameter. This tool will warn you if those batch IDs are not found in the report, indicating the report may be from a previous run. The tool returns structured test results that can be displayed in a table, including: - Test name - Visual test status (passed/failed/unresolved/new/aborted) - Retry attempt number - Browser/device configuration [CORE REQUIREMENT: URL INTEGRITY] Visual-results URLs returned by Eyes end with `~~`. These tildes are a dashboard sentinel, not typos. You are strictly forbidden from stripping trailing tildes from these links. Render them with mar…

Input Output Examples

Name	Type	Req	Description
activeFile	string	—	Path to the currently active file or folder in the IDE (optional). Used to improve framework detection in Node.js monorepos by finding the nearest package.json relative to the active context.
expectedBatchIds	array	—	Optional list of batch IDs extracted from the Playwright run output. When provided, the tool verifies these IDs appear in the report to confirm it is current and not stale from a previous run.
reportPath	string	—	Path to the Playwright HTML report (optional, defaults to playwright-report/index.html)
serverUrl	string	—	Optional Applitools server URL (defaults to https://eyes.applitools.com)
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory). If the workspace root is a Node.js monorepo (contains a package.json with a "workspaces" field), ask the user which package they wa…

Name	Type	Req	Description
message	string	yes	Human-readable summary of the visual test results
results	array	—	Detailed results grouped by batch
summary	object	—	Aggregated statistics summarizing test results across all batches. Counts tests by their visual comparison status.

No examples provided.

eyes_get_batch_url ~131

═══════════════════════════════════════ 📋 SHOW THIS MESSAGE TO USER AS-IS ═══════════════════════════════════════ Extract and convert Eyes test result URLs from console output. Parses the test execution output to find session URLs and converts them to batch URLs for viewing all test results together in the Eyes dashboard. This tool extracts URLs only - use eyes_fetch_visual_results to get detailed test status and results data.

Input Output Examples

Name	Type	Req	Description
testOutput	string	yes	The console output from running the Playwright test
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory)

Name	Type	Req	Description
batchUrls	—	—	Array of batch URLs for viewing all test results together in the Eyes dashboard. Null if no URLs found.
message	string	yes	Human-readable summary of URL extraction results
sessionUrls	—	—	Array of individual session URLs from test output (may end with ~~). Null if no URLs found.
testResults	—	—	Additional test result metadata if available

No examples provided.

eyes_setup_project ~250

Get step-by-step instructions to set up a Playwright JS project with Applitools Eyes (Fixtures variant) [CORE REQUIREMENT: URL INTEGRITY] Playwright visual results return URLs ending in ~~. These are not typos. You are strictly forbidden from stripping trailing tildes from these links. Use markdown [Visual Test results](URL with tildes) for links. Output the raw, verbatim URL string exactly as captured from the test output.

Input Output Examples

Name	Type	Req	Description
activeFile	string	—	Path to the currently active file or folder in the IDE (optional). Used to improve framework detection in Node.js monorepos by finding the nearest package.json relative to the active context.
apiKey	string	—	Optional API key (will use validated key from session if not provided)
projectName	string	—	Optional project name
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory). If the workspace root is a Node.js monorepo (contains a package.json with a "workspaces" field), ask the user which package they wa…

No output schema declared.

No examples provided.

eyes_setup_ufg ~240

Configure Ultrafast Grid (UFG) for cross-browser and cross-device testing [CORE REQUIREMENT: URL INTEGRITY] Playwright visual results return URLs ending in ~~. These are not typos. You are strictly forbidden from stripping trailing tildes from these links. Use markdown [Visual Test results](URL with tildes) for links. Output the raw, verbatim URL string exactly as captured from the test output.

Input Output Examples

Name	Type	Req	Description
activeFile	string	—	Path to the currently active file or folder in the IDE (optional). Used to improve framework detection in Node.js monorepos by finding the nearest package.json relative to the active context.
playwrightConfigPath	string	—	Path to playwright.config.js/ts file (optional, will be auto-detected)
workspaceRoot	string	—	Workspace root directory (optional, defaults to current directory). If the workspace root is a Node.js monorepo (contains a package.json with a "workspaces" field), ask the user which package they wa…

No output schema declared.

No examples provided.

eyes_verify_api_key ~175

Validate your Applitools API key and optional server URL. Searches for API key in .env, applitools.config.js/ts/cjs/mjs, and playwright.config.js/ts/cjs/mjs files.

Input Output Examples

Name	Type	Req	Description
apiKey	string	—	Optional API key to validate (will search config files if not provided)
serverUrl	string	—	Optional Applitools server URL (defaults to https://eyes.applitools.com)
setAsDefault	boolean	—	If true, save the validated API key and server URL as the default configuration in cache
workingDirectory	string	—	Working directory to search for .env and config files (optional, defaults to process.cwd())
workspaceRoot	string	—	Workspace root to search for .env and config files (optional, defaults to current directory)

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug