What is Mcp Screenshot Website Fast

mcp-screenshot-website-fast is a fast and efficient screenshot capture tool designed specifically for web pages. It optimizes screenshots for AI vision workflows, particularly for the Claude Vision API, by automatically tiling full pages into 1072x1072 pixel chunks for optimal processing.

Use cases

Use cases include capturing screenshots for AI model training, generating visual content for reports, testing website responsiveness, and ensuring up-to-date visual representations of web pages.

How to use

To use mcp-screenshot-website-fast, you can install it via MCP with the command: claude mcp add screenshot-website-fast -s user -- npx -y @just-every/mcp-screenshot-website-fast. Alternatively, you can add it to VS Code or use it with Cursor for installation.

Key features

Key features include fast screenshot capture using Puppeteer, automatic resolution limiting to 1072x1072 pixels, automatic tiling of full pages, no caching for fresh content, configurable viewports for responsive testing, wait strategies for dynamic content, full page capture by default, minimal dependencies, and seamless MCP integration.

Where to use

mcp-screenshot-website-fast is ideal for use in AI development environments, web scraping, quality assurance testing, and any application requiring high-quality screenshots of web pages for analysis or processing.

@just-every/mcp-screenshot-website-fast

Fast, efficient screenshot capture tool for web pages - optimized for Claude Vision API. Automatically tiles full pages into 1072x1072 chunks for optimal AI processing.

Overview

Built specifically for AI vision workflows, this tool captures high-quality screenshots with automatic resolution limiting and tiling for optimal processing by Claude Vision API and other AI models. It ensures screenshots are perfectly sized at 1072x1072 pixels (1.15 megapixels) for maximum compatibility.

Features

• 📸 Fast screenshot capture using Puppeteer headless browser
• 🎯 Claude Vision optimized with automatic resolution limiting (1072x1072 for optimal 1.15 megapixels)
• 🔲 Automatic tiling - Full pages are automatically split into 1072x1072 tiles
• 🔄 Always fresh content - No caching ensures up-to-date screenshots
• 📱 Configurable viewports for responsive testing
• ⏱️ Wait strategies for dynamic content (networkidle, custom delays)
• 📄 Full page capture by default for complete page screenshots
• 📦 Minimal dependencies for fast npm installs
• 🔌 MCP integration for seamless AI workflows

Installation

Claude Code

claude mcp add screenshot-website-fast -s user -- npx -y @just-every/mcp-screenshot-website-fast

VS Code

code --add-mcp '{"name":"screenshot-website-fast","command":"npx","args":["-y","@just-every/mcp-screenshot-website-fast"]}'

Cursor

cursor://anysphere.cursor-deeplink/mcp/install?name=screenshot-website-fast&config=eyJzY3JlZW5zaG90LXdlYnNpdGUtZmFzdCI6eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBqdXN0LWV2ZXJ5L21jcC1zY3JlZW5zaG90LXdlYnNpdGUtZmFzdCJdfX0=

JetBrains IDEs

Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add

Choose “As JSON” and paste:

{
  "command": "npx",
  "args": [
    "-y",
    "@just-every/mcp-screenshot-website-fast"
  ]
}

Raw JSON (works in any MCP client)

{
  "mcpServers": {
    "screenshot-website-fast": {
      "command": "npx",
      "args": [
        "-y",
        "@just-every/mcp-screenshot-website-fast"
      ]
    }
  }
}

Drop this into your client’s mcp.json (e.g. .vscode/mcp.json, ~/.cursor/mcp.json, or .mcp.json for Claude).

Prerequisites

• Node.js 20.x or higher
• npm or npx
• Chrome/Chromium (automatically downloaded by Puppeteer)

Quick Start

MCP Server Usage

Once installed in your IDE, the following tools are available:

Available Tools

• screenshot_website_fast - Captures a high-quality screenshot of a webpage
  • Parameters:
    • url (required): The HTTP/HTTPS URL to capture
    • width (optional): Viewport width in pixels (max 1072, default: 1072)
    • height (optional): Viewport height in pixels (max 1072, default: 1072)
    • fullPage (optional): Capture full page screenshot (default: true)
    • waitUntil (optional): Wait until event: load, domcontentloaded, networkidle0, networkidle2 (default: networkidle2)
    • waitFor (optional): Additional wait time in milliseconds

Development Usage

Install

npm install
npm run build

Capture screenshot

# Full page with automatic tiling (default)
npm run dev capture https://example.com -o screenshot.png

# Viewport-only screenshot  
npm run dev capture https://example.com --no-full-page -o screenshot.png

# Wait for specific conditions
npm run dev capture https://example.com --wait-until networkidle0 --wait-for 2000 -o screenshot.png

CLI Options

• -w, --width <pixels> - Viewport width (max 1072, default: 1072)
• -h, --height <pixels> - Viewport height (max 1072, default: 1072)
• --no-full-page - Disable full page capture and tiling
• --wait-until <event> - Wait until event: load, domcontentloaded, networkidle0, networkidle2
• --wait-for <ms> - Additional wait time in milliseconds
• -o, --output <path> - Output file path (required for tiled output)

Architecture

mcp-screenshot-website-fast/
├── src/
│   ├── internal/       # Core screenshot capture logic
│   ├── utils/          # Logger and utilities
│   ├── index.ts        # CLI entry point
│   └── serve.ts        # MCP server entry point

Development

# Run in development mode
npm run dev capture https://example.com -o screenshot.png

# Build for production
npm run build

# Run tests
npm test

# Type checking
npm run typecheck

# Linting
npm run lint

Why This Tool?

Built specifically for AI vision workflows:

1. Optimized for Claude Vision API - Automatic resolution limiting to 1072x1072 pixels (1.15 megapixels)
2. Automatic tiling - Full pages split into perfect chunks for AI processing
3. Always fresh - No caching ensures you get the latest content
4. MCP native - First-class integration with AI development tools
5. Simple API - Clean, straightforward interface for capturing screenshots

Contributing

Contributions are welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Add tests for new functionality
4. Submit a pull request

Troubleshooting

Puppeteer Issues

• Ensure Chrome/Chromium can be downloaded
• Check firewall settings
• Try setting PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true and provide custom executable

Screenshot Quality

• Adjust viewport dimensions
• Use appropriate wait strategies
• Check if site requires authentication

Timeout Errors

• Increase wait time with --wait-for flag
• Use different --wait-until strategies
• Check if site is accessible

License

MIT