Skip to main content
Glama
faridmth

ScreenshotRender MCP Server

by faridmth
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

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

Tool

Description

take_screenshot

Capture 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.

Related MCP server: MCP Browser Screenshot Server

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):

{
  "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

Variable

Required

Description

SCREENSHOTRENDER_API_KEY

yes

Your ScreenshotRender key (sr-...).

SCREENSHOTRENDER_BASE_URL

no

Override the API base URL. Defaults to https://screenshotrender.com.

Local development

npm install
SCREENSHOTRENDER_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

Available Tools

1 tool
take_screenshotTake 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.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the page to screenshot. Include the scheme (https://). Example: https://stripe.com
fullPageNoCapture the entire scrollable page instead of just the 1280x720 viewport. Defaults to false.
waitNoMilliseconds to wait after load before capturing, for pages with animations or lazy content. Defaults to none.
timeoutNoMaximum milliseconds to wait for the page to load.

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavior. It mentions returning image inline, hosted URL, and metadata, but does not discuss failure modes for private sites, rate limits, or auth requirements. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: first states action and output, second gives usage guidance. No wasted words. Front-loaded and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description covers the main purpose and return values. It mentions 'public website' and basic metadata, but could elaborate on default viewport or failure scenarios. Still sufficient for a screenshot tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter is already described in the schema. The description adds no additional parameter meaning, making the baseline score of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Capture a screenshot of any public website' with clear verb and resource, and explains what returns (image, URL, metadata). There are no sibling tools to differentiate, but the purpose is explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Use this whenever the user wants to see, save, or share what a web page looks like', giving clear context. No explicit when-not-to-use or alternatives, but no siblings exist.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.1
    • First observedtake_screenshot
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.1/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The purpose is singular and clear.

Naming Consistency5/5

A single tool named 'take_screenshot' is consistent with itself and uses a clear verb_noun pattern. No inconsistency exists.

Tool Count4/5

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.

Completeness3/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/faridmth/screenshotrender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server