Skip to main content
Glama
russellsch

some-vault-some-mcp

by russellsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to some-vault-some-mcp

No user-submitted related servers found.

    Related Servers

    • Grove

      jmilinovich
      A
      license
      Not graded
      quality
      B
      maintenance
      An open-source MCP server that makes your Obsidian vault accessible from any AI client with hybrid search, read/write, and graph analysis capabilities.
      2 npm
      23
      MIT

    • obsidian-mcp

      seynurmammad0v
      A
      license
      Not graded
      quality
      D
      maintenance
      This MCP server turns any Obsidian vault into an AI-queryable knowledge graph, enabling graph traversal, search, and backlink-aware note manipulation without requiring Obsidian to be running.
      44 npm
      1
      MIT

    • Obsidian MCP Server

      TheGreatAxios
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that enables AI assistants to securely read, create, and modify notes in an Obsidian vault, with support for semantic search and web scraping.
      3,187 npm
      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

    B3.3/5.0

    Scored across 28 tools

    Disambiguation4/5

    Most tools target a distinct resource and action, but a few could be confused: search overlaps with list_notes for finding content, and get_graph_neighbors could be mistaken for a combined version of get_backlinks/get_outlinks. Overall, the descriptions are clear enough to separate the graph, note, and canvas operations.

    Naming Consistency4/5

    The dominant verb_noun pattern is consistent (create_note, move_note, delete_note, add_canvas_node, etc.), with minor deviations like bare 'search', 'vault_index_status' (noun_status), and singular/plural mismatches in canvas operations (update_canvas_node vs remove_canvas_nodes). These are readable and predictable.

    Tool Count3/5

    28 tools is on the heavy side for an MCP server, though the breadth is justified by covering notes, daily notes, link analysis, indexing, and canvases. It exceeds the typical well-scoped range and feels dense, but not bloated with near-duplicate functionality.

    Completeness4/5

    The note lifecycle is well-covered (create, read, update via append/prepend/frontmatter, move, delete), and link analysis plus canvas CRUD are thorough. Minor gaps exist: there is no in-place body editing or trash restore tool, and daily notes can only be created/read, not modified directly.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources