Skip to main content
Glama
GMRoadlander

llm-wiki-mcp

by GMRoadlander
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to llm-wiki-mcp

No user-submitted related servers found.

    Related Servers

    • ObsidianMCP

      kuvarti
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server that exposes an Obsidian vault to LLM clients over Streamable HTTP, letting them browse the accessible tree, read notes, run full-text searches, and resolve wiki-links and backlinks within a share-filtered note set. Access is limited by an operator-editable sharing config that is default-deny and never writes to the vault.
      2,509 npm
      MIT

    • brain-mcp

      delian-research
      A
      license
      A
      quality
      D
      maintenance
      An MCP server for managing Obsidian-style note vaults, providing tools for full-text search, note creation, and backlink tracking. It enables users to navigate, structure, and update their personal knowledge base through natural language.
      9
      MIT

    • markdown-vault-mcp

      pvliesdonk
      A
      license
      A
      quality
      A
      maintenance
      A generic Markdown vault MCP server with FTS5 full-text search, semantic vector search, frontmatter-aware indexing, incremental reindexing, and non-markdown attachment support that exposes search, read, write, and edit tools.
      44
      172 PyPI
      33
      MIT

    • mcp-obsidian

      NeveuGregor
      F
      license
      A
      quality
      B
      maintenance
      A filesystem-based MCP server for Obsidian vaults that enables LLMs to browse, search, read, write, and edit Markdown notes directly on disk without requiring Obsidian to be running.
      6
      803 npm
      1
      -

    • vault-mcp

      seandavi
      A
      license
      A
      quality
      B
      maintenance
      MCP server that exposes an Obsidian-style markdown vault as a shared memory for AI agents, with tools for searching, reading, writing, and querying notes and wiki-links.
      12
      3
      MIT
    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/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools are largely distinct: read/search/list_recent cover read operations, write_note covers creation/append, get_links covers graph traversal. However, read_note and get_links both target a single note's content, and could occasionally be confused for retrieving note data, though their outputs differ enough to be clearly separable.

    Naming Consistency5/5

    All tool names follow a consistent verb_object pattern (read_note, search_wiki, list_recent, write_note, get_links). Verbs are clear and descriptive, with no mixing of conventions or vague imperative actions like 'process' or 'run'.

    Tool Count5/5

    5 tools is well-scoped for a wiki/vault MCP server, covering reading, searching, listing, writing, and graph traversal. Each tool serves a distinct purpose without redundancy, and the count is squarely in the ideal range.

    Completeness4/5

    The surface covers core note lifecycle well: read, search, write/create/append, and link analysis. Minor gaps exist—there's no update/rename/delete operation, though write_note's gated behavior (explicitly never deleting) suggests this is a deliberate design choice. The immutable source protection and dry_run flag further round out the surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources