Skip to main content
Glama
xufei547

Renderly MCP

by xufei547
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Renderly MCP

Clean web screenshots & content for AI agents. An MCP server that gives your AI agent two tools:

  • screenshot — capture a clean PNG/JPEG of any web page. Cookie banners, ads, and chat widgets are auto-removed, so the image is clean for vision models.

  • extract — get the clean main article content (Markdown / text / HTML) of a page, boilerplate stripped — ideal for LLMs / RAG.

Real Chromium rendering, so JavaScript-built pages work. Powered by Renderly.

Setup

  1. Get a RapidAPI key — subscribe to Renderly (free tier available):

    Both share one RapidAPI key (your X-RapidAPI-Key).

  2. Add the server to your MCP client.

Claude Desktop / Cursor

Add to your MCP config (claude_desktop_config.json or Cursor's mcp.json):

{
  "mcpServers": {
    "renderly": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/xufei547/renderly-mcp", "renderly-mcp"],
      "env": { "RAPIDAPI_KEY": "your-rapidapi-key" }
    }
  }
}

(uvx ships with uv — it installs and runs the server straight from GitHub, no extra steps. Prefer pip? pip install git+https://github.com/xufei547/renderly-mcp then use "command": "renderly-mcp".)

Related MCP server: cleanfetch

Tools

Tool

Args

Returns

screenshot

url, full_page, block_cookie_banners, format (png/jpeg), width, height

image

extract

url, format (markdown/text/html), include_tables

clean content

Example prompts

  • "Screenshot https://example.com and describe what's on the page."

  • "Extract the article at and summarize it."

Configuration (env vars)

Var

Default

Purpose

RAPIDAPI_KEY

—

Required. Your RapidAPI key.

RENDERLY_SCREENSHOT_HOST

screenshot-pdf-api2.p.rapidapi.com

Screenshot API host (see your RapidAPI "Code Snippets").

RENDERLY_EXTRACT_HOST

article-extraction-api.p.rapidapi.com

Extraction API host.

RENDERLY_TIMEOUT

90

Request timeout (seconds).

License

MIT

Available Tools

2 tools
extractA

Extract the clean main content of a web page for LLMs / RAG.

Renders the page with real Chromium (so JavaScript-built pages work), then strips ads, navigation, and boilerplate. Returns clean Markdown, text, or HTML.

Args: url: Page URL to extract (http/https). format: "markdown", "text", or "html". include_tables: Keep tables in the extracted content.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
formatNomarkdown
include_tablesNo

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A4.8/5.0
Behavior5/5

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

Discloses key behavioral traits: uses real Chromium for rendering, strips ads/navigation/boilerplate, returns clean formats. No annotations provided, so description carries full burden and does so effectively.

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?

Front-loaded purpose, followed by concise behavioral explanation, then a clear parameter list. Every sentence adds value; no wasted words.

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

Completeness5/5

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

Given the presence of an output schema, the description covers purpose, behavior, and parameters adequately. No missing critical details for the tool's simple domain.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining each parameter: url (http/https), format (markdown/text/html with default), and include_tables (boolean, default true). Adds meaning beyond schema titles.

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 clearly states the tool extracts clean main content of web pages for LLMs/RAG, with a specific verb and resource. It distinguishes from the sibling tool 'screenshot' which captures visual output.

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?

Explains when to use (for getting text content, especially from JS-heavy pages) but does not explicitly mention when not to use. The context with sibling 'screenshot' provides implicit guidance.

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

screenshotA

Capture a clean screenshot of a web page for AI/vision use.

Cookie/consent banners, ads, and chat widgets are removed by default so the image is clean for vision models. Returns the rendered image.

Args: url: Page URL to capture (http/https). full_page: Capture the entire scrollable page, not just the viewport. block_cookie_banners: Auto-hide cookie banners, ads, and chat widgets. format: "png" or "jpeg". width: Viewport width in pixels. height: Viewport height in pixels.

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
widthNo
formatNopng
heightNo
full_pageNo
block_cookie_bannersNo

TDQS

A4.6/5.0
Behavior4/5

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

Discloses key behaviors: removes banners/ads by default, returns rendered image, and explains all parameters. No annotations provided, so description carries full burden. Lacks mention of rate limits or auth, but fine for screenshot.

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?

Concise description with purpose statement, behavioral note, and structured argument list. No redundant information.

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

Completeness5/5

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

Covers all aspects: purpose, default behaviors, parameter details, and return type. No output schema, but description adequately describes output. No missing context for this tool.

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

Parameters5/5

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

All 6 parameters explained with defaults and usage context. Adds meaning beyond schema (e.g., 'Capture entire scrollable page'). Schema coverage 0% but description compensates fully.

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?

Description clearly states verb 'capture', resource 'screenshot of a web page', and purpose 'for AI/vision use'. It distinguishes from sibling 'extract' by specifying it returns an image.

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?

Implied usage for visual capture vs data extraction. Notes that cookie banners, ads, etc. are removed by default, helping agents understand when to use. Lacks explicit alternatives or exclusions.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.5/5.0
Disambiguation5/5

Both tools target web pages but have clearly distinct purposes: 'extract' retrieves text content for LLMs, while 'screenshot' captures visual images for vision models. No overlap in functionality.

Naming Consistency4/5

Tool names are single-word verbs ('extract', 'screenshot'), which is consistent and descriptive, though lacking a verb_noun pattern that could clarify the object (e.g., 'extract_page_content').

Tool Count3/5

Two tools is minimal for a web page utility server. While they cover the core promise of content extraction and screenshots, additional tools for batch processing or download would strengthen the set.

Completeness4/5

The server offers both text and visual extraction for web pages, covering its stated purpose. Minor gaps exist, such as lacking batch processing or file-saving options, but agents can accomplish most tasks.

Maintenance

ActivityStale
ResponsivenessSyncing

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/xufei547/renderly-mcp'

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