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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago