Skip to main content
Glama
wolfyy970

Docs Fetch MCP Server

by wolfyy970
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Docs Fetch MCP Server

No user-submitted related servers found.

    Related Servers

    • llms-txt

      ux-xd
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to discover the llms.txt index covering any site, fetch its linked documentation pages as markdown, and search across parsed indexes by section heading, link title, and notes.
      MIT

    • Fetch MCP Server

      MaartenSmeets
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to fetch and extract web content using browser automation, OCR, and multiple extraction methods, handling JavaScript rendering and anti-scraping techniques.
      17
      MIT

    • Spider MCP Server

      oeo
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables crawling and extracting clean content from documentation websites with optional LLM-powered analysis for intelligent summaries, code example extraction, and content classification.
      -

    • Crawl4AI RAG MCP Server

      Chillbruhhh
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents and coding assistants with advanced web crawling and RAG capabilities, allowing them to scrape websites and leverage that knowledge through various retrieval strategies.
      2
      MIT

    • Fetch MCP Server

      aglolz
      A
      license
      B
      quality
      D
      maintenance
      Enables LLMs to retrieve and process web content by fetching URLs and converting HTML to markdown format. Supports chunked reading of large pages and can access both public websites and local networks.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'fetch_doc_content' has a clear and distinct purpose, making it impossible for an agent to confuse it with other tools.

    Naming Consistency5/5

    Since there is only one tool, it inherently follows a consistent naming pattern. The tool name 'fetch_doc_content' uses a verb_noun structure, which is clear and predictable, and there are no other tools to cause inconsistency.

    Tool Count2/5

    A single tool is too few for a server named 'Docs Fetch MCP Server', which implies a domain involving document fetching and exploration. While the tool is well-described, one tool feels thin and insufficient for comprehensive operations like managing fetched content or handling different document types, limiting the server's utility.

    Completeness2/5

    The tool surface is severely incomplete for the inferred domain of document fetching. It only provides a fetch operation with depth control, missing essential functions such as listing fetched documents, updating or deleting cached content, searching within documents, or handling errors, which are necessary for a complete workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources