- Home
- MCP servers
- Anpigon MCP Server Obsidian Omnisearch
Anpigon MCP Server Obsidian Omnisearch
- python
0
GitHub Stars
python
Language
7 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"mcp-mirror-anpigon_mcp-server-obsidian-omnisearch": {
"command": "uv",
"args": [
"--directory",
"<dir_to>/mcp-server-obsidian-omnisearch",
"run",
"mcp-server-obsidian-omnisearch",
"/path/to/your/obsidian/vault"
]
}
}
}You can search Obsidian vault notes programmatically through a dedicated MCP server. This Obsidian Omnisearch MCP server exposes a REST-friendly search interface and integrates with FastMCP so you can build powerful note-based workflows and tooling.
How to use
You run the server as an MCP stdio tool and connect to it from an MCP client. The server accepts the path to your Obsidian vault as a runtime argument and exposes a search API that returns absolute paths to notes that match your query. You can start it in development mode or use the published runtime configuration.
How to install
Prerequisites you need before installing and running this MCP server are listed below. Ensure each item is available on your system before proceeding.
-
Python 3.x installed on your system.
-
Obsidian with the Omnisearch plugin installed and running.
-
FastMCP library available in your environment.
-
An active Obsidian vault you want to search.
Install and run steps are shown below.
git clone https://github.com/anpigon/mcp-server-obsidian-omnisearch.git
cd mcp-server-obsidian-omnisearch
uv install
# Start the development server (vault path is provided as an argument).
python server.py /path/to/your/obsidian/vault
# Or use the published runtime configuration if you prefer a packaged runtime:
# See the Published Servers Configuration block for the exact runtime command and arguments.
Additional configuration and usage notes
You can run either of the following explicit MCP configurations to start the Obsidian Omnisearch MCP server. The development configuration uses uv and a directory flag, while the published configuration uses uvx to run a packaged server. Each configuration passes the path to your Obsidian vault as an argument.
{
"mcpServers": {
"obsidian_omnisearch": {
"command": "uv",
"args": [
"--directory",
"<dir_to>/mcp-server-obsidian-omnisearch",
"run",
"mcp-server-obsidian-omnisearch",
"/path/to/your/obsidian/vault"
]
}
}
}
Additional configuration and usage notes (published runtime)
If you prefer a published runtime configuration, use the packaged server with uvx. This runs the server executable with the vault path.
{
"mcpServers": {
"obsidian_omnisearch": {
"command": "uvx",
"args": [
"mcp-server-obsidian-omnisearch",
"/path/to/your/obsidian/vault"
]
}
}
}
API reference
Key API function exposed by this server is obsidian_notes_search(query: str). It searches Obsidian notes and returns a list of absolute paths to notes that match the provided query.
Development
You can build, sync, and publish this MCP server as part of your development workflow.
Building and publishing steps are shown below to prepare distributions and publish to PyPI.
uv sync
uv build
uv publish
Debugging
For debugging, the MCP Inspector provides an interactive debugging view for running MCP servers. You can launch it with a command like the one shown here.
npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-server-obsidian-omnisearch run mcp-server-obsidian-omnisearch
Dependencies
Primary dependencies include FastMCP, requests, and urllib.
License
This project is licensed under the MIT License.
Contributing
Contributions are welcome. Submit a Pull Request with your changes.
Available tools
obsidian_notes_search
API function that searches Obsidian notes and returns absolute paths to matching notes.
MCP Inspector
Debugging tool to inspect MCP server interactions at runtime.