mcp-screenshot-website-fast

This MCP server provides fast, automated web page screenshot capture tailored for AI workflows. It uses a headless Chromium browser (via Puppeteer) to take high-quality screenshots, automatically tiles full-page captures into 1072x1072 tiles for efficient downstream processing, and supports screencasts that record a sequence of frames over time. The server is designed for Claude Vision and similar AI models, ensuring consistent tile sizes and fresh content (no caching). Available tools include take_screenshot for single or tiled captures and take_screencast for time-lapse captures. You can specify viewport dimensions, whether to capture the full page, and wait strategies to accommodate dynamic content. Integration with MCP means you can invoke these tools from IDEs like VS Code, JetBrains IDEs, or through standard MCP clients by passing a URL and optional parameters.

Typical usage flows involve invoking take_screenshot with a target URL to get either a base64 image or a set of file paths when you choose to save to a directory. For tiled captures, each 1072x1072 tile is produced as a separate output. The take_screencast tool captures multiple frames over a duration, producing an animated WebP when saved to a directory. Both tools support optional JavaScript injection before capture, wait strategies, and additional wait times to ensure dynamic content settles before capture. The MCP wrapper handles automatic browser cleanup after periods of inactivity and can restart on crashes to maintain reliability in development environments.

Examples of capabilities you’ll likely use:

• take_screenshot(url, width, height, fullPage) to grab a full-page screenshot tiled into 1072x1072 tiles.
• take_screencast(url, duration, interval, directory) to generate an animated WebP screencast and save frames as PNGs for debugging.
• Optional parameters like waitUntil, waitFor, and jsEvaluate let you control timing and pre-capture DOM state for stable results.

Prerequisites:

• Node.js 20.x or higher
• npm or npx
• Chrome/Chromium (Puppeteer can download it automatically)

Installation steps:

1. Ensure prerequisites are installed. Verify versions, for example:

node -v
npm -v

2. Add the MCP server to your environment using the MCP client (example in Claude/VS Code prompts):

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

This registers the MCP server under the name screenshot-website-fast with the command to run via npx.

3. Alternatively, if you prefer direct JSON configuration for your MCP client, use:

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

4. If you’re integrating into a project, you can install the package directly and run it via npx in your scripts as shown in the README examples, including the Quick Start snippets for MCP usage.

5. For development tooling, you can install dependencies and build if you’re contributing to the server code:

npm install
npm run build

Notes and tips:

• Prerequisites specify Node.js 20+. Ensure your environment meets this requirement to avoid runtime issues.
• The server is optimized for 1072x1072 tiles; adjust viewport settings via the tool’s parameters if needed, but keep in mind the default tiling behavior.
• Automatic browser cleanup occurs after 60 seconds of inactivity to conserve resources; in long-running sessions you may want to trigger new captures to recycle the browser instance.
• The MCP integration enables seamless AI workflow automation; if you run into issues, check the restart wrapper (serve-restart) and the auto-restart feature for stability.
• When using take_screenshot with directory output, you’ll get file paths for saved tiles instead of embedded data; this is helpful for batch processing pipelines.
• The server supports JavaScript injection before capture (jsEvaluate) to modify page state prior to taking screenshots.
• If you need to debug or develop locally, you can run the dev capture commands shown in the Development section of the README to avoid the auto-restart feature.