crw-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRW_CONFIG | No | Path to a custom configuration file (e.g., myconfig.toml). | |
| CRW_API_KEY | No | Your API key for authentication with the CRW API server (required for cloud mode). | |
| CRW_API_URL | No | The URL of the CRW API server (e.g., https://fastcrw.com/api). When set, enables cloud mode with web search capabilities. | |
| CRW_SERVER__PORT | No | The port on which the CRW server should run (default is 3000). | |
| CRW_EXTRACTION__LLM__API_KEY | No | API key for the LLM provider (e.g., Anthropic or OpenAI) used for structured extraction. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crw_scrapeA | Scrape one URL to markdown, HTML, or links. |
| crw_crawlA | Start an async site crawl; returns a job id to poll with crw_check_crawl_status. |
| crw_check_crawl_statusA | Poll an async crawl job and retrieve its pages. |
| crw_mapA | Discover URLs on a site via sitemap and/or a short crawl. Returns a URL list only, no page content. |
| crw_extractA | Extract structured JSON from URLs via a prompt and/or JSON schema. Async job — poll crw_check_extract_status with the returned id. Needs an LLM. |
| crw_check_extract_statusA | Poll an extract job; returns status and, when complete, a per-URL results array. |
| crw_cancel_extractA | Request cancellation of an extract job. Returns the canonical status; cancelling remains non-terminal until the claimed URL settles. |
| crw_parse_fileA | Parse a local PDF (base64 in contentBase64) to markdown. No OCR: scanned PDFs return empty markdown with a warning. |
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 8 tools
Each tool targets a distinct operation: single-page scraping, full-site crawling, URL discovery, structured extraction, PDF parsing, and async job control. Status/cancel tools are clearly paired with their respective job types, so an agent can reliably select the right tool.
All tool names share the crw_ prefix and use a consistent lowercase snake_case style. Action verbs (crawl, scrape, extract, map, parse, check, cancel) are used predictably, making the API easy to navigate.
Eight tools is well-scoped for a crawling/extraction server. Each tool covers a distinct part of the workflow without redundancy or unnecessary surface area.
The core workflows are covered: crawling, scraping, extracting, mapping, parsing PDFs, and polling async jobs. The main gap is the lack of a cancel operation for crawl jobs, since extraction jobs have crw_cancel_extract but crawls have no equivalent.