Obsidian MCP Python

Created By
hellozhangrana year ago
obsidian-mcp-python, a very simple MCP Server demo that can help you to operate something about your obsidian md file
Overview

what is Obsidian Mcp Python?

Obsidian Mcp Python is a simple demo project designed to help users understand and operate an MCP (Multi-Channel Processing) server related to Obsidian markdown files.

how to use Obsidian Mcp Python?

To use this project, clone the repository to your local machine, install the required uv tool, and configure your MCP client with the provided JSON configuration.

key features of Obsidian Mcp Python?

  • Easy setup for an MCP server demo
  • Integration with Obsidian markdown files
  • Step-by-step tutorial for developers and users

use cases of Obsidian Mcp Python?

  1. Setting up a local MCP server for testing
  2. Learning how to operate MCP services with Obsidian files
  3. Experimenting with markdown file processing in a multi-channel environment

FAQ from Obsidian Mcp Python?

  • Is this project suitable for beginners?

Yes! The project includes a tutorial for beginners to get started easily.

  • What tools do I need to run this project?

You need to install the uv tool and have a compatible MCP client.

  • Can I use this project for production?

This is a demo project primarily for learning and experimentation.

Server Config

{
  "mcpServers": {
    "obsidian-mcp-python": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/of/your/project/file/obsidian-mcp-python",
        "run",
        "main.py"
      ],
      "env": {
        "OBSIDIAN_PATH": "/path/of/your/obsidian/vault"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hellozhangran
Star
-
Language
-
License
-
Category

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