Obsidian MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Obsidian MCP Server?

Obsidian MCP Server is a lightweight Model Context Protocol (MCP) server that allows AI assistants like Cursor and Claude to interact with your Obsidian vault, enabling reading and writing capabilities.

how to use Obsidian MCP Server?

To use the server, install it via npm, build it, and configure it with your AI assistant by specifying the path to your Obsidian vault in the server settings.

key features of Obsidian MCP Server?

  • Enables AI assistants to read from and write to Obsidian vaults.
  • Provides tools to retrieve filenames, read file contents, and update files.
  • Lightweight and does not require the Obsidian application to be running.

use cases of Obsidian MCP Server?

  1. Automating note creation for daily standups.
  2. Checking project ideas and todos directly from AI assistants.
  3. Updating notes and managing tasks through voice commands.

FAQ from Obsidian MCP Server?

  • Can I use this server without running Obsidian?

Yes! The server allows direct filesystem access without needing the Obsidian application.

  • How do I integrate it with AI assistants?

You can add the server to your AI assistant's configuration by specifying the command and path to your vault.

  • Is it free to use?

Yes! The Obsidian MCP Server is open-source and free to use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
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