MCP Screenshot Server

Created By
sethbanga year ago
A MCP server for capturing screenshots
Overview

what is MCP Screenshot Server?

MCP Screenshot Server is a server implementation that allows users to capture screenshots of web pages and local HTML files using Puppeteer.

how to use MCP Screenshot Server?

To use the MCP Screenshot Server, install the project using npm, and utilize the take_screenshot tool by providing the necessary options such as URL, viewport dimensions, and output path.

key features of MCP Screenshot Server?

  • Capture screenshots of any web page or local HTML file
  • Configurable viewport dimensions
  • Full page screenshot support
  • Custom output path option
  • Automatic screenshot directory management

use cases of MCP Screenshot Server?

  1. Capturing website previews for documentation.
  2. Automating screenshot generation for testing web applications.
  3. Creating visual content for presentations or reports.

FAQ from MCP Screenshot Server?

  • Can I capture screenshots of local HTML files?

Yes! The server supports capturing screenshots from both web pages and local HTML files.

  • Is there a limit to the viewport dimensions?

Yes, the viewport width can be between 1-3840 pixels and height between 1-2160 pixels.

  • What license is MCP Screenshot Server under?

MCP Screenshot Server is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sethbang
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago