Obsidian MCP Server

Created By
roelvena year ago
MCP (Model Context Protocol) server for Obsidian notes access via CouchDB LiveSync
Overview

What is Obsidian MCP Server?

Obsidian MCP Server is a Model Context Protocol (MCP) server that allows AI models to access your Obsidian notes through a CouchDB LiveSync setup.

How to use Obsidian MCP Server?

To use the server, set up a CouchDB instance with your Obsidian notes, configure the environment variables, and run the server using Docker or locally with Python.

Key features of Obsidian MCP Server?

  • Read-only access to Obsidian notes via MCP protocol.
  • Performance-optimized resource listing of recent notes.
  • Enhanced user experience with automatic content inclusion for small result sets.
  • Seamless integration with existing Obsidian LiveSync infrastructure.
  • Metadata extraction including frontmatter, tags, and aliases.
  • Support for encrypted vaults.
  • Docker support for easy deployment.

Use cases of Obsidian MCP Server?

  1. Integrating AI clients like ChatGPT with Obsidian notes.
  2. Accessing and searching notes efficiently through a CouchDB backend.
  3. Enabling read-only access to notes for various applications.

FAQ from Obsidian MCP Server?

  • Can I use this server with encrypted notes?

Yes, if you provide the VAULT_PASSPHRASE, it can handle encrypted vaults.

  • Is it necessary to use Docker?

No, you can run it locally with Python, but Docker is recommended for ease of use.

  • What is the MCP protocol version supported?

The server supports MCP protocol version 2025-03-26.

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

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago