Skip to main content
Glama

Related Servers

Alternatives to GPUI Kit MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Turns any documentation website into a standalone, dependency-free MCP server with local Chinese-first CJK search, enabling AI agents to read and search docs offline without API keys.
      5 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Local documentation search server for AI models using hybrid retrieval (phrase, keyword, vector). Provides MCP tools to search and fetch documentation from bundled or custom doc sets without any external API keys.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search locally indexed documentation entirely offline, resolving libraries and retrieving relevant Markdown fragments under a token budget through SQLite FTS5 full-text search. Docs never leave the machine, with no API keys or cloud dependencies.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to search an explicitly versioned local documentation corpus and retrieve fragments with source paths, sections, and commits. Exposes three tools — docs.search, docs.health, and docs.sources — over streamable HTTP or stdio, without synthesizing answers.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Indexes your project's markdown documentation and exposes it to AI agents via local hybrid search (lexical + semantic) with progressive disclosure tools.
      3
      89 npm
      5
      MIT

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation3/5

    get_doc is clearly distinct as the read tool, but search_docs, list_docs, and get_docs_index all return lists of documentation pages with paths and descriptions. The descriptions hint at differences (full-text search vs. keyword browse vs. llms.txt index), but an agent can easily pick the wrong one, especially list_docs vs. get_docs_index which both filter by language and section.

    Naming Consistency4/5

    All names are snake_case verb_noun (search_docs, get_doc, list_docs, get_docs_index), which is predictable. Minor deviation: get_doc uses a singular object while get_docs_index embeds a plural compound noun, so the pattern isn't perfectly uniform.

    Tool Count4/5

    Four tools is a sensible, well-scoped surface for a documentation server: one search, one read, and two browsing helpers. The only quibble is that the two listing tools partly overlap, so the set could arguably be three.

    Completeness4/5

    The core docs workflow is covered end to end: discover (search/list/index), then read a page with section-level granularity and path disambiguation. No obvious dead ends, though there is no tool for retrieving runnable examples or API signatures beyond what the Markdown pages contain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues