Vault Cortex Obsidian MCP Server
Related Servers
Alternatives to Vault Cortex Obsidian MCP Server
- AlicenseAqualityAmaintenanceSelf-hosted MCP server for Obsidian with semantic + full-text search over PostgreSQL/pgvector, wikilink graph traversal, atomic note CRUD, OAuth 2.0, and a self-describing vault guide.2515MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to read, write, search, and manage Obsidian vault notes through a serverless MCP server deployed on Cloudflare Workers and R2 storage, utilizing Obsidian Sync for seamless bidirectional synchronization without requiring local NAS or tunnel infrastructure.3,358 npm1MIT
- AlicenseAqualityDmaintenanceA server that enables AI agents to perform sophisticated knowledge discovery and analysis across Obsidian vaults through the Local REST API plugin, supporting complex multi-step workflows with advanced filtering and full content retrieval.321MIT
- AlicenseBqualityDmaintenanceWraps the Obsidian CLI to allow LLM agents to read/write notes, search, manage frontmatter, navigate links, and run plugins on a running Obsidian instance.342MIT
- AlicenseAqualityAmaintenanceThe most feature-complete MCP server for Obsidian vaults. 23 tools and 3 resources for search, read, write, tags, link analysis, graph traversal, and canvas support.4154 npm30MIT
- AlicenseNot gradedqualityBmaintenanceA third-party MCP server for interacting with HashiCorp Vault to manage ACL policies, audit devices, and secret engines like KV v2, PKI, and Transit. It provides tools for system backend administration and includes prompts for generating security policy configurations.MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Obsidian — access your vault from any AI agent, even when your machine is off. Powered by Self-hosted LiveSync.146 npm56MIT
- AlicenseBqualityDmaintenanceLocal-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.66MIT
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server for private Obsidian vaults on GitHub, exposing tools to search, read, write, and analyze Markdown notes and their link graph.MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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
- AlicenseAqualityDmaintenanceMCP server that connects any AI to your Obsidian vault. Save articles from your phone, search across notes, build a compounding knowledge base. 15 tools, three transport modes (stdio, HTTP, cloud), zero-install Google Drive OAuth onboarding.157 npmMIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server that provides embedding-powered semantic search with graph context over Obsidian vaults, supporting multiple vaults, local embeddings, and a web dashboard.MIT
TDQS
Scored across 33 tools
Most tools have clearly distinct purposes, and cross-references like 'Prefer vault_search_by_tag' help disambiguate. However, the search/list family (vault_list_notes, vault_search_by_folder, vault_search_by_property, vault_search_by_tag, vault_list_tags, vault_list_property_keys) and the edit family (vault_patch_note, vault_replace_in_note, vault_replace_span, vault_insert_at_anchor, vault_delete_span) have overlapping boundaries that rely on careful description reading.
The vault_ prefix and mostly verb_noun naming make the set feel coherent and predictable. Minor deviations like vault_memory_recall, vault_insert_at_anchor, and vault_find_orphans break the strict pattern, but not enough to cause real confusion.
33 tools is a large surface, and while the server covers many subsystems, several could be consolidated—especially the overlapping search/list and edit variants. The count feels heavy for an agent to navigate, even given the broad scope of a full Obsidian vault server.
The note lifecycle, task workflow, memory layer, and graph navigation are thoroughly covered. The main gap is that non-markdown files are read-only—there is no file write, update, move, or delete—and there is no dedicated task deletion tool, though vault_delete_span can cover it.