Skip to main content
Glama
t-rhex

mcp-obsidian-vault

by t-rhex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-obsidian-vault

No user-submitted related servers found.

    Related Servers

    • Obsidian MCP Server

      suhailnajeeb
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Obsidian vaults through direct filesystem access, supporting note management, lightning-fast search with SQLite indexing, image analysis, tag/link management, and bulk operations.
      MIT

    • Obsidian Second Brain MCP

      dhaseeb-proj
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to store and retrieve project context, bugs, decisions, and session logs by reading and appending markdown files in a local Obsidian vault, without requiring any cloud services.
      6
      MIT

    • obsidian-agi-workspace-mcp

      yunzaixi-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to use Obsidian vaults as persistent, bidirectional knowledge workspaces with wikilink/backlink resolution, structured frontmatter/tag indexing, task aggregation, and Obsidian Headless Sync.
      11
      MIT

    • Obsidian MCP Server

      markheramis
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Obsidian vaults via direct filesystem access for managing notes, folders, and metadata. It features advanced search capabilities and multi-layer caching to provide efficient, real-time access to your personal knowledge base.
      2,778 npm
      MIT

    • brain-mcp

      kaeldominion
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely read and write to an Obsidian-compatible Markdown vault with per-agent access control, audit logging, and conflict resolution.
      Apache 2.0
    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.6/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target a distinct resource and action (notes, tasks, agents, usage, git), so boundaries are generally clear. Minor overlap exists between log_discovery/log_decision and manage_tags/update_note, but descriptions make the intended use recognizable.

    Naming Consistency4/5

    The overwhelming majority of tools follow a clean verb_noun pattern (create_note, list_tasks, get_usage_report, complete_task). The exceptions are daily_note, git_sync, and wikilinks, which break the pattern but are still readable and predictable.

    Tool Count2/5

    At 27 tools, this exceeds the 25-tool threshold and feels overloaded for a single MCP server. The server combines note management, task/project management, agent routing, usage tracking, and git operations, which would be better split into separate focused servers.

    Completeness4/5

    Notes have full CRUD plus search, tags, wikilinks, daily notes, and git sync, while tasks cover create, claim, update, complete, review, timeouts, and project rollups. Notable gaps include no get_task/delete_task, no update/delete_project, and no explicit agent deactivation, but agents can work around these.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources