AIMLPM/markcrawl
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XAI_API_KEY | No | API key for xAI/Grok (required for extraction tool with --provider grok) | |
| GEMINI_API_KEY | No | API key for Google Gemini (required for extraction tool with --provider gemini) | |
| OPENAI_API_KEY | No | API key for OpenAI (required for extraction tool with --provider openai and Supabase upload) | |
| ANTHROPIC_API_KEY | No | API key for Anthropic/Claude (required for extraction tool with --provider anthropic) |
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 |
|---|---|
| crawl_siteA | Crawl a website and save extracted content as clean Markdown or plain text. |
| search_pagesA | Search through previously crawled pages by keyword. |
| read_pageA | Read the full extracted content of a specific crawled page by its URL. |
| list_pagesA | List all pages from a previous crawl with their URLs, titles, and word counts. |
| extract_dataA | Extract structured fields from crawled pages using an LLM. |
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 5 tools
Each tool has a clearly distinct role in the crawl pipeline: crawl_site fetches content, list_pages provides an overview, search_pages filters by keyword, read_page returns full content, and extract_data produces structured fields. There is no overlap or ambiguity between the tools.
All tool names follow the same verb_noun snake_case pattern: crawl_site, list_pages, search_pages, read_page, extract_data. The verbs are consistent and clearly describe the operation, and the nouns reflect the target object.
The server has 5 tools, which is well-scoped for its purpose. Each tool is necessary for the crawl, browse, and extract workflow, and there is no superfluous or redundant surface area.
The tool set covers the full lifecycle of crawling and working with web content: ingestion (crawl_site), discovery (list_pages, search_pages), retrieval (read_page), and structured analysis (extract_data). There are no obvious dead ends or missing operations for the stated domain.