Skip to main content
Glama
AustinAbhari

mcp-wiki-server

by AustinAbhari

Related Servers

Alternatives to mcp-wiki-server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables any compatible MCP client or AI agent to retrieve documentation from a local directory of Markdown, HTML, or TXT files via a remote, read-only MCP server.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides direct access to local documentation files through simple search and overview tools, enabling LLMs to query project-specific markdown documentation without requiring vector databases or RAG pipelines.
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to discover, read, search, and install Markdown-based knowledge (rules, skills, workflows) from a local directory via MCP tools.
      12
      37 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve clearly distinct purposes: search_docs finds documents by keyword, while read_doc retrieves the full content of a known document by path. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    Both tools use a verb_noun pattern (search_docs, read_doc), making the pattern predictable. There is a minor inconsistency in pluralization—search_docs is plural while read_doc is singular—but it does not cause confusion.

    Tool Count3/5

    With only two tools, the server feels minimally scoped. This is appropriate for a simple read-only wiki, but it is on the thin side and offers no additional utility beyond search and read.

    Completeness4/5

    For a read-only documentation server, the search-and-read lifecycle is complete. The only notable gap is the lack of a way to list or browse all documents without a search query, which could be a minor workaround in some cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues