Obsidian MCP Server

Created By
pmmvra year ago
MCP server enabling AI agents to perform natural knowledge discovery and analysis across Obsidian vault
Overview

What is Obsidian MCP Server?

The Obsidian MCP Server is a Model Context Protocol server that enables AI agents to perform natural knowledge discovery and analysis across your Obsidian vault using the Local REST API plugin.

How to use Obsidian MCP Server?

To use the server, install the Obsidian Local REST API plugin, configure it in your Obsidian settings, and run the MCP server using the command obsidian-mcp.

Key features of Obsidian MCP Server?

  • Advanced search capabilities with flexible filters and full content retrieval.
  • Support for regex patterns for complex text matching.
  • Tools for retrieving note content and browsing vault structure efficiently.

Use cases of Obsidian MCP Server?

  1. Performing strategic project analysis by retrieving and analyzing project documentation.
  2. Mining action items from meeting notes for better task management.
  3. Conducting research gap analysis by identifying knowledge gaps and suggesting team members for assistance.

FAQ from Obsidian MCP Server?

  • Is the server easy to set up?

Yes! Follow the installation instructions to set up the server quickly.

  • Can I use it with any Obsidian vault?

Yes! As long as you have the Local REST API plugin installed, it works with any vault.

  • What programming language is it built with?

The server is built using Python.

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

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago