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
The tools are mostly distinct, with each handling a different content type (HTML, JSON, Markdown, plain text). However, fetch_html and fetch_txt could be slightly confusing as both fetch websites, but their output formats (HTML vs. plain text) clarify the distinction. There is no significant overlap in purpose.
All tool names follow a consistent verb_noun pattern with 'fetch_' prefix and descriptive suffixes (html, json, markdown, txt). The naming is predictable and uniform, making it easy to understand the tool set at a glance.
With 4 tools, the count is reasonable for a fetch server focused on retrieving different content types. It is slightly lean but covers core use cases well. A few additional tools (e.g., for handling errors or metadata) might enhance it, but it's not incomplete.
The server covers fetching various content types, which aligns with its purpose. However, there are notable gaps: no tools for handling HTTP methods beyond GET (e.g., POST), error handling, or configuration (e.g., headers, timeouts). This limits advanced use cases but suffices for basic retrieval.