Skip to main content
Glama
Sign In
llm-wiki-mcp

llm-wiki-mcp

by kleinmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to llm-wiki-mcp

No user-submitted related servers found.

    Related Servers

    • ai-wiki-mcp

      jhonnold
      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
      -

    • wikicapsule

      pisigmac
      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

    • kb-server

      philippe-ths
      A
      license
      A
      quality
      C
      maintenance
      Serves a local Obsidian markdown vault over MCP, enabling agents to search, read, build context, verify, and safely propose or apply guarded changes to the knowledge base.
      12
      MIT

    • kaas

      MartaWisniewski
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable coding agents to query a compiled Markdown wiki through a single ask tool, returning cited answers grounded in the wiki over stdio or streamable HTTP.
      -

    • KaaS

      dTsipras7651
      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.
      -
    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.3/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a distinct purpose. get_index provides an overview, search_wiki and find_page are explicitly differentiated for full-text search vs. single-page retrieval, and read_page, list_pages, list_types, list_tags, get_log, read_source, validate_wiki, and ask each serve unique functions without overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_index, search_wiki, find_page, read_page, list_pages, list_types, list_tags, get_log, read_source, validate_wiki). The only minor deviation is 'ask', but it is still a single verb and fits the pattern of action-oriented names.

    Tool Count5/5

    With 11 tools, the set is well-scoped. Each tool covers a specific aspect of wiki interaction (index, search, retrieval, listing, logging, raw source access, validation, Q&A) without being excessive or sparse.

    Completeness5/5

    The tool set is complete for a read-only wiki interface. It provides everything needed to navigate, search, retrieve, validate, and query a wiki corpus. While write tools are absent, the domain inferred from the tool descriptions is clearly read-only, so no gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources