Obsidian MCP Server

Created By
StevenStavrakisa year ago
A simple MCP server for Obsidian
Overview

what is Obsidian MCP Server?

Obsidian MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to interact with Obsidian vaults, enabling users to read, create, edit, and manage notes and tags effectively.

how to use Obsidian MCP Server?

To use the Obsidian MCP Server, configure it in your Claude Desktop application by adding the server details to the configuration file and specifying the path to your Obsidian vault. Restart Claude Desktop to connect the server.

key features of Obsidian MCP Server?

  • Read and search notes in your vault
  • Create new notes and directories
  • Edit existing notes
  • Move and delete notes
  • Manage tags (add, remove, rename)
  • Search vault contents

use cases of Obsidian MCP Server?

  1. Managing personal notes and research in Obsidian.
  2. Automating note-taking processes with AI assistance.
  3. Organizing and tagging information for better retrieval.

FAQ from Obsidian MCP Server?

  • Is it safe to use Obsidian MCP Server?

Yes, but ensure you backup your Obsidian vault before use, as it has read and write access.

  • What are the system requirements?

You need Node.js 20 or higher and an Obsidian vault to use this server.

  • How do I troubleshoot connection issues?

Check the configuration file syntax, ensure the vault path is correct, and review the logs for errors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
StevenStavrakis
Star
-
Language
-
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.

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago