Scrapedo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Set to DEBUG for debug logs, NONE to disable logging | INFO |
| SCRAPEDO_API_KEY | Yes | Your Scrapedo API key for authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeA | Basic web scraping without JavaScript rendering |
| scrape_with_jsC | Scrape JavaScript-rendered pages using headless browser |
| take_screenshotC | Capture webpage screenshots |
| scrape_to_markdownC | Scrape and convert to markdown format |
| get_usage_statsA | Get API usage statistics and remaining credits |
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 5 tools
The three scraping tools (scrape, scrape_with_js, scrape_to_markdown) overlap in core functionality, but their names clearly indicate use cases: basic, JS-rendered, and markdown output. Screenshot and usage stats are distinct. Minor ambiguity remains between scrape and scrape_to_markdown regarding whether the latter also handles JS rendering.
All tool names use snake_case and follow a verb-first pattern (e.g., take_screenshot, get_usage_stats). The bare verb 'scrape' slightly deviates from the verb_noun structure, but it remains readable and consistent with the overall style.
Five tools is well-suited for a scraping server, covering essential capabilities without unnecessary bloat. Each tool serves a distinct purpose, and the count is within the ideal 3-15 range.
The toolset covers the core scraping lifecycle: basic scraping, JS-rendered scraping, screenshots, markdown conversion, and usage tracking. Minor gaps like session/cookie handling exist, but they are not critical for standard scraping workflows and can be worked around.