mcpField
S
Shotpipe — Screenshots & OG Images

Shotpipe — Screenshots & OG Images

Local
shotpipe.ioBrowser Automation0Updated 14w ago
RepositoryVisit website

About Shotpipe — Screenshots & OG Images

Shotpipe MCP is a hosted screenshot and Open Graph image service for AI agents. It captures URL pages as images or creates social-card links, with rendering on Shotpipe infrastructure, caching, and SSRF protection for untrusted URLs.

Key features

  1. 01Return webpage screenshots as images
  2. 02Create signed social-card URLs
  3. 03Support multiple screenshot formats and options
  4. 04Cache screenshot results
  5. 05Remove ads and cookie banners by default

Use cases

  1. 01Let an agent inspect a rendered webpage
  2. 02Generate social-card links for pages or build workflows
  3. 03Capture pages from user-provided URLs

MCP support

The MCP server exposes `screenshot` and `og_image` tools to clients. It uses Shotpipe's hosted service to render pages and returns screenshot images or signed image URLs.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "podop29-shotpipe": {
      "command": "npx",
      "args": [
        "-y",
        "shotpipe-mcp"
      ],
      "env": {
        "SHOTPIPE_KEY": "<SHOTPIPE_KEY>",
        "SHOTPIPE_SECRET": "<SHOTPIPE_SECRET>",
        "SHOTPIPE_BASE_URL": "<SHOTPIPE_BASE_URL>"
      }
    }
  }
}
Run commandnpx -y shotpipe-mcp
Environment variables to set
SHOTPIPE_KEYSecretShotpipe API key id (starts with k_). Free at https://shotpipe.io/signup.
SHOTPIPE_SECRETSecretShotpipe HMAC signing secret. Requests are signed locally; the secret never leaves the process.
SHOTPIPE_BASE_URLOverride the API base URL for a self-hosted Shotpipe instance. Defaults to https://shotpipe.io.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmshotpipe-mcp0.1.1

Tools

2

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
dprenumNoDevice pixel ratio (retina). Default 1.1 | 2 | 3
urlstringYesThe page URL to capture (http/https).
darkbooleanNoEmulate prefers-color-scheme: dark.
delayintegerNoExtra settle time in ms before capture.
freshbooleanNoBypass the cache and force a fresh render.
widthintegerNoViewport width in px. Default 1200.
formatenumNoOutput format. Default png.png | jpeg | pdf
heightintegerNoViewport height in px. Default 630.
qualityintegerNoJPEG quality 1-100 (format=jpeg only).
selectorstringNoCSS selector — clip the shot to this element.
wait_forstringNoCSS selector to wait for before capturing.
block_adsbooleanNoBlock ad/tracker requests. Default true.
full_pagebooleanNoCapture the full scrollable page, not just the viewport.
block_bannersbooleanNoHide cookie-consent banners. Default true.
omit_backgroundbooleanNoTransparent background (png only).

Details

From the project README

shotpipe-mcp

Hosted, SSRF-safe, cached screenshots and Open Graph images for AI agents — no headless Chrome to run.

An MCP server that lets an agent screenshot any URL and see the result, or mint a social-card image, by calling Shotpipe. It's the thing a local browser tool can't be:

  • No Chrome in your agent's sandbox. Rendering happens on Shotpipe's infrastructure. Nothing to install, no memory to babysit, no OOM at 2am.
  • Safe on untrusted URLs. Agents point at URLs their users typed. Shotpipe resolves DNS itself, pins the IP, re-checks every redirect, and refuses private / loopback / cloud-metadata hosts — so a hostile link can't turn your renderer into an SSRF hole.
  • Cached. The first capture renders; every identical one after is served from the edge in milliseconds and costs nothing.

Ad and cookie-consent banners are stripped by default.

Install

// Claude Desktop (claude_desktop_config.json), Claude Code (.mcp.json),
// Cursor, Cline, or any MCP client:
{
  "mcpServers": {
    "shotpipe": {
      "command": "npx",
      "args": ["-y", "shotpipe-mcp"],
      "env": {
        "SHOTPIPE_KEY": "k_your_key",
        "SHOTPIPE_SECRET": "your_signing_secret"
      }
    }
  }
}

Get a free key at shotpipe.io/signup (no card) or run npx shotpipe-init. Self-hosting Shotpipe? Set SHOTPIPE_BASE_URL.

Tools

screenshot

Screenshot a URL and return the image (so the model can see it) plus a permanent, shareable signed URL.

url (required) · format png|jpeg|pdf · width · height · dpr · full_page · selector · dark · omit_background · block_ads · block_banners · wait_for · delay · quality · fresh

og_image

Build a signed social-card URL from a hosted template. Returns the URL only by default and renders nothing — the image renders lazily on the first crawler hit, so agent/build time stays fast. Drop it into <meta property="og:image">. Pass render: true to also get a preview image.

title (required) · template · author · tag · accent · logo · width · height · dpr · render

How it works

The signing secret never leaves the process — every request is HMAC-signed locally, exactly like Shotpipe's other clients. The server just builds a signed URL and (for screenshot) fetches the bytes.

MIT · shotpipe.io

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.