shantycrawl-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_URL | No | Your Firecrawl API base URL | http://localhost:3002 |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrapeC | Extract markdown from a URL |
| crawlB | Crawl a website for page content |
| searchC | Search the web |
| check_crawl_statusC | Check crawl job progress |
| tool_enableB | Activate an advanced tool for this session. Use without arguments to list available tools. |
| tool_disableA | Deactivate an advanced tool for this session. Use without arguments to list currently active tools. See tool_enable for the full list of available tools. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| shantycrawl-setup | How to use shantycrawl-mcp lazy-loading tools |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear distinct purpose: crawl for site crawling, scrape for single URL extraction, search for web search, check_crawl_status for monitoring, and tool_enable/disable for session management. No significant overlap.
Naming is mixed: some tools are single verbs (crawl, scrape, search), one uses verb_noun with underscore (check_crawl_status), and two use a 'tool_' prefix (tool_enable, tool_disable). This inconsistency could confuse an agent.
With 6 tools, the server is well-scoped for a focused crawler/scraper. Every tool serves a necessary function, and the count is neither excessive nor too thin.
Basic crawling, scraping, and search are covered, but missing operations like cancel crawl or list jobs limit the surface. The meta-tools don't address domain gaps.