eyeballs
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@eyeballstake a screenshot of example.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
eyeballs
Visual monitoring for AI agents and humans. Take screenshots, detect visual changes, track what matters.
Ships as both a CLI tool and an MCP server in one package.
Install
npm install -g eyeballs-cliThis installs Chromium automatically (~400MB on first install).
Related MCP server: Where's Waldo Rick
CLI Usage
# Take a screenshot
eyeballs screenshot https://example.com
eyeballs screenshot https://example.com --viewport 1440x900 -o homepage.png
# Check for visual changes (captures baseline on first run)
eyeballs check https://example.com
eyeballs check https://example.com --threshold 10 --region 0,100,1280,500
# Re-check (diffs against baseline)
eyeballs check https://example.com
# Accept current state as new baseline
eyeballs check https://example.com --reset
# List watched URLs
eyeballs list
# Remove a watch
eyeballs remove <id>MCP Server
eyeballs works as an MCP server for AI agents (Claude Desktop, Claude Code, Cursor, etc.).
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"eyeballs": {
"command": "eyeballs-mcp"
}
}
}Claude Code
claude mcp add eyeballs eyeballs-mcpTools
Tool | Description |
| Take a screenshot of a URL. Returns the image directly. |
| Check a URL for visual changes against a stored baseline. |
| List all monitored URLs and their status. |
| Remove a watch and its screenshots. |
Example: screenshot
screenshot({ url: "https://example.com", viewport: { width: 1440, height: 900 } })Returns the screenshot as an image the agent can see, plus metadata (dimensions, load time).
Example: check_url
check_url({ url: "https://example.com", threshold: 5, region: { x: 0, y: 100, width: 1280, height: 500 } })First call captures a baseline. Subsequent calls diff against it and report the percentage of pixels that changed. Use reset_baseline: true to accept the current state.
Overlay Handling
eyeballs automatically dismisses cookie consent banners, chat widgets, and other overlays before taking screenshots. Three layers:
CSS injection hides common banners (OneTrust, Cookiebot, Intercom, Drift, Zendesk, etc.) before the page loads
autoconsent (via DuckDuckGo's database) clicks through 100+ known consent platforms
Brute-force dismiss finds and clicks remaining "Agree"/"Accept" buttons and removes overlay elements
No configuration needed. Works on most sites out of the box.
How It Works
Screenshots via Playwright (headless Chromium)
Diffing via pixelmatch (deterministic pixel comparison, no AI needed)
Overlay removal via CSS injection + autoconsent + button clicking
Storage at
~/.eyeballs/(baselines + screenshots as PNG files)Threshold default 5%, configurable per watch to reduce noise from dynamic content
Region crop to monitor just the part of the page you care about
Requirements
Node.js 18+
~400MB disk for Chromium (installed automatically)
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/danecodes/eyeballs'
If you have feedback or need assistance with the MCP directory API, please join our Discord server