Vault Cortex

Name: Vault Cortex
Author: aliasunder

@aliasunder

Vault Cortex について

MCP server that exposes an Obsidian vault to any MCP client — no Obsidian plugins required. 26 tools + 3 prompts across vault CRUD, hybrid search (FTS5 + vector + cross-encoder reranking), task queries (Tasks-plugin + Dataview formats), structured memory (About Me/ files), link g

#obsidian #vault #hybrid-search #semantic-search #reranking #memory #tasks #knowledge-graph #oauth #note-taking #daily-notes

基本情報

カテゴリ

開発者ツール

トランスポート

stdio

公開者

aliasunder

投稿者

T Aberdeen

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "vault-cortex": {
      "url": "http://localhost:8000/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_MCP_AUTH_TOKEN>"
      }
    }
  }
}

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Vault Cortex?

Vault Cortex gives any MCP client — Claude Desktop, Claude Code, Cursor, OpenCode — full access to your Obsidian vault through 26 tools and 3 guided prompts over a single Docker container. It works directly with .md files on disk, removing the need for Obsidian to be running or for a Local REST API plugin.

How to use Vault Cortex?

Run npx vault-cortex@latest init after installing Docker and Node.js >= 20.12 and pointing to an Obsidian vault. Alternatively, follow the local or remote deployment guides in the repository. Authentication can be configured via OAuth 2.1 or a static bearer token.

Key features of Vault Cortex

Plugin‑free: Obsidian does not need to be running
Remote access via OAuth 2.1 from any MCP client
Hybrid search: FTS5 + vector similarity + cross‑encoder reranking
Structured memory for persistent AI personalization
Obsidian‑native: frontmatter, wikilinks, tags, headings, daily notes
Task queries parsing both Tasks‑plugin and Dataview formats
Link graph: backlinks, outgoing links, orphan detection

Use cases of Vault Cortex

Search notes using keyword, semantic, or hybrid queries across an entire vault
Read, write, patch, or delete note content and front‑matter properties
Query tasks by status, dates, priority, folder, or heading
Explore the link graph to find backlinks, outgoing links, and orphans
Manage structured memory entries with dated sections for AI context
Retrieve, create, or review daily notes programmatically

FAQ from Vault Cortex

How does Vault Cortex differ from other Obsidian MCP setups?

Vault Cortex works directly with .md files on disk, so Obsidian doesn’t need to be running. It replaces the typical three‑part setup (Obsidian + Local REST API plugin + separate MCP server) with a single Docker container.

What are the prerequisites to run Vault Cortex?

You need Docker, Node.js >= 20.12, and an Obsidian vault. The quick start uses npx vault-cortex@latest init to configure the server.

How does authentication work?

Vault Cortex supports OAuth 2.1 with dynamic client registration, JWT access tokens, and 60‑day sliding refresh for clients like Claude Desktop and Claude Code. A static bearer token (MCP_AUTH_TOKEN) is also available for use with Claude Code, MCP Inspector, or curl.

Can I run Vault Cortex remotely?

Yes. Vault Cortex supports remote access via OAuth 2.1 and can be used from a phone, a remote server, or any MCP client. Separate remote deployment instructions are provided in the repository.

Where does Vault Cortex store data?

It reads and writes directly to your Obsidian vault’s .md files on disk. No additional database or cloud storage is required; the server works with your existing vault folder.

「開発者ツール」の他のコンテンツ

MCP Unity Editor (Game Engine)

CoderGamester

Model Context Protocol (MCP) plugin to connect with Unity Editor — designed for Cursor, Claude Code, Codex, Windsurf and other IDEs

1.8K

Golf

golf-mcp

Production-Ready MCP Server Framework • Build, deploy & scale secure AI agent infrastructure • Includes Auth, Observability, Debugger, Telemetry & Runtime • Run real-world MCPs powering AI Agents

834