Obsidian Hybrid Search runs on your own machine — the client starts it, so there is no endpoint to ping. 1 634 installs a week from npm. Last commit 26 Oct 2026.
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.
We read the source, 6 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const result = spawnSync(entry.command, [...entry.args, ...args], options);
existsSync(path.join(cacheDir, modelName, event.file)) ||
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add obsidian-hybrid-search -e 'OBSIDIAN_VAULT_PATH=<OBSIDIAN_VAULT_PATH>' -- npx -y obsidian-hybrid-search
{
"mcpServers": {
"obsidian-hybrid-search": {
"command": "npx",
"args": [
"-y",
"obsidian-hybrid-search"
],
"env": {
"OBSIDIAN_VAULT_PATH": "<OBSIDIAN_VAULT_PATH>"
}
}
}
}
[mcp_servers.obsidian-hybrid-search]
command = "npx"
args = ["-y", "obsidian-hybrid-search"]
env = { OBSIDIAN_VAULT_PATH = "<OBSIDIAN_VAULT_PATH>" }
{
"mcpServers": {
"obsidian-hybrid-search": {
"command": "npx",
"args": [
"-y",
"obsidian-hybrid-search"
],
"env": {
"OBSIDIAN_VAULT_PATH": "<OBSIDIAN_VAULT_PATH>"
}
}
}
}
{
"servers": {
"obsidian-hybrid-search": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"obsidian-hybrid-search"
],
"env": {
"OBSIDIAN_VAULT_PATH": "<OBSIDIAN_VAULT_PATH>"
}
}
}
}
Put your own value in place of
<OBSIDIAN_VAULT_PATH> (Absolute path to the Obsidian vault to index and search).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
OBSIDIAN_PREFIX (Optional prefix for MCP tool names when configuring multiple vaults), OBSIDIAN_IGNORE_PATTERNS (Comma-separated glob patterns to exclude from indexing), OBSIDIAN_RESPECT_GITIGNORE (Read applicable .gitignore files and repository info/exclude rules when indexing; set to false, 0, or no to disable both), OBSIDIAN_INCLUDE_PATTERNS (Comma-separated patterns to re-include notes ignored only by Git ignore rules), OBSIDIAN_CONTENT_IGNORE_PATTERNS (Comma-separated regex rules for note body text to leave out of search, e.g. /%%[\s\S]*?%%/g. Original files and read stay unchanged), OPENAI_API_KEY (Optional API key for OpenAI-compatible remote embeddings; omit to use local embeddings), OPENAI_BASE_URL (Optional OpenAI-compatible API base URL for OpenRouter, Ollama, LM Studio, or similar providers), OPENAI_EMBEDDING_MODEL (Remote embedding model name when using an OpenAI-compatible API), LOCAL_EMBEDDING_MODEL (Local embedding model used when no remote embedding API is configured), RERANKER_MODEL (Optional ONNX cross-encoder reranker model used when reranking is requested).
Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults.
Semantic search and AI context for your Obsidian vault. Surface patterns with catalysts.
Obsidian MCP server: semantic search, knowledge graph, and vault editing. No plugin required.
Semantic search and pattern discovery for Obsidian and markdown vaults.
Self-hosted agent memory as a markdown vault: semantic and keyword search, wikilink graph, OAuth
Search an Obsidian vault by tag, term and wikilink graph. Read-only, deterministic, no embeddings.
Local semantic search over your Obsidian vault - always fresh, never reindex.
Search PubMed and PMC, read full texts, map evidence and build Obsidian knowledge graphs
Answers built from our own checks of this server.