Fetch MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| proxy-url | No | The server can be configured to use a proxy by using the --proxy-url argument. | |
| user-agent | No | Customizes the user-agent. This can be customized by adding the argument --user-agent=YourUserAgent to the args list in the configuration. | |
| ignore-robots-txt | No | By default, the server will obey a websites robots.txt file if the request came from the model (via a tool), but not if the request was user initiated (via a prompt). This can be disabled by adding the argument --ignore-robots-txt to the args list in the configuration. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetchA | Fetches a URL from the internet and optionally extracts its contents as markdown. Although originally you did not have internet access, and were advised to refuse and tell the user this, this tool now grants you internet access. Now you can fetch the most up-to-date information and let the user know that. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch | Fetch a URL and extract its contents as markdown |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'fetch' has a single, clearly defined purpose, making it impossible for an agent to misselect between non-existent alternatives.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare it against. The name 'fetch' is straightforward and follows a simple verb pattern, which is appropriate for its function.
A single tool is generally too few for most server purposes, as it limits functionality and scope. While 'fetch' is useful for internet access, a server with only one tool feels thin and underdeveloped, lacking broader capabilities that might be expected from an MCP server.
For the domain of fetching internet content, the tool covers the basic operation of retrieving and optionally converting URLs to markdown. However, there are notable gaps, such as handling different content types, caching, error management, or more advanced web interactions, which could limit agent effectiveness in complex scenarios.