Renderly MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Required. Your RapidAPI key. | |
| RENDERLY_TIMEOUT | No | Request timeout (seconds). | 90 |
| RENDERLY_EXTRACT_HOST | No | Extraction API host. | article-extraction-api.p.rapidapi.com |
| RENDERLY_SCREENSHOT_HOST | No | Screenshot API host (see your RapidAPI 'Code Snippets'). | screenshot-pdf-api2.p.rapidapi.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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
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 2 tools
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.
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').
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.
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.