MCP Server Obsidian Omnisearch

Created By
anpigona year ago
An MCP server that enables searches within Obsidian vaults using the Omnisearch plugin API. Returns absolute paths to matching notes for seamless integration. 🚀
Overview

what is MCP Server Obsidian Omnisearch?

MCP Server Obsidian Omnisearch is a FastMCP-based server that provides programmatic search functionality through the REST API for notes in an Obsidian vault. It allows users to efficiently search and retrieve notes based on query strings.

how to use MCP Server Obsidian Omnisearch?

To use the server, clone the repository from GitHub, install the required dependencies, and run the server with the path to your Obsidian vault. The API can then be accessed following the setup of the Obsidian Omnisearch plugin.

key features of MCP Server Obsidian Omnisearch?

  • Programmatic search capability for Obsidian vault notes.
  • REST API integration for seamless use in other applications.
  • Returns absolute paths to notes matching the search query.
  • Easy integration with FastMCP tools for extended functionality.

use cases of MCP Server Obsidian Omnisearch?

  1. Searching for specific notes in a large Obsidian vault.
  2. Integrating Obsidian notes search into custom applications or workflows.
  3. Enhancing note organization and retrieval in personal knowledge management systems.

FAQ from MCP Server Obsidian Omnisearch?

  • What are the prerequisites for using MCP Server Obsidian Omnisearch?

You need Python 3.x, the Obsidian Omnisearch plugin, the FastMCP library, and an active Obsidian vault.

  • Can I run the server on any operating system?

Yes, the server can be run on any OS that supports Python and has access to the required libraries.

  • How can I debug issues while using the server?

Use the MCP Inspector for a better debugging experience and to monitor server logs.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
anpigon
Star
9
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago