crawl4ai-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| scrape_webpageC | Scrape content and metadata from a single webpage using Crawl4AI. Args: url: The URL of the webpage to scrape Returns: List containing TextContent with the result as JSON. |
| crawl_websiteB | Crawl a website starting from the given URL up to a specified depth and page limit. Args: url: The starting URL to crawl. crawl_depth: The maximum depth to crawl relative to the starting URL (default: 1). max_pages: The maximum number of pages to scrape during the crawl (default: 5). Returns: List containing TextContent with a JSON array of results for crawled pages. |
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 2 tools
The two tools have clearly distinct purposes: crawl_website handles multi-page crawling with depth and page limits, while scrape_webpage focuses on single-page extraction. There is no overlap in functionality, making it easy for an agent to choose the right tool based on whether it needs to crawl multiple pages or scrape just one.
Both tools follow a consistent verb_noun pattern (crawl_website and scrape_webpage), using snake_case and descriptive action-object naming. This consistency makes the tool set predictable and easy to understand at a glance.
With only 2 tools, the server feels too thin for a web crawling/scraping domain. While the tools cover basic crawling and scraping, typical MCP servers in this domain would include additional utilities like filtering, parsing, or handling different content types, making this set appear incomplete and limited in scope.
The tool set is severely incomplete for web crawling and scraping. It lacks essential operations such as updating crawl parameters, deleting or managing crawl jobs, handling errors or retries, and processing extracted data (e.g., cleaning, summarizing). This forces agents into dead ends for common workflows beyond basic one-off tasks.