Skip to main content
Glama
pvliesdonk

markdown-vault-mcp

by pvliesdonk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to markdown-vault-mcp

No user-submitted related servers found.

    Related Servers

    • Datacron

      VBlackJack
      A
      license
      A
      quality
      A
      maintenance
      Local MCP server for querying and maintaining a Markdown vault. Provides full-text search, backlinks, note retrieval, and optional confined write tools, without sending the whole vault to the client context.
      22
      541 PyPI
      1
      Apache 2.0

    • kmd

      bartolli
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for structured markdown knowledge vaults that provides validation, FTS5 search, and wikilink cross-references. Enables AI agents to prime context and search across vaults using two MCP tools and template resources.
      7
      MIT

    • moneta-notes-mcp

      ajmichels
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server exposing fast full-text and semantic search over an Obsidian vault, plus safe structured note read and write access for Claude.
      2
      Apache 2.0

    • vault-search-mcp

      everton-dgn
      A
      license
      B
      quality
      A
      maintenance
      Enables local hybrid search over Obsidian and Markdown vaults via MCP, combining vector retrieval, full-text search, reranking, graph navigation, and safe CRUD while keeping data local.
      43
      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.1/5.0

    Scored across 44 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose, reinforced by detailed descriptions and cross-references (e.g., show_context vs get_context, vault_* marked app-only). The graph-analysis tools (backlinks, outlinks, broken links, orphans, most_linked, connection_path) are each specific, and even the naming overlap between read/vault_read and search/vault_search is resolved by explicit app-only tags.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern with consistent prefixes like get_ and list_, but there are deviations: bare verbs (search, read, write, edit, append, delete, rename, fetch, reindex, stats) and irregular names like embeddings_status and the okf_/vault_ prefixed tools. The pattern is readable but not fully uniform.

    Tool Count2/5

    With 44 tools (even ~38 excluding app-only), the server is well beyond the 25+ threshold for 'too many'. Many read-only query tools could be consolidated (e.g., get_context already combines backlinks/outlinks/similar but the individual get_* tools remain), adding unnecessary selection complexity for an agent.

    Completeness5/5

    The tool surface provides complete lifecycle coverage: CRUD (write, read, edit, append, delete, rename, move_folder), search (keyword/semantic/list), link-graph analysis, index/embedding management, git history/diff, conventions, OKF migration, and UI tools. No significant gaps for a markdown vault server are apparent.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources