FetchV2 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 |
|---|---|
| fetchA | Fetch a single webpage and extract its main content as clean markdown. USE THIS TOOL WHEN:
DO NOT USE WHEN:
PAGINATION: Large pages are automatically truncated. The response will include 'use start_index=N to continue' - call again with that value to get more content. EXAMPLES:
|
| fetch_batchA | Fetch multiple webpages in a single request and return combined content. USE THIS TOOL WHEN:
KEY BENEFIT: One tool call instead of multiple fetch() calls = fewer round trips, faster results, and reduced overhead in supervised/approval workflows. WORKFLOW EXAMPLE:
NOTES:
|
| discover_linksA | Discover all links on a webpage. Use this BEFORE fetch_batch to find relevant URLs. USE THIS TOOL WHEN:
RECOMMENDED WORKFLOW:
FILTER EXAMPLES:
NOTES:
|
| fetch_llms_txtA | Fetch and parse an llms.txt file to discover LLM-friendly documentation. USE THIS TOOL WHEN:
WHAT IS llms.txt: A proposal for sites to provide LLM-friendly content at /llms.txt. It's a markdown file listing documentation links with descriptions. See https://llmstxt.org for the specification. WORKFLOW:
EXAMPLES:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| fetch_manual | Fetch a URL manually (user-initiated, bypasses robots.txt check). |
| research_topic | Research a topic by fetching multiple relevant URLs. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct retrieval mode: discover_links maps a site, fetch retrieves one URL, fetch_batch retrieves multiple URLs, and fetch_llms_txt parses the llms.txt format. Descriptions explicitly clarify when to use fetch vs fetch_batch, so an agent should not misselect.
All tool names use a lowercase verb-first style: fetch, fetch_batch, fetch_llms_txt, discover_links. The only minor inconsistency is that plain 'fetch' lacks the object/scope qualifier the other names have, but the overall pattern remains predictable.
Four tools is well-scoped for a web fetching and content discovery server. Each tool fills a distinct role—single fetch, batch fetch, link discovery, and llms.txt support—without unnecessary bloat or redundancy.
The server covers the core workflow end-to-end: discover relevant links, then fetch them individually or in batches. Minor gaps exist, such as no dedicated search or robots.txt checking tool, but these do not create dead ends for the stated purpose.