The value here is that it does not build its own index: Omnisearch is already ranking your notes inside Obsidian, and this exposes that ranking over one tool. What comes back is paths, not note contents — pair it with a filesystem server if you want the agent to read what it finds, and keep in mind that Obsidian has to be running for any of it to answer.
A FastMCP server that passes a query to the Omnisearch plugin running inside your own Obsidian and returns the matching notes as absolute paths.
- Full-text search across the vault through obsidian_notes_search, using Omnisearch's own ranking rather than a filename match
- Absolute paths back, so a filesystem tool can open the notes the search found
- The vault chosen at launch — you pass its path as a command line argument
Obsidian must be open with the Omnisearch community plugin installed and its local API enabled — the server talks to that, not to the files. Runs from uvx as mcp-server-obsidian-omnisearch with the vault path as an argument. Python 3.x, no account, no key.
One command — npx -y @smithery/cli install @anpigon/mcp-server-obsidian-omnisearch --client claude
