Obsidian Mcp Server

Created By
smith-and-web5 months ago
Overview

What is Obsidian MCP Server?

Obsidian MCP Server is a server that enables AI assistants to interact with your Obsidian vault, allowing for natural conversation to access notes, create content, manage tags, and search your knowledge base.

How to use Obsidian MCP Server?

You can run the server using npx or Docker. For npx, set the VAULT_PATH environment variable and execute the command: npx @smith-and-web/obsidian-mcp-server. For Docker, use the provided Docker commands to run the server with your vault mounted.

Key features of Obsidian MCP Server?

  • CRUD operations for notes (create, read, update, delete)
  • Frontmatter parsing and tag management
  • Full-text search and backlinks
  • Directory management and section operations
  • API key authentication for secure access

Use cases of Obsidian MCP Server?

  1. Integrating AI assistants like Claude with your Obsidian notes.
  2. Automating note management tasks through natural language commands.
  3. Enhancing productivity by allowing quick access to information in your vault.

FAQ from Obsidian MCP Server?

  • Can I use this server with any AI assistant?

Yes, as long as the assistant supports the Model Context Protocol (MCP).

  • Is there a way to secure the server?

Yes, you can enable API key authentication for secure access to the server endpoints.

  • What is the recommended way to deploy this server?

Using Docker is recommended for production environments.

Server Config

{
  "mcpServers": {
    "obsidian": {
      "command": "npx",
      "args": [
        "@smith-and-web/obsidian-mcp-server"
      ],
      "env": {
        "VAULT_PATH": "/path/to/your/vault",
        "PORT": "3001"
      }
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
smith-and-web
Star
-
Language
-
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