Obsidian-MCP-Server

Created By
Trao95a year ago
Seamlessly integrate Claude AI into your Obsidian vault! This guide provides a straightforward setup for the Model Context Protocol (MCP) server on Windows 11, empowering Claude to directly assist your brainstorming, notetaking, and knowledge management within Obsidian.
Overview

What is Obsidian-MCP-Server?

Obsidian-MCP-Server is a guide for integrating Claude AI into your Obsidian vault, allowing for enhanced brainstorming, note-taking, and knowledge management through AI assistance.

How to use Obsidian-MCP-Server?

To use the Obsidian-MCP-Server, follow the step-by-step setup instructions provided in the guide to configure the Model Context Protocol (MCP) server on Windows 11, enabling Claude AI to interact with your Obsidian notes.

Key features of Obsidian-MCP-Server?

  • Seamless integration of Claude AI with Obsidian.
  • Ability for Claude to read, create, and modify notes in your vault.
  • Enhanced search capabilities across your knowledge base.

Use cases of Obsidian-MCP-Server?

  1. Brainstorming ideas with AI assistance.
  2. Generating and modifying notes based on AI prompts.
  3. Performing in-depth analysis and summarization of notes.

FAQ from Obsidian-MCP-Server?

  • Can I use Obsidian-MCP-Server with other AI applications?

The guide is specifically designed for Claude AI, but similar setups may work with other AI applications that support the Model Context Protocol.

  • Is there any cost associated with using Obsidian-MCP-Server?

The guide and integration are free to use, but ensure you have the necessary software installed.

  • What should I do if I encounter issues during setup?

The guide includes a troubleshooting section for common issues that may arise during the setup process.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Trao95
Star
1
Language
-
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
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