Skip to main content
Glama
COOLFEATHER

LLM Wiki MCP Server

by COOLFEATHER

Related Servers

Alternatives to LLM Wiki MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Local-first personal wiki and memory server for AI agents. MCP clients can capture knowledge, retrieve context, read and maintain source-backed wiki pages, and carry project context between sessions.
      33
      92
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      A local MCP server that lets AI hosts like Claude Desktop, Cursor, or Cline query a hybrid vector + BM25 index of your scattered notes, project docs, PDFs, and chat exports, returning answers with section-level citations. It exposes eight tools, resources, and prompts so agents can search, ask, and walk links across all your source directories at once.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for persistent, compounding markdown wikis maintained by LLMs. Enables incremental knowledge base building with interlinked pages, search, and raw source management.
      27 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Local-first MCP server for retrieval over markdown wikilink vaults, offering hybrid vector+lexical search, note reading, neighbor expansion, and recent activity tracking with fully local embeddings and no network egress.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Exposes a local hybrid (vector + BM25) index of scattered notes, docs, PDFs, and chat logs to AI hosts like Claude Desktop, Cursor, and Cline, letting agents search and get cited answers. It publishes a set of tools, resources, and prompts so any MCP-compatible client can query that knowledge base with section-level citations.
      -

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct operation: query for retrieval, write_wiki for creating pages, read_wiki for reading pages, rebuild_index for indexing maintenance, and ingest for processing raw material into wiki pages. There is minimal overlap, and descriptions clarify any potential confusion.

    Naming Consistency3/5

    The naming pattern is mixed: two tools use verb_noun style (write_wiki, read_wiki), one uses verb_noun but for a different object (rebuild_index), while two tools are single-word verbs (query, ingest). This inconsistency makes the set less predictable, though still readable.

    Tool Count5/5

    With 5 tools, the set is well-scoped for a wiki server, covering creation, reading, searching, indexing, and ingestion. It is neither too thin nor too heavy, and each tool serves a clear purpose.

    Completeness3/5

    The set covers create, read, query, index rebuild, and ingestion, but notably lacks update and delete operations for wiki pages. This creates a gap in the typical CRUD lifecycle, which agents may need to work around.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues