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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_htmlC | Fetch a website and return the content as HTML |
| fetch_markdownC | Fetch a website and return the content as Markdown |
| fetch_txtA | Fetch a website, return the content as plain text (no HTML) |
| fetch_jsonC | Fetch a JSON file from a URL |
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 clearly distinct purpose: fetch_html returns HTML, fetch_json fetches JSON files, fetch_markdown converts to Markdown, and fetch_txt provides plain text. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'fetch_' as the prefix, followed by the content type (html, json, markdown, txt). This predictable naming scheme enhances readability and usability.
With 4 tools, the server is well-scoped for fetching different content types from URLs. Each tool earns its place by covering a specific format, avoiding bloat while providing comprehensive coverage for the domain.
The tool set offers complete coverage for fetching content in various formats (HTML, JSON, Markdown, plain text), with no obvious gaps. Agents can handle a wide range of fetching tasks without encountering dead ends.