Scrapfly MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPFLY_API_KEY | No | Your Scrapfly API key for authentication. Can be obtained from https://scrapfly.io/dashboard |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| info_accountA | Get subscription, usage, limits. Use for quotas/billing/concurrency. Avoid for content scraping. |
| info_api_keyA | Return the Users' ScrapFly API key |
| scraping_instruction_enhancedC | Return critical instructions for scraping tools |
| screenshotB | Screenshot a URL. |
| web_get_pageA | Quick page fetch with sane defaults. Use tool scraping_instruction_enhanced before using this tool. Use when you just need the content fast. |
| web_scrapeA | Scrape a URL with full control. Use tool scraping_instruction_enhanced before using this tool. Prefer web_get_page for quick fetch |
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 6 tools
Most tools have distinct purposes, but web_get_page and web_scrape overlap in fetching web content, which could cause confusion despite descriptions suggesting different use cases (quick fetch vs. full control). The info_account and info_api_key tools are clearly separate for account management versus API key retrieval.
Naming is mixed with snake_case used throughout, but patterns vary: some start with 'info_' (info_account, info_api_key), others with 'web_' (web_get_page, web_scrape), and one with 'scraping_' (scraping_instruction_enhanced). This inconsistency makes the set less predictable, though it remains readable.
With 6 tools, the count is well-scoped for a scraping server, covering account info, instructions, screenshot, and web fetching. Each tool appears to serve a specific function without being overly sparse or bloated, fitting the domain appropriately.
The toolset covers key scraping needs: account management, instructions, screenshot, and web fetching with both quick and full-control options. A minor gap exists in lacking explicit tools for post-processing scraped data or handling errors, but core workflows are adequately supported.