Obsidian MCP Server Enhanced

Created By
labeverydaya year ago
This project provides a Model Context Protocol (MCP) server for interacting with Obsidian vaults through AI assistants.
Overview

What is Obsidian MCP Server Enhanced?

Obsidian MCP Server Enhanced is a Model Context Protocol (MCP) server designed to facilitate interaction with Obsidian vaults through AI assistants, enabling users to manage notes and knowledge without needing the Obsidian application open.

How to use Obsidian MCP Server Enhanced?

To use the server, install Obsidian and the Local REST API plugin, clone the repository, set up a virtual environment, install dependencies, and configure the API settings in a .env file. Finally, run the server using Python.

Key features of Obsidian MCP Server Enhanced?

  • File operations: Read, create, update, append, and delete notes.
  • Basic folder management: List files in folders.
  • Daily and meeting notes: Create structured notes with predefined templates.
  • Integration with Amazon Q CLI for enhanced functionality.

Use cases of Obsidian MCP Server Enhanced?

  1. Managing personal notes and documents efficiently.
  2. Automating note-taking for meetings and daily tasks.
  3. Enhancing knowledge management through AI-assisted organization.

FAQ from Obsidian MCP Server Enhanced?

  • Can I use this server without Obsidian?

No, the server requires Obsidian and the Local REST API plugin to function.

  • Is there a cost to use this server?

The server is open-source and free to use.

  • What programming language is used?

The project is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
labeveryday
Star
0
Language
Python
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
Crevio

2 days ago