Screenshotrender MCP vs Universal Screenshot MCP
A side-by-side look at the Screenshotrender MCP and Universal Screenshot MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Screenshotrender MCP for browser automation work as a local process; choose Universal Screenshot MCP for browser automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Screenshotrender MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
SCREENSHOTRENDER_API_KEY, SCREENSHOTRENDER_BASE_URL. - You want tools like
take_screenshot.
Choose Universal Screenshot MCP when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
take_screenshot, take_system_screenshot.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Browser Automation | Browser Automation |
| Quality signal | 48/100 · Fair | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SCREENSHOTRENDER_API_KEYSCREENSHOTRENDER_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 35 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 1 | 2 |
| Full listing | View Screenshotrender MCP | View Universal Screenshot MCP |
Tools & capabilities
Screenshotrender MCP tools 1
take_screenshotCapture a screenshot of any public URL. Returns the image inline plus a hosted URL and page metadata (title, description).
Universal Screenshot MCP tools 2
take_screenshotCaptures a web page (or a specific element) via a headless Puppeteer browser.take_system_screenshotCaptures the desktop, a specific application window, or a screen region using native OS tools. Works on **macOS**, **Linux**, and **Windows**.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Screenshotrender MCP
{
"mcpServers": {
"screenshotrender-mcp": {
"command": "npx",
"args": [
"-y",
"screenshotrender-mcp"
],
"env": {
"SCREENSHOTRENDER_API_KEY": "YOUR_SCREENSHOTRENDER_API_KEY_HERE",
"SCREENSHOTRENDER_BASE_URL": "YOUR_SCREENSHOTRENDER_BASE_URL_HERE"
}
}
}
}
Universal Screenshot MCP
{
"mcpServers": {
"universal-screenshot-mcp": {
"command": "npx",
"args": [
"-y",
"universal-screenshot-mcp"
]
}
}
}
Frequently asked questions
Screenshotrender MCP is categorized under Browser Automation and uses a local stdio subprocess. Universal Screenshot MCP belongs to Browser Automation and uses a local stdio subprocess. Pick Screenshotrender MCP for browser automation work and Universal Screenshot MCP for browser automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Screenshotrender MCP has no declared pricing — check the project's own site. Universal Screenshot MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add screenshotrender-mcp and universal-screenshot-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Screenshotrender MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Universal Screenshot MCP has 59/100 (Good) with 1 views, 0 installs and 35 GitHub stars.
