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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago