richardk/iso27diy-corp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
iso27diy-corp/Corpus/Various/LLMs and Vibe Coding/MCP server for Obsidian Vault.md

4.3 KiB
Raw Blame History

tags:

  • llm
  • mcp
  • obsidian

Perplexity, 13 juni 2025

Prompt: `is there an MCP server that is particularly apt to interacting with my Obsidian vault? One that can work with the YAML metadata and internal links

Several MCP (Model Context Protocol) servers are specifically designed to interact with Obsidian vaults, supporting advanced features like YAML frontmatter (metadata) handling and internal link management.

Recommended MCP Servers for Obsidian

1. cyanheads/obsidian-mcp-server

  • YAML Metadata Support: This server offers robust property management, including YAML frontmatter parsing, intelligent merging, and custom field support. This means it can read, modify, and manage metadata fields in your notes seamlessly123.

  • Internal Link Handling: It supports comprehensive search capabilities, including full-text search, glob patterns, and frontmatter field queries. These features are well-suited for navigating and managing internal links within your vault123.

  • Security & Performance: Includes API key authentication, rate limiting, and SSL options for secure and efficient operation123.

  • Requirements: Needs the Obsidian Local REST API plugin enabled and Node.js installed13.

2. natestrong/obsidian-mcp

  • YAML and Tag Management: This server provides tools for reading, creating, searching, and managing notes, with explicit support for tag management in frontmatter (YAML)4.

  • Link Analysis: Offers note insights, including link analysis, which helps in understanding and traversing internal links in your vault4.

  • Smart Search: Allows searching by content, tags, or modification date, making it apt for metadata-driven workflows4.

  • Requirements: Requires the Local REST API plugin, Python 3.10+, and optionally Node.js for inspection tools4.

3. jacksteamdev/obsidian-tools

  • Semantic Search & Templates: Enables semantic searches and template execution, working with your vault’s structure and metadata5.

  • Automated Setup: Installation is streamlined via the plugin’s settings, making it convenient for users who prefer minimal manual configuration5.

  • Security: Publishes binaries with cryptographic provenance for added trust5.

Features Comparison Table

Server Name YAML Metadata Support Internal Link Handling Search/Query Features Requirements
cyanheads/obsidian-mcp-server Yes Yes Full-text, glob, frontmatter Node.js, Local REST API plugin
natestrong/obsidian-mcp Yes Yes Content, tags, link analysis Python 3.10+, Local REST API plugin
jacksteamdev/obsidian-tools Yes Yes Semantic, template-based Plugin install, Local REST API

Key Points

  • All these servers require the Obsidian Local REST API plugin to enable external access to your vault1243.
  • They provide comprehensive support for YAML metadata and internal links, making them well-suited for advanced Obsidian workflows.
  • Security features such as API key authentication and rate limiting are standard.

Conclusion:

The cyanheads/obsidian-mcp-server is particularly robust for YAML metadata and internal link management, but both natestrong/obsidian-mcp and jacksteamdev/obsidian-tools are also strong choices, depending on your environment and preferred setup style12543.