Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
FRESHVAULT_VAULT=<value> claude mcp add io.github.kioko-lab-freshvault -- npx -y freshvault@0.4.0Ejecútalo en una terminal.
{ "mcpServers": { "io.github.kioko-lab-freshvault": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FRESHVAULT_VAULT": "<value>" } } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirYour 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 onnpx -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:
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:
Commands: setup · serve (default) · index (manual escape hatch) · status
Patterns follow gitignore semantics, matched against vault-relative paths:
* and ? never cross a /. ** crosses directories only as a whole path segment (**/x, x/**, x/**/y); glued inside a segment it collapses to a single *, as in git.Templates never matches TemplatesOld.! negation and character classes are not supported; such patterns match nothing.FRESHVAULT_IGNORE is comma-separated, so a pattern cannot contain a comma.Behaviour change since v0.3.0. v0.3.0 treated a trailing slash as a root anchor, so
Templates/excluded only the vault-rootTemplates/and silently indexed every nested one — no warning, just a quietly polluted index. Patterns shaped likeTemplates/,/Templates,**/xanda/**/bnow exclude more than before (/Templatespreviously matched nothing at all). Conversely,**glued inside a segment (Daily**md) no longer crosses/. Runfreshvault statusafter upgrading and compare the excluded count if it matters to you.
Two retrieval micro-benchmarks ship in-repo (node scripts/bench.mjs): ko-bench (30 Korean notes, 40 paraphrase queries) and id-bench (38 technical notes, 14 identifier queries). Both run under three scoring modes — dense, hybrid-always, and the shipped gated mode — and the script checks the no-regression contract itself. Results and the bge-m3-ko (85.0% top-1, 634MB) import guide in docs/ko-bench.md.
MIT © Kioko Lab
Local semantic search over your Obsidian vault - always fresh, never reindex.
{ "mcpServers": { "io.github.kioko-lab-freshvault": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "FRESHVAULT_VAULT": "<value>" } } }}Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
El publicador indica estas variables de entorno: FRESHVAULT_VAULT.
Freshvault se ejecuta localmente por stdio.
Última comprobación: 2026-11-09. Local semantic search over your Obsidian vault - always fresh, never reindex.