This MCP server provides fast, tiling-based web page screenshot capture designed for AI workflows. It runs the @just-every/mcp-screenshot-website-fast package via npx, exposing tools to capture high-quality screenshots, tile full pages into 1072x1072 segments, and generate screencasts. The server integrates with MCP-enabled IDEs and clients, enabling you to request take_screenshot or take_screencast operations as part of your AI pipelines. Use it to generate consistently sized image tiles for vision models, or to create screencasts for temporal analysis. The available tooling supports configuring viewport size, tiling behavior, wait strategies, and output directories for saved files or frames.

Within an MCP-enabled environment you can invoke the screenshot tool to capture a URL, optionally saving results to a directory, or request a screencast sequence over time. The module is optimized for Claude Vision and similar models by enforcing a fixed tile size and default full-page tiling, ensuring predictable input dimensions for downstream processing.

Prerequisites:

• Node.js 20.x or higher
• npm or pnpm
• Chromium/Chrome (Puppeteer installs it automatically on first run)

Installation steps:

1. Install Node.js (20.x) from https://nodejs.org/
2. Ensure npm is available: npm -v
3. Install or configure MCP client integration in your IDE or toolchain (the MCP protocol client or support in your IDE)
4. Install the MCP server package via npx (the server is run through your MCP client). Example usage below:

Code:

Quick run via MCP config (no local install required beyond Node)

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

Alternative: add to your MCP JSON config (example shown in the raw JSON section of the README) and load it through your MCP client.

Note: The first run may download Chromium automatically through Puppeteer; ensure network access is allowed for the installation and browser download.

Tips and considerations:

• The server uses Puppeteer to launch a headless browser and capture full-page screenshots. Ensure your environment allows headless browser operation.
• Default tiling creates 1072x1072 tiles. If you need different tile sizes, you may need to adjust the underlying tool or configuration (via the MCP client if supported).
• Auto-restart is enabled for reliability; for debugging without auto-restart, you can run the underlying dev server directly (npm run serve:dev) as described in the README.
• prerequisites include a compatible Node.js version and a functioning setup for MCP integration in your IDE or toolchain.
• When using the take_screenshot tool, you can specify a directory to save tiles and file paths will be returned instead of base64 data.
• For screencasts, only the top 1072x1072 tile is captured per frame; you can adjust duration and interval to tailor the frame count.