Skip to main content
Glama

Related Servers

Alternatives to vault-bridge

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      Local-first MCP server for Obsidian vaults with 66 tools for reading, writing, searching, and managing notes, tasks, graphs, and more. Works without Obsidian running and requires no plugins.
      66
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Local MCP server that automates an open Obsidian vault through Obsidian's official CLI, offering tools for note creation/update, search, tasks, daily notes, and organization. It uses MCP over STDIO, requires no cloud services, and provides safety/audit features for autonomous writes.
      10
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Obsidian vaults — multi-brain manager with templates, persistent registry, search, CRUD, frontmatter, wikilinks and context bundling. Works with Hermes Agent and Claude Code simultaneously.
      MIT
    • F
      license
      C
      quality
      C
      maintenance
      MCP server to query and modify an Obsidian vault or any folder of markdown files. It provides search, tag filtering, backlinks, and CRUD operations on notes, with path traversal protection.
      11
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Obsidian that exposes tools for reading/writing notes, managing frontmatter and tags, querying Tasks, semantic search, and interacting with Obsidian Bases, with shared local caching and support for various runtime modes.
      40
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are mostly distinct: read/write/list/search are clearly separated, and search_notes vs search_frontmatter are differentiated by search type. However, search_notes and search_frontmatter could be confused if an agent doesn't read carefully, though the descriptions clarify the distinction.

    Naming Consistency4/5

    Tool names follow a consistent verb_noun pattern (read_note, write_note, list_notes, search_notes, search_frontmatter, get_daily_note). The only minor deviation is get_daily_note, which uses 'get' instead of 'read' and includes a specific noun, but it's still predictable.

    Tool Count5/5

    Six tools is well-scoped for a vault-bridge server. Each tool covers a distinct core operation for interacting with an Obsidian vault, and none feel redundant or excessive.

    Completeness4/5

    The tool set covers the core note lifecycle: read, write, list, search, and daily note handling. Missing operations like delete_note or rename_note are minor gaps since agents can work around them, but the surface is largely complete for typical vault interactions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues