Capture website screenshots from any MCP client via the ScreenshotRender API.
Capture website screenshots from any MCP client via the ScreenshotRender API. That is what the screenshotrender mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
sr-). 2. Add the server to your MCP client config.The server publishes 1 tool. What each one is for:
take_screenshot — Capture a screenshot of any public URL. Returns the image inline plus a hosted URL and page metadata (title, description)Configuration is passed through the environment: SCREENSHOTRENDER_API_KEY, SCREENSHOTRENDER_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Screenshotrender's toolset — take_screenshot — is a fair guide to whether it matches your workflow. It is maintained by faridmth; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| take_screenshot | Capture a screenshot of any public URL. Returns the image inline plus a hosted URL and page metadata (title, description). |
{
"mcpServers": {
"screenshotrender": {
"command": "npx",
"args": ["-y", "screenshotrender-mcp"],
"env": {
"SCREENSHOTRENDER_API_KEY": "sr-your-key-here"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SCREENSHOTRENDER_API_KEY | Credential the server authenticates with. | Yes |
| SCREENSHOTRENDER_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.