obsidian-mcp-server and mcp-obsidian-advanced
Both tools are competing implementations of an Obsidian Knowledge-Management MCP (Model Context Protocol) server, designed to enable AI agents and development tools to interact with an Obsidian vault.
About obsidian-mcp-server
cyanheads/obsidian-mcp-server
Obsidian Knowledge-Management MCP (Model Context Protocol) server that enables AI agents and development tools to interact with an Obsidian vault. It provides a comprehensive suite of tools for reading, writing, searching, and managing notes, tags, and frontmatter, acting as a bridge to the Obsidian Local REST API plugin.
Implements a modular TypeScript architecture leveraging stdio transport for MCP communication with automatic reconnection, backed by an intelligent in-memory vault cache that provides fallback search functionality if the REST API becomes unavailable. Supports flexible file targeting (by path, active note, or periodic notes) and atomic frontmatter operations, with structured logging, Zod validation, and optional HTTP transport via Hono for alternative deployment scenarios.
About mcp-obsidian-advanced
ToKiDoO/mcp-obsidian-advanced
Advanced MCP server for interacting with Obsidian via the Local REST API community plugin. It empowers AI agents (like Claude) to deeply understand your vault's structure, links, and content—beyond basic read/write operations.
Leverages the obsidiantools library and NetworkX graph analysis to expose vault topology and bidirectional note relationships as structured data for LLM reasoning. Implements 20+ granular tools spanning file operations, full-text/JsonLogic search, command execution, and vault introspection—with granular tool filtering via `INCLUDE_TOOLS` environment variable. Integrates with Claude Desktop and any MCP-compatible client through the Obsidian Local REST API plugin, communicating over HTTP to a running Obsidian instance.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work