Browser Use
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Description from the maker (original English)
Screenshot capture with PII masking and cross-platform support for AI agents
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"screenshot": {
"command": "npx",
"args": [
"-y",
"@ai-capabilities-suite/mcp-screenshot"
]
}
}
}Run this in your terminal
claude mcp add screenshot -- npx -y @ai-capabilities-suite/mcp-screenshotPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"screenshot": {
"command": "npx",
"args": [
"-y",
"@ai-capabilities-suite/mcp-screenshot"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"screenshot": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@ai-capabilities-suite/mcp-screenshot"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified with the GitHub account Digital-Defiance, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 11 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Browser Use, Chrome DevTools MCP, MCP Server Browser
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Lets AI do web tasks for you, such as filling forms, searching and extracting data, in the maker’s cloud browsers or on your computer.
Lets AI use Chrome’s developer tools to inspect pages, find what makes them slow and spot errors. Made by the Chrome DevTools team.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Give AI agents visual superpowers to see, analyze, and document your applications like senior UX designers.
This enterprise-grade MCP server transforms AI from code-only assistants into visual experts capable of UI analysis, accessibility auditing, documentation generation, and responsive design testing.
This package is now maintained in its own repository: [https://github.com/Digital-Defiance/mcp-screenshot](https://github.com/Digital-Defiance/mcp-screenshot)
This repository is part of the AI Capabilitites Suite on GitHub.
AI agents today are powerful but visually blind:
Result: You're stuck manually creating screenshots, documentation, and visual analysis that AI should handle.
You: "Document the checkout process with screenshots"
AI: *Captures each step, analyzes UI flow* AI: "Generated complete user guide with 6 annotated screenshots, highlighting key interactions and error states..."
You: "Check if this form meets WCAG guidelines"
AI: *Captures form, analyzes visual elements* AI: "Found 4 accessibility issues: contrast ratio 2.1:1 (needs 4.5:1), missing focus indicators, touch targets too small..."
You: "The mobile navigation is broken"
AI: *Captures different viewport sizes* AI: "Created bug report with before/after screenshots, exact breakpoint where it fails, and CSS fix suggestions..."
You: "Which hero section design works better?"
AI: *Captures both versions, analyzes visual hierarchy* AI: "Version B has 28% better visual flow—CTA more prominent, text hierarchy clearer, better use of whitespace..."
You: "How does this look on different screen sizes?"
AI: *Captures multiple viewport sizes* AI: "Layout breaks at 768px—sidebar overlaps content. Here's the media query fix with visual proof..."
Before: AI worked blind, relying on code descriptions
After: AI sees and analyzes your actual user interface
npm install @ai-capabilities-suite/mcp-screenshot
Linux:
imagemagick package (provides import command)grim package# Ubuntu/Debian
sudo apt-get install imagemagick grim
sudo dnf install ImageMagick grim
sudo pacman -S imagemagick grim
macOS:
screencapture command (no additional dependencies)Windows:
Add to your MCP settings file (e.g., ~/.kiro/settings/mcp.json or .kiro/settings/mcp.json):
{
"mcpServers": { "screenshot": { "command": "node", "args": ["/path/to/mcp-screenshot/dist/cli.js"], "env": { "SCREENSHOT_ALLOWED_DIRS": "/home/user/screenshots,/tmp", "SCREENSHOT_MAX_CAPTURES_PER_MIN": "60", "SCREENSHOT_ENABLE_AUDIT_LOG": "true" } } } }
Purpose-built for AI agents to capture, analyze, and work with visual information:
The server exposes 5 comprehensive MCP tools that enable AI agents to see and understand your applications:
Capture full screen or specific display.
Parameters:
display (string, optional): Display ID to capture (defaults to primary display)format (string, optional): Image format - png, jpeg, webp, or bmp (default: png)quality (number, optional): Compression quality 1-100 for lossy formats (default: 90)savePath (string, optional): File path to save screenshot (returns base64 if not provided)enablePIIMasking (boolean, optional): Enable PII detection and masking (default: false)Example:
{
"name": "screenshot_capture_full", "arguments": { "format": "png", "savePath": "/home/user/screenshots/desktop.png", "enablePIIMasking": true } }
Response:
{
"status": "success", "filePath": "/home/user/screenshots/desktop.png", "metadata": { "width": 1920, "height": 1080, "format": "png", "fileSize": 245678, "timestamp": "2024-12-01T10:30:00.000Z", "display": { "id": "0", "name": "Primary Display", "resolution": { "width": 1920, "height": 1080 }, "position": { "x": 0, "y": 0 }, "isPrimary": true }, "piiMasking": { "emailsRedacted": 2, "phonesRedacted": 1, "creditCardsRedacted": 0, "customPatternsRedacted": 0 } } }
Capture specific application window by ID or title pattern.
Parameters:
windowId (string, optional): Window identifier (use windowId or windowTitle)windowTitle (string, optional): Window title pattern to match (use windowId or windowTitle)includeFrame (boolean, optional): Include window frame and title bar (default: false)format (string, optional): Image format (default: png)quality (number, optional): Compression quality 1-100 (default: 90)savePath (string, optional): File path to save screenshotExample:
{
"name": "screenshot_capture_window", "arguments": { "windowTitle": "Chrome", "includeFrame": false, "format": "jpeg", "quality": 85 } }
Response:
{
"status": "success", "data": "iVBORw0KGgoAAAANSUhEUgAA...", "mimeType": "image/jpeg", "metadata": { "width": 1280, "height": 720, "format": "jpeg", "fileSize": 89234, "timestamp": "2024-12-01T10:31:00.000Z", "window": { "id": "12345", "title": "Google Chrome", "processName": "chrome", "pid": 5678, "bounds": { "x": 100, "y": 100, "width": 1280, "height": 720 } } } }
Capture specific rectangular region of the screen.
Parameters:
x (number, required): X coordinate of top-left cornery (number, required): Y coordinate of top-left cornerwidth (number, required): Width of region in pixelsheight (number, required): Height of region in pixelsformat (string, optional): Image format (default: png)quality (number, optional): Compression quality 1-100 (default: 90)savePath (string, optional): File path to save screenshotExample:
{
"name": "screenshot_capture_region", "arguments": { "x": 100, "y": 100, "width": 800, "height": 600, "format": "png" } }
Response:
{
"status": "success", "data": "iVBORw0KGgoAAAANSUhEUgAA...", "mimeType": "image/png", "metadata": { "width": 800, "height": 600, "format": "png", "fileSize": 123456, "timestamp": "2024-12-01T10:32:00.000Z", "region": { "x": 100, "y": 100, "width": 800, "height": 600 } } }
List all connected displays with resolution and position information.
Parameters: None
Example:
{
"name": "screenshot_list_displays", "arguments": {} }
Response:
{
"status": "success", "displays": [ { "id": "0", "name": "Primary Display", "resolution": { "width": 1920, "height": 1080 }, "position": { "x": 0, "y": 0 }, "isPrimary": true }, { "id": "1", "name": "Secondary Display", "resolution": { "width": 1920, "height": 1080 }, "position": { "x": 1920, "y": 0 }, "isPrimary": false } ] }
List all visible windows with title, process, and position information.
Parameters: None
Example:
{
"name": "screenshot_list_windows", "arguments": {} }
Response:
{
"status": "success", "windows": [ { "id": "12345", "title": "Google Chrome", "processName": "chrome", "pid": 5678, "bounds": { "x": 100, "y": 100, "width": 1280, "height": 720 }, "isMinimized": false }, { "id": "67890", "title": "Terminal", "processName": "gnome-terminal", "pid": 9012, "bounds": { "x": 200, "y": 200, "width": 800, "height": 600 }, "isMinimized": false } ] }
The server enforces security policies to control screenshot operations. Configure via environment variables or security policy file.
SCREENSHOT_ALLOWED_DIRS: Comma-separated list of allowed directories for saving screenshotsSCREENSHOT_MAX_CAPTURES_PER_MIN: Maximum captures per minute (default: 60)SCREENSHOT_ENABLE_AUDIT_LOG: Enable audit logging (default: true)SCREENSHOT_BLOCKED_WINDOWS: Comma-separated list of window title patterns to excludeCreate a security-policy.json file:
{
"allowedDirectories": ["/home/user/screenshots", "/tmp/screenshots"], "blockedWindowPatterns": [ ".*Password.*", ".*1Password.*", ".*LastPass.*", ".*Bitwarden.*", ".*Authentication.*" ], "maxCapturesPerMinute": 60, "enableAuditLog": true }
Load the policy when starting the server:
import { MCPScOnly the beginning is shown; read the rest in the repo