MCP server for Obsidian (TypeScript + Bun)

Created By
fazer-aia year ago
MCP server for Obsidian (TypeScript + Bun)
Overview

What is MCP Obsidian?

MCP Obsidian is a Model-Context-Protocol (MCP) server that allows Claude or any MCP-compatible LLM to interact with your Obsidian vault through a Local REST API.

How to use MCP Obsidian?

To use MCP Obsidian, set up the server with your Obsidian API key and run it using bun. You can then send commands to interact with your notes and vault.

Key features of MCP Obsidian?

  • Interact with Obsidian notes via a REST API.
  • Execute various commands such as retrieving, updating, and deleting notes.
  • Supports both active and periodic notes management.

Use cases of MCP Obsidian?

  1. Summarizing notes from meetings.
  2. Searching for specific content across your vault.
  3. Automating note-taking and content management in Obsidian.

FAQ from MCP Obsidian?

  • Can MCP Obsidian work with any LLM?

Yes! It is designed to work with any MCP-compatible LLM.

  • Is there a specific setup required?

You need to provide your Obsidian API key and configure the server accordingly.

  • What programming language is MCP Obsidian written in?

MCP Obsidian is written in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
fazer-ai
Star
11
Language
TypeScript
License
MIT 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