
Obsidian Hybrid Search
io.github.flowing-abyssPublished by GitHub account flowing-abyssv0.17.4Updated Nov 5, 2026
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval.
Overview
Indexes a local Obsidian vault and lets an AI assistant search it by keyword, meaning, title or link graph, and read notes with their metadata.
- What you can do
- Search notes with hybrid, semantic, fulltext or fuzzy title modes, with folder, tag and frontmatter filters
- Find notes similar to a given note and traverse outgoing links and backlinks to a chosen depth
- Read one or more notes by vault-relative path, returning content, title, aliases, tags, links and backlinks
- Rebuild or refresh the index and check indexing status, note counts and last indexed time
- When to use it
- Useful when you keep notes in an Obsidian vault and want an assistant to ground answers in your own notes instead of pasted text, including following links between notes and pulling cited context from source files.
- Requirements
- Runs locally over stdio via npx, or as a shared local HTTP server on 127.0.0.1:3939. Requires Node.js and the absolute path of the vault in OBSIDIAN_VAULT_PATH. Local embeddings work offline but download roughly 117 MB on first use; remote embeddings need OPENAI_API_KEY and optionally OPENAI_BASE_URL and OPENAI_EMBEDDING_MODEL. Optional reranking downloads a separate model.
Installation
In SourceWeft
- Open Obsidian Hybrid Search in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Obsidian Hybrid Search
[npm version] [Tests] [Total downloads]
[Obsidian Hybrid Search explains hybrid retrieval from Obsidian notes]
Your Obsidian vault already contains your best thinking. Obsidian Hybrid Search makes that thinking easier to find, reuse, and bring into AI-assisted work.
It gives your vault one retrieval engine and three practical ways to use it. The native Obsidian plugin gives you fast search, previews, similar notes, link discovery, and graph views while you write. The MCP server lets AI agents search and read your notes as tool calls. The CLI gives power users the same engine for indexing, filtering, reranking, reading, and scripting.
The search understands how real vaults are built. It combines semantic search, BM25 full text, fuzzy title and alias matching, tags, folders, frontmatter, wikilinks, backlinks, and similar-note lookup. You can search by idea, phrase, title, relationship, or metadata without remembering the exact words you wrote.
That turns Obsidian into a stronger personal knowledge system and a better starting point for AI work. Agents can begin from your own notes, pull cited context from source files, follow related material, and work with knowledge you already trust. OHS runs locally by default with SQLite, FTS5, sqlite-vec, RRF ranking, and optional OpenAI-compatible embedding APIs.
Search quality
Evaluated on the Obsidian Help vault (171 notes, 58 queries, local model):
¹ CPU (Apple Silicon), hybrid mode, no rerank. ² GPU (Apple Silicon Metal), LLM query expansion + reranking.
OHS uses Xenova/multilingual-e5-small. How to reproduce → · Full benchmark →
Real knowledge-vault benchmark
OHS is also evaluated on Andy Matuschak’s public evergreen notes, converted into an Obsidian vault with title-based note filenames, source URLs in frontmatter, local attachments, and 5,000+ internal note links across 1,357 notes.
The curated golden set includes 78 hand-judged queries across known-item lookup, paraphrases, quote fragments, ambiguous topics, citation lookup, and multi-note evidence.
Using the default local embedding model, OHS performs strongly on this dense note network.
The benchmark exercises retrieval over a highly connected real-world knowledge vault, including queries that do not simply repeat note titles.
Result JSON · Reproduce and interpret →
Large memory benchmark
To test retrieval on a larger public dataset,
LongMemEval-S
was converted into a 22,419-note Obsidian-style vault with 470 retrieval
queries. Using baai/bge-m3 embeddings, OHS ranked the answer-bearing notes
strongly:
For this benchmark, each query uses the LongMemEval-provided haystack as its search scope. That makes the result reproducible and easy to inspect query by query, while still exercising retrieval over a large generated memory vault.
Result JSON · Reproduce and interpret →
Features
- Hybrid search
- BM25 + fuzzy title + semantic embeddings, fused with RRF
- Alias search
- notes with
aliases:in frontmatter are indexed and searchable by any alias; alias matches are boosted in BM25 (weight 5×) and fuzzy title scoring
- notes with
- Four search modes
hybrid,semantic,fulltext,title(for text queries)
- Similar note lookup
- pass
--pathto find semantically related notes using stored chunk embeddings, with a title + content fallback
- pass
- Graph traversal
--path --relatedshows linked notes at configurable depth; filter by--direction outgoing|backlinks|both
- Links & backlinks
- every result includes outgoing links and backlinks
- Scope filtering
- restrict to subfolder(s); supports multiple values and exclusions (
-notes/dev/)
- restrict to subfolder(s); supports multiple values and exclusions (
- Tag filtering
- filter by tag(s); supports multiple values and exclusions (
-category/cs)
- filter by tag(s); supports multiple values and exclusions (
- Snippet control
--snippet-lengthsets the context window; empty snippets always fall back to note content
- Extended output
--extendedadds a TAGS/ALIASES column to the CLI table showing frontmatter tags (#tag) and aliases
- Incremental indexing
- only re-indexes changed files; watches for edits in real time
- Multi-query fan-out
- pass multiple queries at once (
ohs "q1" "q2"orqueries[]in MCP); results are merged via RRF, so a note that ranks well in any one query floats to the top; useful when the note may use different vocabulary than the query
- pass multiple queries at once (
- Cross-encoder reranking
--rerankre-scores results withgte-multilingual-reranker-base(ONNX int8, ~341 MB download once); improves precision for conceptual and multilingual queries; applied after multi-query merge
- Local embeddings
- works offline via
@huggingface/transformers(no API key required); default model: Xenova/multilingual-e5-small, 100+ languages
- works offline via
- Remote embeddings
- OpenAI-compatible API (OpenRouter, Ollama, etc.)
- Note reading
readfetches one or more notes by vault-relative path; returns full content with title, aliases, tags, links, and backlinks; on path miss returns top-3 fuzzy suggestions
- Ignore patterns
- exclude folders, extensions, or specific files
- Obsidian plugin
- native search modal inside Obsidian powered by the same CLI; see obsidian-hybrid-search-plugin
Installation
CLI usage
Quick start
The recommended setup is to set OBSIDIAN_VAULT_PATH once in ~/.zshrc or ~/.bashrc. This lets you run the CLI from any directory.
Open a new terminal and index the vault once.
You can now search from any directory.
Run from a vault
Alternatively, run the CLI without an environment variable from any directory inside your vault. It finds the vault root by walking up to the nearest .obsidian/ folder.
From outside the vault, set OBSIDIAN_VAULT_PATH or pass --db /path/to/vault/.obsidian-hybrid-search.db explicitly.
Optional remote embeddings
By default, the CLI uses the local Xenova/multilingual-e5-small model. It works offline without an API key, downloads about 117 MB on first use, and supports more than 100 languages.
To use a remote API, add its settings to your shell profile.
Search modes
The CLI supports four search modes called hybrid, fulltext, semantic, and title, plus graph traversal for linked notes. The commands below show how to use them, apply filters, rerank results, and control the output.
Shell aliases
Add to your ~/.zshrc or ~/.bashrc for quick access:
Then reload (source ~/.zshrc) and use:
Output example
Hybrid search returns a table with scores and snippets. Scores are color-coded by relevance:
With --extended, a TAGS/ALIASES column is added. Tags are prefixed with #, aliases are shown as-is:
Title mode omits the snippet column automatically.
MCP server
Most AI assistants operate without access to your personal knowledge and can only work with what you paste into the conversation. Adding this server gives any MCP-compatible assistant a persistent, searchable index of your entire vault. It becomes a tool call, not a copy-paste session: the assistant queries your notes the same way it calls any other tool, gets ranked results with snippets and links, and can navigate your knowledge graph on request.
Add to your MCP config (.mcp.json, claude_desktop_config.json, or equivalent for your client).
Minimal config (local embeddings, no API key)
Uses the built-in Xenova/multilingual-e5-small model. It works fully offline and supports 100+ languages. Downloads ~117 MB on first run.
Full config (OpenRouter)
Note: On first run,
npxwill install the package automatically. Ignore patterns are persisted in the database and restored on every subsequent startup even if the env var is missing.
Shared HTTP server
Use this when multiple MCP clients should share one long-lived search/indexing process.
Start or reuse the background server:
serve starts the MCP server over HTTP by default; serve --http is the explicit equivalent. The command prints the server URL, PID, log path, and a client config snippet. The default bind address is 127.0.0.1:3939.
Then add this to a URL-based MCP client config (.mcp.json, claude_desktop_config.json, or equivalent):
Manage the server:
HTTP mode uses stateless MCP Streamable HTTP. It does not issue or validate Mcp-Session-Id, so an MCP client can continue making tool calls after the daemon restarts even if it still sends a stale session header. This mode is intended for the server's request/response tools and does not provide persistent SSE streams, server-initiated notifications, or SSE resume.
If port 3939 is already in use, the command exits with an error instead of choosing another port automatically. Use --port for separate vaults.
When binding beyond localhost, allow every hostname or address that MCP clients will use.
Repeat --allowed-host for multiple values. You can also set a comma-separated list with OBSIDIAN_MCP_ALLOWED_HOSTS. The --allow-any-host option disables Host-header protection for trusted networks.
Available MCP tools
Set OBSIDIAN_PREFIX to add a prefix to every tool name. For example, myvault_ produces myvault_search and myvault_read. The prefix is empty by default.
Configuration
Ignore patterns
- Use
folder/**to ignore a directory and all its contents. - Use
*.canvasto ignore files by extension. - Use
exact/path.mdto ignore a specific file. - Use
**/node_modules/**to ignore a directory at any depth.
Root and nested .gitignore files are respected by default. Set OBSIDIAN_RESPECT_GITIGNORE=false to disable this behavior. Use OBSIDIAN_INCLUDE_PATTERNS to re-include Markdown notes that are ignored only by .gitignore. Include patterns do not override OBSIDIAN_IGNORE_PATTERNS or internal exclusions.
The database stores the ignore configuration and restores it when the server restarts, even if the environment variable is missing.
How it works
- Indexing splits notes by headings with a sliding-window fallback, creates embeddings, and stores the results in SQLite with FTS5 and
sqlite-vec. - Search runs BM25, fuzzy trigram title and alias search, and vector KNN search in parallel. BM25 uses weights of 10× for titles, 5× for aliases, and 1× for content. RRF then gives semantic and BM25 results a weight of 1.5× each, exact alias matches 2×, and partial fuzzy matches 0.25×. The final scores range from 0 to 1, where higher scores mean greater relevance.
- Links are resolved from wikilinks such as
[[note]], mapped to note paths, and stored. Every search result includeslinksandbacklinksarrays. - Watcher uses
chokidarto detect file changes and update the index in the background.
License
MIT
Source: README.md at commit a450eff
Tools
0Version history
13- v0.17.4LatestNov 5, 2026
- v0.17.3Nov 4, 2026
- v0.17.2Oct 26, 2026
- v0.17.1Oct 25, 2026
- v0.16.4Oct 22, 2026
- v0.16.3Oct 19, 2026
- v0.16.2Oct 12, 2026
- v0.16.1Oct 5, 2026
- v0.16.0Sep 29, 2026
- v0.15.6Sep 21, 2026
- v0.15.5Sep 20, 2026
- v0.15.3Sep 17, 2026
- v0.15.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
