Obsidian Hybrid Search runs on your own machine — the client starts it, so there is no endpoint to ping. 674 installs a week from npm. Last commit 17 Sep 2026.
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.
We read the source, 19 h ago · rules 3dff92dd89df
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(options.command, [...options.args], {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Run auto-tag for dependency update merge
if: steps.merge.outputs.commit
env:
GH_TOKEN: ${{ github.token }}
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 -- npx -y obsidian-hybrid-search
{
"mcpServers": {
"obsidian-hybrid-search": {
"args": [
"-y",
"obsidian-hybrid-search"
],
"command": "npx"
}
}
}
[mcp_servers.obsidian-hybrid-search]
command = "npx"
args = ["-y", "obsidian-hybrid-search"]
{
"mcpServers": {
"obsidian-hybrid-search": {
"args": [
"-y",
"obsidian-hybrid-search"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"obsidian-hybrid-search": {
"args": [
"-y",
"obsidian-hybrid-search"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
OBSIDIAN_VAULT_PATH (Absolute path to the Obsidian vault to index and search.), 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 root and nested .gitignore files when indexing; set to false, 0, or no to disable.), OBSIDIAN_INCLUDE_PATTERNS (Comma-separated patterns to re-include notes ignored only by .gitignore.), 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.).
The author declared them in the registry entry; get the values from the project itself.
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.
Local semantic search over your Obsidian vault - always fresh, never reindex.
Access Obsidian vaults via Local REST API - read, search, and interact with notes
Filesystem-direct Obsidian MCP server — search and edit your vault with low context-tax.
Read-only semantic search MCP server for Obsidian vaults using local Ollama embeddings.
Answers built from our own checks of this server.