Fetch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| smart_fetchA | Fetch any URL and auto-optimize based on content type. For HTML: converts to clean markdown, stripping navigation, ads, and scripts. For JSON: returns a schema + sample by default for large arrays. Use the jsonpath parameter to drill into specific items or fields on follow-up calls. Dramatically reduces token usage compared to raw fetching. |
| web_searchA | Search the web using DuckDuckGo and return results as a markdown list. |
| css_queryA | Fetch a page and return only the content matching a CSS selector. |
| browser_fetchA | Fetch a JavaScript-rendered page with Playwright and return markdown. |
| pdf_fetchA | Fetch a PDF URL and return its text content as markdown. Falls back to HTML markdown if the URL does not return a PDF. |
| optimize_jsonA | Optimize any JSON payload to reduce token usage. |
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 6 tools
Each tool has a clear primary purpose (fetch, search, CSS extraction, JS rendering, PDF, JSON optimization), but smart_fetch overlaps somewhat with the specialized fetch tools, requiring attention to descriptions to pick the right one.
Most tools follow an object_action pattern (web_search, css_query, browser_fetch, pdf_fetch), but smart_fetch and optimize_json deviate by putting the action first, resulting in mixed conventions.
Six tools is well-scoped for a fetch server, covering general fetching, specialized fetch modes, search, and JSON optimization without redundancy.
The server covers major fetch types (HTML, PDF, JS-rendered) and adds search and JSON optimization. A minor gap is the lack of a raw HTML fetch without transformation, but smart_fetch and css_query nearly fill this need.