Best for
- Development workflows that need to provide screenshots to AI models
- AI coding tools like Claude Code, Cursor that support MCP
- Automated testing scenarios requiring full-page screenshots
M
MCP Screenshot Website Fast
Community
Fast, efficient webpage screenshots optimized for AI vision workflows.
GitHub source repository ↗
50FMRS · D
This server is optimized for AI workflows, capturing screenshots in a format ideal for vision models. The automatic tiling is excellent for full-page captures. Installation is straightforward across multiple clients. However, there is a resolution cap, and it relies on an external browser, which may require additional setup in some environments. Overall, it's reliable and practical.
This MCP server uses Puppeteer headless browser to quickly capture web page screenshots, automatically tiling full pages into 1072x1072 pixel chunks for optimal processing by AI models like Claude Vision API. It supports configurable viewports, wait strategies, selector capture, and screencast recording with optional animated WebP output. Designed for CLI coding tools like Claude Code, VS Code, Cursor, it integrates seamlessly into AI workflows.
Tools
take_screenshot
Captures a high-quality screenshot of a webpage, with options for viewport dimensions, fullPage tiling, wait conditions, and saving to a directory for file paths instead of base64.
capture_selector
Captures a screenshot of a specific DOM element matched by a CSS selector, with support for wait strategies and timeout.
take_screencast
Captures a series of screenshots over time to create a screencast, with configurable duration, interval, optional JavaScript execution, and saving as animated WebP.
Setup
For Claude Code: claude mcp add screenshot-website-fast -s user -- npx -y @just-every/mcp-screenshot-website-fast. For VS Code, use the code --add-mcp command or JSON config. For JetBrains IDEs, add via settings with JSON. Alternatively, add the JSON config to any MCP client's mcp.json.
claude_desktop_config.json
{
"mcpServers": {
"screenshot-website-fast": {
"command": "npx",
"args": [
"-y",
"@just-every/mcp-screenshot-website-fast"
]
}
}
}
Fit and risk
Not for
- Scenarios requiring high-resolution original screenshots (pixel limit)
- Real-time applications where latency is critical (no caching but still dependent on load times)
- Situations requiring complex browser interactions such as login or cookie management
Required permissions
- Network access to load target web pages
- Local file system access when saving screenshots to a directory
- Execution of Puppeteer, which downloads Chrome/Chromium browser
Risks and side effects
- Server crash may trigger auto-restart (with exponential backoff limit)
- Screenshots may contain sensitive information; handle accordingly
- Dependency on Puppeteer; network/firewall may block browser download
Troubleshooting
- If Puppeteer fails to download Chrome, set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true and provide custom executable
- If screenshot quality is poor, adjust viewport dimensions or wait strategies
- For timeout errors, increase wait time or use networkidle strategy
Use cases
Taking web page screenshots for AI vision workflows
Capturing specific elements for automated testing
Recording screencasts of dynamic page changes
Supported clients
Claude DesktopFull support
VS CodeFull support
CursorFull support
JetBrains IDEsFull support