Screenshotrender Mcp
Grab hosted URL screenshots from Claude Code or Cursor without opening a browser tab yourself.
Overview
ScreenshotRender MCP is an MCP server for the Launch phase that captures website screenshots from any URL via the ScreenshotRender API inside your agent.
What is this MCP server?
- Stdio MCP server (npm screenshotrender-mcp v1.0.1) wired to the ScreenshotRender hosted API
- Requires SCREENSHOTRENDER_API_KEY (sr- prefix) via environment variable
- Works from any MCP client that supports stdio npm packages
- Captures arbitrary public URLs for marketing, docs, and QA comparisons
- No local headless browser install—offloads rendering to ScreenshotRender
- Package version 1.0.1 on npm (identifier screenshotrender-mcp)
- Single required secret env var: SCREENSHOTRENDER_API_KEY
- Transport: stdio only in published server schema
What problem does it solve?
You need polished page previews for docs or launch posts, but spinning up local browser automation just to save a PNG wastes time and clutters your repo.
Who is it for?
Indie builders who want one-click URL screenshots inside Claude or Cursor for marketing, docs, and quick visual checks.
Skip if: Teams that need interactive E2E flows, DOM inspection, or offline/air-gapped rendering without a third-party API key.
What do I get? / Deliverables
Your agent can return hosted URL screenshots on demand so you ship visuals with landing pages, docs, and social copy in the same session.
- PNG or image output of a specified website URL via agent tool calls
- Reusable MCP config snippet for screenshot capture across projects
Recommended MCP Servers
Journey fit
Launch distribution is the canonical shelf because solo builders most often need shareable page captures for go-to-market assets, even though the same tool supports docs and prototype reviews. Distribution covers social previews, pitch decks, and partner emails where a rendered URL image is the deliverable.
How it compares
Hosted screenshot API bridge, not a Playwright-style test runner or full browser MCP.
Common Questions / FAQ
Who is ScreenshotRender MCP for?
Solo and indie builders using MCP clients who need shareable website images without running headless Chrome locally.
When should I use ScreenshotRender MCP?
Use it when you have a public or staging URL and need a screenshot for docs, launch assets, or quick layout comparison—not for scripted clicks or test assertions.
How do I add ScreenshotRender MCP to my agent?
Install the npm package screenshotrender-mcp (v1.0.1), set SCREENSHOTRENDER_API_KEY in your MCP config, and connect via stdio in Claude Code, Cursor, or another MCP host.