Distill MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Your RapidAPI key for the Distill API. | |
| API_MARKET_KEY | No | Your api.market key, used when RAPIDAPI_KEY is not set. | |
| HFL_MARKETPLACE | No | Set to 'rapidapi' or 'apimarket' when both keys are set, to choose which marketplace to use. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Fetch a web page and get its main content as clean Markdown, without navigation, ads or scripts. Distill honours robots.txt and AI opt-outs: when a result says the site refused, don't try to get the page another way. Each call is one request on the user's Distill plan.
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_markdownA | Fetch a web page and return its main content as Markdown, with title, author, date and language.
|
| html_to_markdownA | Turn HTML you already have into clean Markdown (main content only). A |
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 are clearly separated by input source: fetch_markdown takes a URL and retrieves content, while html_to_markdown takes HTML the caller already has. There is mild conceptual overlap since fetching implicitly converts HTML, but the descriptions make the boundary clear enough to choose correctly.
Both names follow the same snake_case verb_object pattern (fetch_markdown, html_to_markdown) and use the shared 'markdown' noun, making the pair predictable and readable.
Two tools is on the thin side for a server, though the scope (fetch and convert to Markdown) is genuinely narrow. It is borderline rather than mismatched, since each tool earns its place.
The core lifecycle of getting Markdown from either a URL or raw HTML is covered, with status codes explaining failure modes. Minor gaps exist, such as batch fetching or metadata-only extraction, but agents can work around them.