Obsidian MCP Lite

Created By
yokarilighta year ago
A TypeScript-based MCP server for Obsidian, providing a simple interface to interact with Obsidian vaults.
Overview

What is Obsidian MCP Lite?

Obsidian MCP Lite is a TypeScript-based MCP server designed for Obsidian, providing a simple interface to interact with Obsidian vaults.

How to use Obsidian MCP Lite?

To use Obsidian MCP Lite, install the necessary dependencies, build the server, and configure it with your Obsidian API key and host. You can then run the server to interact with your Obsidian vaults.

Key features of Obsidian MCP Lite?

  • List files in vault
  • List files in directory
  • Get file contents
  • Search specific texts from files
  • Patch content
  • Append content
  • Delete files

Use cases of Obsidian MCP Lite?

  1. Managing files within an Obsidian vault.
  2. Automating content updates in Obsidian.
  3. Integrating Obsidian with other applications via the MCP protocol.

FAQ from Obsidian MCP Lite?

  • What are the prerequisites for using Obsidian MCP Lite?

You need Node.js >= 18.16.0, Obsidian with the Local REST API plugin installed, and an Obsidian API key.

  • How do I set up Obsidian MCP Lite?

Follow the setup instructions to install dependencies, build the server, and configure your API key and host.

  • Can I use Obsidian MCP Lite with other tools?

Yes! You can integrate it with other applications that support the MCP protocol.

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