Obsidian MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Obsidian MCP Server?

Obsidian MCP Server is a Model Context Protocol server designed for large language models (LLMs) to interact with Obsidian vaults, enabling AI assistants to manage knowledge bases effectively.

how to use Obsidian MCP Server?

To use the server, install Node.js, enable the Local REST API plugin in Obsidian, and clone the repository or install it via npm. Configure the MCP client settings with your API key and other parameters.

key features of Obsidian MCP Server?

  • Atomic file operations with validation and resource monitoring.
  • Full-text search capabilities with advanced querying options.
  • YAML frontmatter parsing and intelligent property management.
  • API key authentication with rate limiting and SSL options.

use cases of Obsidian MCP Server?

  1. Managing and searching through large collections of notes in Obsidian.
  2. Automating file operations and updates in an Obsidian vault.
  3. Integrating AI assistants to enhance knowledge management workflows.

FAQ from Obsidian MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol (MCP) allows AI models to interact with external tools and resources through a standardized interface.

  • Do I need to install any plugins?

Yes, you need to enable the Local REST API plugin in Obsidian to use this server.

  • Is there a limit on API requests?

Yes, the server includes rate limiting to manage the number of requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
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.

8 hours ago