ScreenshotRender MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCREENSHOTRENDER_API_KEY | Yes | Your ScreenshotRender key (starts with sr-). | |
| SCREENSHOTRENDER_BASE_URL | No | Override the API base URL. Defaults to https://screenshotrender.com. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| take_screenshotA | Capture a screenshot of any public website using ScreenshotRender. Returns the rendered image inline plus a hosted URL and basic page metadata (title, description). Use this whenever the user wants to see, save, or share what a web page looks like. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The purpose is singular and clear.
A single tool named 'take_screenshot' is consistent with itself and uses a clear verb_noun pattern. No inconsistency exists.
One tool is minimal but appropriate for a focused screenshot-capturing server. It does not feel too thin given the narrow scope, though additional options could be considered.
The tool covers the core action of taking a screenshot, but lacks common customization parameters such as viewport size, format selection, or full-page capture, which limits completeness.