docs-to-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIRECRAWL_API_KEY | No | The API key for Firecrawl. Required when using hosted Firecrawl. | |
| FIRECRAWL_API_URL | No | The URL of the Firecrawl API. Defaults to http://localhost:3002 for self-hosted. Set to https://api.firecrawl.dev for hosted. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsC | Search the captured docs and return ranked matching pages. |
| get_docA | Return one captured page: metadata, source URL, and full markdown. |
| list_docsB | List captured pages, optionally filtered to one section or category. |
| refresh_docsC | Re-crawl the source site and rebuild the local corpus and index. |
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 4 tools
Each tool has a distinct purpose: searching, retrieving full content, listing, and refreshing the corpus. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (search_docs, get_doc, list_docs, refresh_docs).
4 tools is a compact but sufficient set for documentation management, covering core operations without excess.
The set covers search, retrieval, listing, and corpus refresh. Missing delete/update of individual docs, but these are less critical for a read-oriented MCP server.