Skip to main content
Glama

Related Servers

Alternatives to wiki-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Turns a git-backed markdown directory into an MCP-compatible knowledge server, enabling any MCP client to read, search, ingest, and maintain a persistent wiki that compounds across sessions.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides structured search, schema-validated writes, and linting for a markdown knowledge base, enabling agents to operate the wiki over a single streamable-HTTP MCP endpoint.
      1
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a compiled Markdown wiki to any MCP-capable coding agent through a single ask tool that returns cited answers grounded in whole articles rather than embedded fragments. It can run locally over stdio or be published remotely as a streamable-HTTP endpoint, optionally protected by a bearer token.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable coding agents to query a self-hosted, LLM-compiled Markdown wiki through a single ask tool, returning cited answers grounded in whole articles rather than embedded fragments. Served either locally over stdio or remotely over streamable HTTP with optional bearer-token auth.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a compiled Markdown knowledge wiki to any MCP-capable client through a single ask tool that returns cited Markdown answers grounded in whole wiki articles, available over stdio or an authenticated streamable-HTTP endpoint.
      -

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: orientation (read_orientation), discovery (search_wiki), and retrieval (get_page). There is no ambiguity about which tool to call for a given need, even though search_wiki and get_page both return page content, they serve different stages of a workflow.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case: read_orientation, search_wiki, get_page. The naming is predictable and aligns with the action each tool performs.

    Tool Count3/5

    With only 3 tools, the server is on the thin side but not extreme. It covers basic reading and searching operations, but for a wiki server one might expect additional tools like listing or writing, making the count feel slightly limited for the domain.

    Completeness2/5

    The tool surface lacks any write operations (create, update, delete) and does not provide a straightforward way to list all pages without parsing the index. This is a significant gap for a wiki, as agents cannot modify or manage content, only read and search.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues