Skip to main content
Glama
pinkpixel-dev

LLMSTXT-MCP Server

by pinkpixel-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to LLMSTXT-MCP Server

No user-submitted related servers found.

    Related Servers

    • fetch-html-to-md

      kabeep
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that fetches remote or local HTML resources and converts them to Markdown, enabling AI clients to summarize or process web content.
      3 npm
      MIT

    • devdoc

      vision-release
      A
      license
      Not graded
      quality
      C
      maintenance
      A documentation MCP server that crawls websites and Git repositories, stores them as Markdown, and provides tools to search and retrieve documentation for local LLMs and AI agents.
      Apache 2.0

    • superFetch MCP Server

      j0hanz
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that fetches web pages and extracts clean, AI-friendly Markdown content using Mozilla Readability. It provides secure web access for LLMs with built-in SSRF protection and automated content cleaning for improved context retrieval and summarization.
      1
      107 npm
      MIT

    • MCP LLMS-TXT Documentation

      ankitrautela333
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables users to fetch and audit documentation from user-defined llms.txt index files. It provides tools to list documentation sources and retrieve content from specific URLs with built-in domain access controls for secure context retrieval.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.8/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve clearly distinct purposes: listing configured sources versus fetching a specific documentation URL. There is no overlap or ambiguity about when to use each.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern (list_doc_sources, fetch_docs) using snake_case. The naming is predictable and readable.

    Tool Count3/5

    With only two tools, the server feels minimal, though it may be appropriate for its narrow scope of listing sources and fetching docs. According to calibration, 1-2 tools is borderline thin, so this is not a strong score.

    Completeness4/5

    The tool surface covers the core workflow: list sources, fetch llms.txt or specific pages, and convert to markdown. A minor gap is the lack of a dedicated tool for managing sources (add/remove), but that appears to be configuration outside the server's purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources