Skip to main content
Glama
praveenc

FetchV2 MCP Server

by praveenc

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fetchA

Fetch a single webpage and extract its main content as clean markdown.

USE THIS TOOL WHEN:

  • You need to read an article, documentation page, or blog post

  • You want clean, readable text without boilerplate (navbars, ads, footers)

  • The user provides a specific URL to read

DO NOT USE WHEN:

  • You need to fetch multiple URLs (use fetch_batch instead - fewer round trips)

  • You want to discover what pages exist on a site (use discover_links first)

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:

  • You have 2-10 URLs to read (e.g., from discover_links results)

  • Comparing content across multiple pages

  • Gathering context from several documentation pages at once

KEY BENEFIT: One tool call instead of multiple fetch() calls = fewer round trips, faster results, and reduced overhead in supervised/approval workflows.

WORKFLOW EXAMPLE:

  1. discover_links(url="https://docs.example.com", filter_pattern="/api/")

  2. fetch_batch(urls=[...returned links...], max_length_per_url=1500)

NOTES:

  • Each URL's content is separated by '---' dividers

  • Failed URLs show inline errors without stopping other fetches

  • Robots.txt is NOT checked for batch fetches (assumes prior discovery)

discover_linksA

Discover all links on a webpage. Use this BEFORE fetch_batch to find relevant URLs.

USE THIS TOOL WHEN:

  • Exploring a documentation site to find relevant pages

  • Building a list of URLs to fetch in batch

  • Finding all subpages under a section (e.g., all /api/ docs)

  • Checking what content exists before deciding what to read

RECOMMENDED WORKFLOW:

  1. discover_links(url="https://docs.example.com/", filter_pattern="/guide/")

  2. Review the returned links and select relevant ones

  3. fetch_batch(urls=[selected_urls], max_length_per_url=1500)

FILTER EXAMPLES:

  • filter_pattern="/docs/" → Only links containing '/docs/'

  • filter_pattern="getting-started|quickstart" → Links with either term

  • filter_pattern=".md$" → Only markdown file links

NOTES:

  • Returns up to 100 links (more are noted but omitted to save context)

  • Relative URLs are automatically resolved to absolute URLs

  • JavaScript/mailto/anchor links are excluded

fetch_llms_txtA

Fetch and parse an llms.txt file to discover LLM-friendly documentation.

USE THIS TOOL WHEN:

  • A site provides an llms.txt file for AI-friendly content discovery

  • You need to understand what documentation is available

  • You want to fetch structured docs in a single request

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:

  1. fetch_llms_txt(url="https://example.com/llms.txt") → Get structure

  2. Review sections and links

  3. Either use include_content=True or fetch_batch for specific pages

EXAMPLES:

Prompts

Interactive templates invoked by user choice

NameDescription
fetch_manualFetch a URL manually (user-initiated, bypasses robots.txt check).
research_topicResearch a topic by fetching multiple relevant URLs.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.6/5.0

Scored across 4 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues