Skip to main content
Glama
RuloGB

compendio-mcp

by RuloGB
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to compendio-mcp

No user-submitted related servers found.

    Related Servers

    • Markdown RAG Documentation

      andnp
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables semantic search over local Markdown documentation using hybrid retrieval combining embeddings, keyword search, and graph traversal with automatic file watching and zero-configuration setup.
      2
      MIT

    • docsGround

      youssefvdel
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to search, index, and manage documentation libraries with hybrid retrieval and live web fallback, all self-hosted and offline.
      1
      MIT

    • localgate

      omgamy1179-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables local AI agents to perform hybrid search (BM25 + vector) over privately indexed local files, including notes, PDFs, DOCX, source code, and OCR'd images. All indexing and retrieval stay on the machine with read-only, whitelist-scoped access.
      MIT
    • docs-mcp by apideck-libraries

      docs-mcpofficial

      apideck-libraries
      A
      license
      A
      quality
      C
      maintenance
      Lets AI agents search and read a folder of Markdown documentation at query time, exposing heading-level search, whole-page or section retrieval, and page listing as tools and resources over stdio or Streamable HTTP. Can run as a CLI, a hosted endpoint, or a library inside an existing Node or Next.js site.
      3
      121 npm
      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

    A4.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: search_docs for finding relevant content, docs_overview for enumerating the corpus, and read_doc for retrieving specific sections. The descriptions explicitly cross-reference when to use one over the other, leaving no real ambiguity.

    Naming Consistency4/5

    read_doc and search_docs follow a clear verb_noun pattern, while docs_overview is a noun-phrase exception. All names are lowercase snake_case, so the set is still readable and mostly predictable.

    Tool Count5/5

    Three tools is an ideal size for a documentation-corpus server: enumerate, search, and read cover the full exploration workflow without redundancy. Every tool earns its place.

    Completeness5/5

    The read-side lifecycle is fully covered: search to locate, overview to enumerate, and read to retrieve content. There are no obvious gaps for a read-only documentation server.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources