Server data from the Official MCP Registry
Local semantic search over your Obsidian vault - always fresh, never reindex.
Local semantic search over your Obsidian vault - always fresh, never reindex.
Valid MCP server (2 strong, 4 medium validity signals). 1 code issue detected. 1 known CVE in dependencies (0 critical, 1 high severity) Package registry verified. Imported from the Official MCP Registry.
6 files analyzed · 3 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: FRESHVAULT_VAULT
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-kioko-lab-freshvault": {
"env": {
"FRESHVAULT_VAULT": "your-freshvault-vault-here"
},
"args": [
"-y",
"freshvault"
],
"command": "npx"
}
}
}From the project's GitHub README.
Your Obsidian vault is Claude's memory. Always fresh, always local.
Every other vault-search MCP makes you re-run an index command, babysit a watch terminal, or click "Update Index" in a web UI. freshvault watches your vault from inside the MCP server: edit a note, and Claude sees it seconds later. Automatically. Forever.

bge-m3), your notes never leave your machinebge-m3 handles Korean, Japanese, and 100+ languages that English-only defaults fail onPrerequisites: Node 20+ and Ollama.
npx -y freshvault setup
That's it. The wizard detects your Obsidian vault, pulls the embedding model, builds the index, and registers with Claude Code. There is no step 2, and there is never a step 2: no index command to re-run, no watch terminal, no background service.
{
"mcpServers": {
"freshvault": {
"command": "npx",
"args": ["-y", "freshvault", "serve"],
"env": { "FRESHVAULT_VAULT": "/absolute/path/to/your/vault" }
}
}
}
Claude Code one-liner:
claude mcp add freshvault -s user -- npx -y freshvault serve
Just ask Claude about your notes:
"Search my notes for what I wrote about cache eviction strategies"
Three tools, all read-only:
| tool | what it does |
|---|---|
search_notes | semantic search + optional folder / tags / modified_after / modified_before scoping; exact-title lookups boosted |
get_note_context | full note + its backlinks/outlinks from the vault link graph (path-traversal safe) |
index_status | freshness report: notes/chunks, excluded count, last sync, watcher state |
Scoped queries competitors gate behind settings or paywalls work per-query here:
"Search my notes tagged #project modified after June for the budget discussion"
Obsidian vault ──fs.watch──▶ freshvault MCP server ──search_notes──▶ Claude
(.md files) (chunks → bge-m3 embeddings (generation)
→ one JSON index, incremental)
Register one server per vault — index files are kept per-vault automatically:
claude mcp add work-vault -s user -e FRESHVAULT_VAULT=/path/to/work -- npx -y freshvault serve
claude mcp add personal-vault -s user -e FRESHVAULT_VAULT=/path/to/personal -- npx -y freshvault serve
FRESHVAULT_EMBED_API=openai FRESHVAULT_EMBED_URL=http://localhost:1234 npx -y freshvault serve
Anything speaking /v1/embeddings works; FRESHVAULT_EMBED_KEY for authenticated endpoints (never written to the config file).
Everything works with zero config after setup. Override when needed:
| Flag | Env | Default |
|---|---|---|
--vault | FRESHVAULT_VAULT | from setup |
--model | FRESHVAULT_MODEL | bge-m3 |
--ollama-url | FRESHVAULT_OLLAMA_URL | http://localhost:11434 |
--data | FRESHVAULT_DATA | platform data dir |
| — | FRESHVAULT_EMBED_API | ollama (or openai) |
| — | FRESHVAULT_EMBED_URL | http://localhost:1234 (openai mode) |
| — | FRESHVAULT_EMBED_KEY | none (openai mode, optional) |
| — | FRESHVAULT_IGNORE | none — e.g. Templates/,Daily/** (or ignore: [] in config) |
Commands: setup · serve (default) · index (manual escape hatch) · status
A Korean retrieval micro-benchmark ships in-repo (node scripts/bench.mjs) — 30 Korean notes, 40 paraphrase queries, comparing embedding models on top-1/MRR. Results and the bge-m3-ko (85.0% top-1, 634MB) import guide in docs/ko-bench.md.
MIT © Kioko Lab
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.