# Applitools MCP for AI Agents AI Agent Connect

> Applitools MCP. Connect your visual testing suite to your AI agent to manage visual regression testing without leaving your editor. Inspect test batches, review UI diffs, and manage graphical baselines through natural language. It lets your agent handle the heavy lifting of visual QA.

## Overview
- **Category:** ship-it
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_1ndLMlxAw2nCuJj6kBoTmkGgowFbzClCzzhDWYqC/ai-agent-connect
- **Tags:** visual-testing, regression-testing, ui-validation, automated-testing, quality-assurance, batch-processing

## Description

Connect your visual testing suite to your AI agent and manage your entire visual regression pipeline without opening the dashboard. This Connector lets your agent spot UI changes, validate baselines, and assess testing health dynamically. Since this is hosted on the Vinkius marketplace, you get a central way to manage these visual assets, making it easy to verify that your UI stays consistent across every device without the constant context switching. It turns visual QA from a manual chore into a conversation with your agent.

## Tools

### list_baselines
Lists baseline IDs, names, and environment configs for a specific application. This helps you see what visual references exist.

### get_batch_stats
Pulls the count of passed, failed, and unresolved tests for a specific batch. Use it for a quick status update.

### list_batches
Shows all test batches with their names, statuses, and total test counts. It helps you find specific test runs quickly.

### list_branch_baselines
Shows the visual baselines associated with a specific Git branch. This is great for verifying branch-specific UI states.

### delete_baseline
Removes an outdated or redesigned baseline from your Applitools account. Use this to keep your visual workspace clean.

### delete_batch
Deletes a specific test batch from your history. This is a way to clear out old data that you no longer need.

### get_batch
Retrieves all the details for a specific batch using its unique ID. Use this to see the full results of a test run.

### list_results
Shows every individual test result contained within a specific batch. It lets you see every session in a single list.

### get_session
Provides the details for a specific test session inside a batch. Use this to drill down into a single UI mismatch.

### validate_key
Confirms that your Applitools API key is valid and connected. Check this first to ensure your agent can reach the data.

## Prompt Examples

**Prompt:** 
```
List the most recent visual test batches in Applitools.
```

**Response:** 
```
You have 3 recent batches.

| Batch Name | ID | Status |
| :--- | :--- | :--- |
| **V2 Checkout Redesign** | `b_991x` | Unresolved |
| **Marketing Footer Fix** | `b_882y` | Passed |
| **Login Dropdown** | `b_773z` | Failed |

Would you like to inspect the failures in the Login Dropdown batch?
```

**Prompt:** 
```
Get me the exact session results for our unresolved batch ID b_991x.
```

**Response:** 
```
Checking batch `b_991x` (**V2 Checkout Redesign**). There are 4 unresolved sessions out of 10.

**Main Mismatch Details:**
* **Step:** Payment Modal
* **Browsers:** Chrome 114 (Windows) and Safari 16 (iOS)
* **AI Analysis:** Noticed a 12% pixel drift in the button alignment.

Should I generate the links to view the diffs?
```

**Prompt:** 
```
List the baselines assigned specifically to fixing the 'feature/dark-mode-header' branch.
```

**Response:** 
```
I found 2 baselines associated with `feature/dark-mode-header`:

* **Nav Bar Base** (ID: `bs_4ab`)
* **Mobile Hamburger Dark** (ID: `bs_5cd`)

They appear to have been created 3 days ago. Are these outdated, and would you like me to delete them?
```

## Capabilities

### Summarize test results
Get a high-level view of passed, failed, and unresolved tests in a batch.

### Inspect specific failures
Drill down into individual sessions to see why a UI element didn't match the baseline.

### Manage visual baselines
List and organize the golden images for different apps and branches.

### Clean up old data
Remove outdated baselines or discard legacy test batches to keep your workspace tidy.

### Verify connection
Check your Applitools API key status before starting a new testing run.

## Use Cases

### Investigating a specific UI failure
A QA engineer wants to know why a Checkout button is broken on Safari. They ask the agent to list the results of the latest batch and find the session with the highest mismatch level using `list_results` and `get_session`.

### Verifying a new branch UI
A developer is merging a dark mode PR. They ask the agent to list baselines for that branch to ensure the new theme is correctly captured using `list_branch_baselines`.

### Getting a quick release status
A manager needs a status report. They ask the agent for the stats of the Homepage Redesign batch to see if it is ready for deployment using `get_batch_stats`.

### Auditing visual changes
A designer wants to see what changed in a recent update. They ask the agent to summarize the visual diffs for a specific UI component across all devices using `list_batches`.

## Benefits

- Stop context switching by checking visual test results directly in Claude or Cursor using `list_batches`.
- Faster PR reviews by using `list_branch_baselines` to see exactly what's being tested on a specific feature branch.
- Cleaner workspaces by letting your agent use `delete_baseline` to prune old visual references automatically.
- Instant status updates for large releases by pulling summary data with `get_batch_stats` instead of clicking through dashboards.
- Precise bug hunting by using `get_session` to isolate specific browser or OS failures in a failed batch.

## How It Works

The bottom line is you get a direct line to your visual testing data without ever leaving your development environment.

1. Subscribe to the Applitools MCP via the Vinkius marketplace.
2. Provide your Applitools API Key in the configuration.
3. Ask your agent to check test results or manage baselines in your preferred editor.

## Frequently Asked Questions

**Can the Applitools MCP help me see if my UI is broken on mobile?**
Yes, it allows your AI agent to query specific test sessions and report exactly which browser or OS combinations are showing visual mismatches.

**How do I use the Applitools MCP to check test results in Cursor?**
Once connected, you can simply ask your agent in Cursor to list the latest batches or summarize the results of a specific test run.

**Can I use the Applitools MCP to delete old visual baselines?**
Yes, you can use your agent to identify and delete outdated baselines to keep your visual testing workspace clean and organized.

**Does the Applitools MCP work with my existing Applitools account?**
It connects directly to your existing Applitools Eyes suite using your API key, giving your agent access to your current data.

**How can the Applitools MCP help my QA team during a release?**
It lets your team quickly pull batch stats and pinpoint exact UI failures, helping you make faster decisions about release readiness.

**Can I check if my Applitools API key is working using this Connector?**
Yes, there is a specific tool to validate your API key, ensuring your agent has a solid connection before you start your work.

**Can my AI agent resolve a test failure on its own?**
No. The Connector is designed for pulling state data—it retrieves batches, session diff links, and match levels so you can review them locally. Approving a new baseline or resolving a mismatch still requires human intervention within the Applitools Eyes dashboard to maintain absolute testing safety.

**Can I use the agent to delete old UI snapshots?**
Yes. If your UI has undergone major structural changes and old baselines are causing false positives, you can authorize the agent to execute the `delete_baseline` tool. Provide the exact baseline ID to instantly discard the legacy screenshot from your workspace.

**How fast can I summarize test errors after my CI/CD action triggers?**
Almost instantly. Rather than scrolling through dozens of Applitools logs, ask your agent to 'Get batch stats for ID 123'. It will immediately return the aggregation of Passed, Failed, and Unresolved runs, saving you countless minutes of digging.