zenrows-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENROWS_API_KEY | Yes | The ZenRows Universal Scraper API key required to authenticate requests. |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeA | Scrape any webpage and return its content using ZenRows. Use this tool to fetch webpage content for analysis. By default it returns clean markdown, which is ideal for LLM processing. When to enable options:
Examples: Basic: { url: "https://example.com" } Dynamic: { url: "https://spa.com", js_render: true } Protected:{ url: "https://protected.com", js_render: true, premium_proxy: true } Extract: { url: "https://shop.com", css_extractor: '{"title":"h1","price":".price"}' } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| scrape_and_summarize | Scrape a webpage and return a concise summary of its content. |
| extract_structured_data | Scrape a webpage and extract specific structured data using CSS selectors. |
| scrape_js_page | Scrape a page that requires JavaScript rendering (React, Vue, Angular, or any SPA). |
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 or overlap between tools. The single 'scrape' tool has a clear, distinct purpose of fetching webpage content.
There is only one tool name, so consistency is inherently perfect. The name 'scrape' follows a clear verb-based pattern appropriate for its function.
A single tool is too few for most server purposes, as it limits functionality and flexibility. While scraping is a focused domain, having only one tool feels thin and may not cover related needs like batch processing or error handling.
The tool covers basic webpage scraping with options for dynamic content and proxies, but there are notable gaps. Missing operations might include checking scrape status, managing sessions, or handling rate limits, which could lead to agent workarounds or failures in complex scenarios.