Skip to main content
Glama
gronare

notes-vault-mcp

by gronare
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to notes-vault-mcp

No user-submitted related servers found.

    Related Servers

    • obsidian-guarded-mcp

      cyber-sami
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to securely read, search, and edit Markdown notes across multiple Obsidian vaults with path guards, soft delete, and vault switching.
      MIT

    • obsidian-mcp

      jason-c-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables reading, writing, searching, and managing an Obsidian vault through Claude, operating directly on markdown files via Node.js fs without requiring the Obsidian app.
      12,601 npm
      MIT

    • obsidian-connector

      reyk-zepper
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables bidirectional interaction with Obsidian vaults, allowing reading, writing, and organizing notes through Claude.
      MIT

    • pando

      sigrmoff
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to search, read, write, and manage a local markdown vault through 8 tools, turning your notes into an AI-accessible knowledge base.
      3 npm
      AGPL 3.0

    • obsidian-mcp

      bbdaniels
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude Code read/write access to an Obsidian vault, including creating, editing, searching, and browsing notes.
      8
      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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool owns a clearly distinct operation: search/list_files/context/lint cover different discovery and integrity concerns, while read_file/write_file/append_file/move_file/delete_file/close/log_append cover separate mutation or lifecycle actions. Even the pair write_file/append_file is well separated by full-file conditional write versus append-and-create behavior.

    Naming Consistency3/5

    Most file operations follow a clean verb_noun pattern (read_file, write_file, append_file, move_file, delete_file, list_files), but search, close, context, and lint are single words and log_append reverses the pattern. The naming is readable and grouped by function, but it is not consistently predictable across the whole surface.

    Tool Count5/5

    Eleven tools is well within the ideal scope for a notes vault server: discovery, read/write, move/delete, archive, session context, logging, and lint each have a dedicated tool. No tool feels redundant or like filler.

    Completeness4/5

    The surface covers the core lifecycle thoroughly: search/read/create/update/append/move/delete/archive, plus session context, logging, and lint. The main gap is the lack of an explicit restore/reopen operation for archived notes, though move_file combined with write_file can work around it.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources