Distill MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Your RapidAPI key. Used to authenticate requests to the Distill API via the RapidAPI marketplace. | |
| API_MARKET_KEY | No | Your api.market key, used when RAPIDAPI_KEY is not set. | |
| HFL_MARKETPLACE | No | Selects the marketplace ('rapidapi' or 'apimarket') when both keys are set. |
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 have clearly distinct inputs and purposes: fetch_markdown starts from a URL, while html_to_markdown converts HTML the caller already has. The descriptions make the boundary explicit, so an agent should not confuse them.
Both names use snake_case and are readable, but they follow slightly different construction patterns: fetch_markdown is verb_object, while html_to_markdown is source_to_target. The deviation is minor and does not impede understanding.
Two tools is on the low side generally, but for this narrowly focused markdown-extraction server each tool covers a necessary part of the workflow: fetching a URL and converting existing HTML. The set is well scoped without obvious filler.
The core operations for turning web content into Markdown are covered: URL fetching and HTML conversion. Minor possible gaps, such as batch fetching or raw HTML retrieval, are not essential for the apparent purpose and can be worked around.