just-every/mcp-screenshot-website-fast
MCP ServerFree** - High-quality screenshot capture optimized for Claude Vision API. Automatically tiles full pages into 1072x1072 chunks (1.15 megapixels) with configurable viewports and wait strategies for dynamic content.
Capabilities11 decomposed
claude vision api-optimized screenshot capture with automatic tiling
Medium confidenceCaptures full-page website screenshots and automatically tiles them into 1072x1072 pixel chunks (1.15 megapixels) using Sharp image processing, optimizing for Claude Vision API's token efficiency and visual processing constraints. The system constrains all viewport dimensions to maximum 1072x1072 to ensure each tile fits within optimal vision model input boundaries without requiring external image resizing or post-processing.
Implements automatic tiling specifically calibrated to Claude Vision API's 1.15 megapixel optimal input size, using Sharp for efficient image chunking rather than generic screenshot tools that require manual post-processing. The 1072x1072 constraint is baked into the viewport configuration itself, not applied after capture.
Unlike Playwright or Puppeteer screenshot methods that capture at arbitrary resolutions requiring external tiling, this tool bakes Claude Vision optimization into the capture pipeline, eliminating post-processing overhead and ensuring consistent token efficiency.
configurable wait strategies for dynamic content stabilization
Medium confidenceImplements multiple wait strategies (networkIdle, domContentLoaded, custom JavaScript conditions) to ensure dynamic content has fully loaded before capture, with configurable timeouts and retry logic. The system injects JavaScript probes to detect application-specific readiness conditions (e.g., React hydration, data fetch completion) rather than relying solely on browser network events.
Combines multiple wait strategies (networkIdle, domContentLoaded, custom JavaScript probes) with retry logic and timeout handling, allowing detection of application-specific readiness states via injected JavaScript rather than generic browser events. The architecture supports both framework-agnostic network-based waits and framework-aware custom conditions.
More sophisticated than Puppeteer's default waitForNavigation (which only handles network events), this system allows custom JavaScript condition injection for framework-specific readiness detection, making it suitable for modern SPAs that don't follow traditional page load patterns.
sharp-based image processing and tiling pipeline
Medium confidenceUses the Sharp image processing library to efficiently tile full-page screenshots into 1072x1072 chunks, handling image format conversion, compression, and metadata extraction. The tiling pipeline processes captured PNG images through Sharp's streaming API, splitting large images into overlapping or non-overlapping tiles based on configuration, and returning tile metadata with coordinate information.
Leverages Sharp's high-performance image processing library for efficient tiling, using streaming APIs to minimize memory overhead. The tiling pipeline is optimized for the specific 1072x1072 constraint, avoiding generic image resizing or cropping overhead.
More efficient than canvas-based tiling or ImageMagick, Sharp provides native Node.js bindings with streaming support, enabling fast tiling of large images without excessive memory consumption or process spawning.
headless browser lifecycle management with auto-restart and signal handling
Medium confidenceManages Chromium browser process lifecycle with automatic restart on crash, graceful shutdown on signals (SIGTERM, SIGINT), and connection pooling to reuse browser instances across multiple screenshot operations. The system implements a serve-restart wrapper that monitors the main MCP server process and automatically restarts it if it crashes, maintaining availability for long-running AI agent workflows.
Implements a two-tier process architecture (serve-restart wrapper + main MCP server) that monitors and auto-restarts the screenshot service on crash, combined with graceful signal handling for clean shutdown. This pattern is distinct from simple browser pooling — it ensures the entire service remains available even if the underlying browser process crashes.
Unlike Puppeteer or Playwright used directly (which require manual crash handling), this tool wraps the entire screenshot service with automatic restart logic, making it suitable for production AI agent deployments where availability is critical.
screencast recording with adaptive frame rates and webp animation
Medium confidenceRecords time-series screenshots of page interactions as WebP animations with adaptive frame rate selection based on content change detection. The system captures PNG frames at configurable intervals, deduplicates identical frames to reduce file size, and encodes the sequence into WebP animations using Sharp, enabling efficient video-like capture of dynamic page behavior without full video codec overhead.
Combines adaptive frame rate capture with pixel-level deduplication and WebP animation encoding, allowing efficient time-series recording of page state changes. The system injects JavaScript to detect content changes and adjust frame capture intervals dynamically, reducing redundant frames while maintaining visual fidelity.
More efficient than full video recording (no codec overhead) and more intelligent than fixed-interval frame capture (deduplication reduces file size by 30-50% for static content), making it ideal for AI vision analysis of page interactions without excessive token consumption.
javascript console message capture with execution context
Medium confidenceCaptures console output (log, error, warn, info) during page execution with full execution context, including message content, severity level, and timestamp. The system injects a JavaScript listener that intercepts console methods and collects messages over a specified duration, returning structured JSON with all captured messages for analysis by AI models.
Implements JavaScript injection-based console interception that captures all console method calls with structured metadata (level, timestamp, message), providing a machine-readable log of page execution behavior. This is distinct from browser DevTools protocol logging, which requires additional parsing.
More accessible than raw CDP (Chrome DevTools Protocol) console logging, this approach provides structured JSON output directly suitable for AI analysis without requiring additional parsing or protocol handling.
mcp protocol integration with stdio json-rpc transport
Medium confidenceExposes screenshot and screencast capabilities as MCP tools via stdio-based JSON-RPC transport, enabling integration with Claude Code, VS Code, Cursor, and JetBrains IDEs. The system implements the Model Context Protocol specification, serializing tool requests/responses as JSON-RPC messages over stdin/stdout, allowing AI assistants to invoke screenshot operations as native tools.
Implements full Model Context Protocol compliance with stdio JSON-RPC transport, exposing screenshot operations as native MCP tools that Claude and other AI assistants can invoke directly. The architecture includes proper tool schema definition, error handling, and response serialization.
Unlike REST API or direct library integration, MCP protocol integration allows Claude and other AI assistants to treat screenshot capture as a first-class tool with proper schema validation and error handling, enabling more reliable AI-driven web automation.
cli binary interface with direct command-line screenshot execution
Medium confidenceProvides a command-line interface (bin/mcp-screenshot-website.js) for direct screenshot capture without MCP server overhead, enabling scripting, testing, and manual screenshot operations. The CLI accepts URL, viewport, wait strategy, and output format parameters, executing the screenshot capture engine directly and returning results as files or base64-encoded output.
Provides a lightweight CLI entry point that bypasses MCP server overhead for one-off screenshot operations, using the same underlying screenshot engine as the MCP server but with direct process invocation and file-based output.
Simpler than running a full MCP server for single screenshot operations, this CLI approach is ideal for scripting and testing but trades concurrency and performance for simplicity.
viewport configuration with constraint enforcement
Medium confidenceAllows configuration of browser viewport dimensions (width, height) with automatic constraint enforcement to ensure all viewports are clamped to maximum 1072x1072 pixels. The system validates viewport parameters at request time and rejects or clamps oversized viewports to maintain compatibility with Claude Vision API tiling constraints.
Implements viewport configuration with hard constraint enforcement at the request level, ensuring all screenshots comply with Claude Vision API tiling requirements. The system validates and clamps viewport parameters rather than allowing arbitrary resolutions.
Unlike generic screenshot tools that allow arbitrary viewport sizes, this system enforces vision API constraints at configuration time, preventing downstream tiling failures and ensuring consistent output.
base64 and file-based output encoding with format selection
Medium confidenceSupports multiple output formats for screenshot results: base64-encoded PNG for embedding in JSON responses (suitable for MCP protocol), and file-based PNG output for CLI and direct file storage. The system handles encoding/decoding transparently based on output format selection, enabling flexible integration with different transport mechanisms.
Provides transparent encoding/decoding abstraction that supports both base64 (for JSON-RPC transport) and file-based output, allowing the same screenshot engine to serve both MCP and CLI use cases without format conversion overhead.
More flexible than tools that support only one output format, this dual-mode approach enables seamless integration with both JSON-RPC-based MCP servers and file-based CLI workflows.
page navigation with retry logic and error recovery
Medium confidenceImplements robust page navigation with automatic retry on transient failures, timeout handling, and detailed error reporting. The system attempts to navigate to the target URL with configurable retry counts and backoff strategies, capturing detailed error information (network errors, timeouts, navigation failures) for debugging and fallback handling.
Combines automatic retry with exponential backoff and detailed error reporting, providing resilient navigation suitable for production workflows. The system captures full error context (network errors, timeouts, navigation failures) for debugging and fallback handling.
More robust than basic Puppeteer navigation (which fails on first error), this approach implements production-grade retry logic with backoff and detailed error reporting, making it suitable for unreliable network environments.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with just-every/mcp-screenshot-website-fast, ranked by overlap. Discovered automatically through the match graph.
@browserstack/mcp-server
BrowserStack's Official MCP Server
Claude Code UI
Beautiful Claude Code UI Interface for VS Code
@executeautomation/playwright-mcp-server
Model Context Protocol servers for Playwright
@browserstack/mcp-server
BrowserStack's Official MCP Server
Anthropic Cookbook
Official Anthropic recipes for building with Claude.
Claude
Talk to Claude, an AI assistant from Anthropic.
Best For
- ✓AI developers building Claude-integrated web automation agents
- ✓Teams building vision-based web testing and monitoring systems
- ✓Developers integrating screenshot capture into MCP-compatible AI development environments
- ✓Developers testing single-page applications with complex initialization
- ✓Teams building web scraping agents that need to handle dynamic content
- ✓QA automation engineers validating rendered state of JavaScript-heavy applications
- ✓Developers building vision model integration pipelines
- ✓Teams processing large images with memory constraints
Known Limitations
- ⚠Fixed 1072x1072 tile size cannot be customized — designed specifically for Claude Vision API constraints
- ⚠Tiling process adds latency proportional to page height (full-page screenshots of 10,000px+ pages may take 5-10 seconds)
- ⚠Sharp image processing requires sufficient system memory for large pages; very large pages (50MB+) may cause memory pressure
- ⚠Custom JavaScript condition detection requires knowledge of application internals; generic 'wait for element' patterns may not work across different frameworks
- ⚠Timeout-based waits add latency (default 30 seconds) — slow or unresponsive pages will hit timeout and capture incomplete state
- ⚠No built-in detection for infinite loading states; pages that continuously fetch data will timeout rather than capture partial state
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - High-quality screenshot capture optimized for Claude Vision API. Automatically tiles full pages into 1072x1072 chunks (1.15 megapixels) with configurable viewports and wait strategies for dynamic content.
Categories
Alternatives to just-every/mcp-screenshot-website-fast
Are you the builder of just-every/mcp-screenshot-website-fast?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →