scrapy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRAPY_MCP_JOB_DIR | No | Where crawl jobs are stored. | <tmp>/scrapy_mcp_jobs |
| SCRAPY_MCP_LOG_LEVEL | No | Scrapy log level (to stderr). | ERROR |
| SCRAPY_MCP_MAX_BYTES | No | Max characters returned per page (then truncated). | 50000 |
| SCRAPY_MCP_USER_AGENT | No | User-Agent header. | scrapy-mcp/<version> … |
| SCRAPY_MCP_OBEY_ROBOTS | No | Obey robots.txt. | true |
| SCRAPY_MCP_RETRY_TIMES | No | Retries on transient failures. | 2 |
| SCRAPY_MCP_AUTOTHROTTLE | No | Adapt delay to server latency. | true |
| SCRAPY_MCP_JOB_TTL_DAYS | No | Delete crawl jobs older than this (0 disables). | 7 |
| SCRAPY_MCP_MAX_DEPTH_CAP | No | Hard cap for depth. | 10 |
| SCRAPY_MCP_MAX_PAGES_CAP | No | Hard cap for pages. | 1000 |
| SCRAPY_MCP_DOWNLOAD_DELAY | No | Seconds between requests to a host. | 0.5 |
| SCRAPY_MCP_REQUEST_TIMEOUT | No | Wall-clock cap for a blocking single fetch (s). | 60 |
| SCRAPY_MCP_DOWNLOAD_TIMEOUT | No | Per-request timeout (s). | 30 |
| SCRAPY_MCP_DEFAULT_MAX_DEPTH | No | Crawl depth default. | 2 |
| SCRAPY_MCP_DEFAULT_MAX_PAGES | No | Crawl page default. | 50 |
| SCRAPY_MCP_CONCURRENT_REQUESTS | No | Global concurrency. | 8 |
| SCRAPY_MCP_CONCURRENT_REQUESTS_PER_DOMAIN | No | Per-host concurrency. | 4 |
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 |
|---|---|
| fetch_pageA | Fetch a single web page and return its content (no JavaScript rendering).
An HTTP error status (404, 500, ...) is returned in |
| extractA | Fetch a page and pull structured fields out of it with CSS or XPath selectors.
Example: {"title": "h1::text", "prices": {"css": ".price::text", "all": true}} Returns {"data": {field: value | [values]}}. |
| extract_tablesA | Fetch a page and extract every HTML as {headers, rows}.
|
| extract_linksA | Fetch a page and return its links (de-duplicated, absolute URLs).
|
| get_sitemapA | Fetch a sitemap and return the URLs it lists. Handles gzip-compressed sitemaps and recurses one level of into its
child sitemaps. |
| check_robotsA | Check the site's robots.txt: is
|
| start_crawlA | Start a bounded breadth-first crawl. Returns a job_id immediately (non-blocking). The crawl follows in-scope links from
Poll progress with |
| crawl_statusA | Report a crawl's state and progress.
|
| crawl_resultsA | Page through a crawl's scraped items.
|
| cancel_crawlA | Stop a running crawl by killing its worker process. Results so far are kept. |
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 10 tools
Each tool has a clearly distinct purpose: fetching a page, extracting tables, links, structured data, checking sitemap/robots, and managing crawls. There is no overlap between single-page extraction tools and crawl lifecycle tools.
Tool names consistently follow a verb_noun pattern: extract_tables, extract_links, fetch_page, get_sitemap, check_robots, start_crawl, crawl_status, etc. The generic 'extract' is slightly less patterned but still readable and predictable.
With 10 tools, the server is well-scoped for its purpose. The set balances single-page extraction utilities with essential crawl management operations without unnecessary bloat.
The domain of web scraping and crawling is well covered: page fetching, link/table/structured extraction, robots and sitemap handling, plus full crawl lifecycle (start, status, results, cancel). Minor gap is lack of a tool to list all crawls, but core workflows are complete.