mcp -obsidian-omnisearch

This MCP server provides a REST API that lets you search Obsidian vault notes using the Obsidian Omnisearch plugin. It exposes a simple search endpoint that returns absolute paths to matching notes, enabling easy integration with other tools and services via the FastMCP protocol. You can run the server with a command that launches the Python-based MCP server module and passes the path to your Obsidian vault, then query it through your preferred MCP client or via a downstream tool that speaks the FastMCP protocol.

To use it, ensure the Obsidian Omnisearch plugin is installed and running in your Obsidian vault so that the server can query and index notes as needed. Start the server according to your deployment preference (Development/Unpublished or Published configuration) and point your client at the provided vault path. The API focuses on note search functionality and returns absolute file-system paths to the matching notes for easy downstream processing.

Prerequisites:

• Python 3.x
• Obsidian with the Omnisearch plugin installed and running
• FastMCP library (or the uv/uvx tooling required for your setup)
• An active Obsidian vault

Option 1: Installing via Smithery (Recommended for automated deployment)

npx -y @smithery/cli install @anpigon/mcp-server-obsidian-omnisearch --client claude

Option 2: Manual Installation

1. Clone the repository:

git clone https://github.com/anpigon/mcp-server-obsidian-omnisearch.git
cd mcp-server-obsidian-omnisearch

2. Install dependencies using uv (Python tooling):

uv install

3. Run the server (example with your vault path; adjust as needed):

python server.py /path/to/your/obsidian/vault

Note: The README describes configurations for development and published deployments using uv/uvx. If you’re using Those configurations, follow the corresponding commands to launch the server with the vault path as an argument.

Tips and notes:

• The Obsidian Omnisearch plugin must be running in your Obsidian vault for the server to query notes.
• The server accepts the vault path as a command-line argument; ensure the path is accessible from where you run the MCP server.
• If you publish via uvx, you typically invoke the module name and vault path: uvx mcp-server-obsidian-omnisearch /path/to/your/obsidian/vault
• For debugging, you can use the MCP Inspector tool to attach to the running MCP server and inspect traffic.
• Logs can be monitored to diagnose issues; the README references a Claude-specific log path which may vary by environment.
• Ensure network/firewall settings allow your MCP client to communicate with the server if running on a different host.
• If you change the vault path, restart the server to take effect.