Spider Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug logging | false |
| SPIDER_API_KEY | Yes | Your Spider Cloud API key | |
| SPIDER_API_BASE_URL | No | API endpoint URL | https://api.spider.cloud |
| SPIDER_REQUEST_TIMEOUT | No | Request timeout in milliseconds | 60000 |
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 |
|---|---|
| spider_scrapeC | Scrape content from a single URL with advanced options for JavaScript rendering, anti-bot bypass, and content extraction |
| spider_crawlC | Crawl an entire website with configurable depth, limits, and filtering options |
| spider_searchC | Search the web with Google-like results and optional page content fetching |
| spider_linksC | Extract and analyze all links from a webpage with filtering options |
| spider_screenshotC | Capture high-quality screenshots of webpages with customizable viewport and options |
| spider_transformC | Transform HTML content to clean markdown, text, or formatted output |
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
Each tool targets a distinct web operation: scrape single URL, crawl site, search web, extract links, screenshot, and transform HTML. Overlap is minimal and descriptions clarify boundaries.
All tools use the same 'spider_' prefix followed by a clear verb/noun, creating a fully predictable naming pattern.
Six tools are well-scoped for a web scraping and content processing server, covering common workflows without bloat.
Core lifecycle is covered: discovery/search, extraction/scraping, crawling, link analysis, screenshots, and transformation. Minor gaps exist, such as batch operations or structured data extraction, but agents can work around them.