ObsidianFetch

Created By
soukoukia year ago
MCP servers focused on fetching and presenting information from Obsidian vaults.
Overview

What is ObsidianFetch?

ObsidianFetch is a specialized MCP server designed to efficiently retrieve information from Obsidian vaults, addressing common issues faced by existing servers.

How to use ObsidianFetch?

To use ObsidianFetch, install it via Ruby with the command gem install obsidian_fetch, and then run it by specifying the path to your Obsidian vault using obsidian_fetch /path/to/your/vault.

Key features of ObsidianFetch?

  • Simplified retrieval and loading of notes from Obsidian vaults.
  • Automatic removal of invalid characters in links when retrieving link information.
  • Display of links pointing to the opened file, enhancing navigation in network-style note tools.

Use cases of ObsidianFetch?

  1. Quickly accessing and loading notes from large Obsidian vaults.
  2. Enhancing the usability of Obsidian by improving link navigation.
  3. Supporting local GPU-based LLMs by streamlining note retrieval processes.

FAQ from ObsidianFetch?

  • What programming language is ObsidianFetch written in?

ObsidianFetch is written in Ruby.

  • Is ObsidianFetch open source?

Yes! ObsidianFetch is available under the MIT License.

  • How can I contribute to ObsidianFetch?

You can report bugs or submit pull requests on its GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
soukouki
Star
2
Language
Ruby
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours 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.

a day ago