Screenshotrender Mcp

io.github.faridmthPublished by GitHub account faridmthv1.0.1Updated Oct 24, 2026

Capture website screenshots from any MCP client via the ScreenshotRender API.

VerifiedSTDIODesktop onlyBrowser AutomationMedia & Design

Overview

AI-generated overview

Wraps the ScreenshotRender API so an assistant can capture screenshots of public web pages and return the image inline with a hosted URL.

What you can do
  • Capture a screenshot of any public URL, with options for full-page capture, a wait delay before capture, and a load timeout.
  • Receive the image inline in the chat together with a hosted URL and page metadata such as title and description.
When to use it
Useful when you want an assistant to render a live public web page and show it in the conversation, for example to check how a site looks or to grab a full-page capture without leaving the chat.
Requirements
Runs locally over stdio, typically launched with npx from the npm package screenshotrender-mcp, so Node.js is needed. Requires a ScreenshotRender API key supplied in the SCREENSHOTRENDER_API_KEY environment variable; an optional SCREENSHOTRENDER_BASE_URL can override the API base URL. Network access to the ScreenshotRender service is required.
Before you install
The API key in SCREENSHOTRENDER_API_KEY is a secret and is sent to the ScreenshotRender service; usage may be billed by that provider. Requested page URLs are sent to a third party, and the resulting image is also stored at a hosted URL. Only public pages should be captured.

Installation

In SourceWeft

  1. Open Screenshotrender Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ScreenshotRender MCP server

Capture website screenshots from inside Claude, Cursor, VS Code, Windsurf, or any Model Context Protocol client. This server wraps the ScreenshotRender API so your AI assistant can render any public web page on request.

Ask your assistant: "Take a full-page screenshot of stripe.com" and the image appears right in the chat.

Tools

ToolDescription
take_screenshotCapture a screenshot of any public URL. Returns the image inline plus a hosted URL and page metadata (title, description).

Parameters

  • url (string, required) — page to capture, including https://.
  • fullPage (boolean, optional) — capture the entire scrollable page instead of the viewport.
  • wait (number, optional) — milliseconds to wait before capturing (for animations / lazy content).
  • timeout (number, optional) — max milliseconds to wait for load.

Setup

  1. Get your API key at screenshotrender.com (it starts with sr-).
  2. Add the server to your MCP client config.

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

json
{  "mcpServers": {    "screenshotrender": {      "command": "npx",      "args": ["-y", "screenshotrender-mcp"],      "env": {        "SCREENSHOTRENDER_API_KEY": "sr-your-key-here"      }    }  }}

Cursor / VS Code / Windsurf

Add the same block under the editor's MCP settings (mcp.json or the MCP settings UI). Restart the client and the take_screenshot tool will be available.

Environment variables

VariableRequiredDescription
SCREENSHOTRENDER_API_KEYyesYour ScreenshotRender key (sr-...).
SCREENSHOTRENDER_BASE_URLnoOverride the API base URL. Defaults to https://screenshotrender.com.

Local development

bash
npm installSCREENSHOTRENDER_API_KEY=sr-your-key npm run inspect   # opens MCP Inspector

The Inspector lets you call take_screenshot and view the result before shipping.

License

MIT

Source: README.md at commit 092d24c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts