Skip to main content
Glama
ma-nakaya

GitHub Pages Retrieval MCP

by ma-nakaya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GitHub Pages Retrieval MCP

No user-submitted related servers found.

    Related Servers

    • Crawl4AI+SearXNG MCP Server

      alexesom
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to search the web, crawl websites, and perform intelligent RAG queries with semantic search capabilities. Includes integrated private search engine, vector database storage, and optional knowledge graph for AI hallucination detection in code repositories.
      1
      MIT

    • OmniDocs RAG

      ElvinBayramov
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to index and search local files, websites, GitHub repos, and packages using hybrid retrieval with reranking, all through IDE chat.
      4
      Apache 2.0

    • OmniDocs-RAG-CN

      ybhuang995-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to index and search local files, websites, GitHub repos, and packages with hybrid AI-powered retrieval, all locally through IDE chat.
      Apache 2.0

    • search-docs

      otolab
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search local Markdown documents using natural language, with automatic indexing and section-level retrieval.
      10
      5 npm
      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

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists between fetch_pages_content and fetch_indexed_section (both retrieve content, one live and one cached), and the three auth-related tools (begin_source_reauth, validate_source_auth, get_source_auth_status) represent sequential steps that could be confused. Descriptions are clear enough to resolve most ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., begin_source_reauth, fetch_pages_content, list_pages_sources). No casing or naming style deviations are present.

    Tool Count5/5

    The 10 tools are well-scoped for the server's purpose of retrieving and indexing GitHub Pages content. Each tool covers a distinct step in the configuration, authentication, fetching, and search workflow without unnecessary bloat.

    Completeness4/5

    The tool surface covers the core lifecycle: configure, list, authenticate, fetch live content, build and query an index, and retrieve indexed sections. Minor gaps exist, such as no tool to delete or update a configured source, but these do not significantly hinder the primary use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources