claude mcp add vault-cortex -- npx -y vault-cortex
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
27 ★ · aliasunder/vault-cortex · read from the repository page · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 27 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository aliasunder/vault-cortex;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
Third-party quality signals
**Vault Cortex** is a standalone MCP server that gives any AI agent **hybrid sea
**Contents** — What you get · Quick Start · How It Works · Hybrid Search · Memory · Tasks · Files · Tools · Prompts · Properties · Config · Daily Notes · Data Integrity · Auth · Deployment · One-click Deploy · Community Deployments What you get Search the vault Reason over notes Write back to Obsidian All three demos run on Claude mobile. The vault is on a remote server, not the phone. - **Remote access** — works from your phone, a remote server, or any MCP client via OAuth 2.1. One click on Render or Railway gets you there with no server to manage; a VPS works too. - **Plugin-free** — Obsidian doesn't need to be running. The server works directly with .md files on disk. Headless sync keeps the vault current. - **Hybrid search** — FTS5 keyword matching + vector semantic similarity via RRF fusion, refined by cross-encoder reranking for intent-heavy queries. Keywords stay precise on exact terms and jargon; vectors find notes even when your words differ from the vault's. - **Structured memory** — dated, append-only entries accumulate into a personal knowledge layer, auto-initialized for AI personalization. Topic recall answers "what do I think about X?" with the current take and the dated history behind it — evolution included. - **Tasks** — Kanban-aware task queries and updates: triage by status, dates, or priority, then complete, reprioritize, or move tasks between lanes in one call. Completing a recurring task spawns its next occurrence. Parses both Tasks plugin emoji and Dataview inline-field formats. - **Link graph** — backlinks, outgoing links, and orphan detection across the vault - **Files** — read the vault's non-markdown files too: images arrive as actual images (shrunk to fit when needed), PDFs as structured text or rendered pages, canvases as readable outlines, data files as text - **Obsidian-native** — understands frontmatter, wikilinks, tags, headings, and daily notes - **Guided workflows** — built-in prompts for vault health, memory review, and daily reconciliation — assembled from live vault data each time **Tested across a 15-day trip through Europe.** 30+ sessions from a phone, 216 tool calls, zero laptop access needed. Writes in one session were immediately available in the next, across cities and days. --- Quick Start Local (2 minutes — Docker + your vault folder) **Prerequisites:** Docker (or a Docker-compatible runtime, e.g. OrbStack, Colima, Podman), Node.js >= 22.12 (only for the CLI — the server itself runs in Docker), and an Obsidian vault (or any folder of .md files). That's it — the CLI asks for your vault path, generates the auth token and config files, starts the server, and prints the connection details for your MCP client (CLI reference →). **Set up with the CLI?** It manages the server from here on — configure, upgrade, start, restart, logs, down (CLI reference →). **Set up with Compose?** Stick with Compose for updates too (docker compose pull && docker compose up -d) — the CLI and Compose manage the container independently. Manual setup (no Node.js needed) **Full local guide →** (includes Windows setup) Remote (access from anywhere) Your vault on a server, kept current by Obsidian Sync, reachable from your phone, claude.ai, or any MCP client. The one-click options ask for your vault name and timezone (plus the vault password if your vault is encrypted), then handle HTTPS, restarts, a generated MCP token, and persistent storage. Once deployed, a setup page walks you through signing in to Obsidian Sync in your browser. On your own server the CLI asks for the public URL and vault name, captures the Sync token for you, and generates the MCP token; HTTPS is yours to set up. | | Railway | Render | Self-hosted | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | | | | **CLI setup →** | | **Account** | Railway on the Hobby plan or higher — the 5 GB volume is included | Render with a card on file | A VPS with Docker | | **Cost** | Usage-metered: typically $20–30 USD/mo for a personal vault — a little under Render for a quiet vault, a little over for a busy one | Flat: about $26 USD/mo for the Standard instance (2 GB) and 5 GB disk, billed by the second | Whatever your VPS costs |