Skip to main content
Glama

Related Servers

Alternatives to wiki-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to search, read, and navigate a folder of Markdown notes as a knowledge base, with full-text search, backlinks, tags, metadata, and note resources for conversation attachment.
      1
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and query a local knowledge base of scattered notes and docs through hybrid vector plus BM25 retrieval with section-level citations, and to store, retract and explore durable memories, note links and agent harness memories. It also exposes note resources plus briefing, study-plan and contradiction-check prompts, all backed by a shared local index.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables a local second brain for capturing notes, searching with AI-driven relevance ranking, and discovering connections between related pages, with persistent history and queue resumption.
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables creating, linking, tagging, searching and exploring atomic notes that form a networked knowledge graph, with bidirectional semantic link types and markdown files as the source of truth. Supports knowledge creation, exploration and synthesis through Claude and other MCP-compatible clients.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables users to create, link, tag, search, and update atomic notes stored as Markdown files with a SQLite index, building a bidirectional knowledge graph that can be explored and synthesized through Claude and other MCP-compatible clients.
      -

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a clearly distinct action: read_note (fetch by ID) vs search_wiki (hybrid query) vs find_related (graph BFS) are well differentiated by their descriptions. Minor overlap exists between verify_citations and find_broken_links (both validate [[id]] references) and between suggest_new_note and find_related (both surface related notes), but the descriptions make the boundaries workable.

    Naming Consistency4/5

    Nearly all tools follow a clean snake_case verb_noun pattern (read_note, create_note, update_note, delete_note, add_link, list_domains, find_related). A couple of minor deviations (reindex as a bare verb, ingest_raw as verb_adjective) slightly break the pattern but remain readable and predictable.

    Tool Count5/5

    15 tools is well-scoped for a wiki system covering CRUD, search, graph traversal, templates, ingestion, and maintenance. Each tool earns its place with a distinct role; nothing appears redundant or padded.

    Completeness4/5

    Full note lifecycle is covered (create/read/update/delete) plus linking, templates, stats, ingestion, reindexing, and citation/broken-link checks. Minor gaps remain: no list_notes to enumerate all notes (only list_domains and stats), and no rename/move operation, but agents can work around these via search and domains.