OBSIDIAN-MCP-SERVER

Created By
zerogon1203a year ago
Overview

What is OBSIDIAN-MCP-SERVER?

OBSIDIAN-MCP-SERVER is a Python-based Stdio server that integrates with LLM Agents to provide functionalities related to Obsidian, a popular note-taking application. It allows users to manage their Obsidian vaults and files through a set of API calls.

How to use OBSIDIAN-MCP-SERVER?

To use the server, clone the repository, set up a virtual environment, install dependencies, and configure the environment variables. Then, run the server and interact with it using JSON-RPC API calls.

Key features of OBSIDIAN-MCP-SERVER?

  • Vault management: Create, delete, list, and configure vaults.
  • File management: List, create, modify, and delete files within vaults.
  • Error handling: Provides detailed error codes for troubleshooting.

Use cases of OBSIDIAN-MCP-SERVER?

  1. Automating the creation and management of Obsidian vaults.
  2. Integrating Obsidian functionalities into other applications via API.
  3. Streamlining note-taking workflows for users of Obsidian.

FAQ from OBSIDIAN-MCP-SERVER?

  • What programming language is used for OBSIDIAN-MCP-SERVER?

The server is built using Python.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • How can I report issues or contribute to the project?

You can report issues or contribute by visiting the project's GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zerogon1203
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year 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.

16 hours ago
Voyei

6 hours ago