obsidian-mcp-server and obsidian-mcp-tools
These are complements that address different integration patterns: one provides a general-purpose MCP server for vault access, while the other adds specialized features (semantic search, Templater integration) that could run on top of or alongside an MCP server to enhance Claude's Obsidian capabilities.
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 obsidian-mcp-tools
jacksteamdev/obsidian-mcp-tools
Add Obsidian integrations like semantic search and custom Templater prompts to Claude or any MCP client.
Implements a two-component architecture with a local MCP server binary (built with reproducible builds and SLSA provenance) that bridges Claude Desktop to Obsidian vaults through the Local REST API plugin. Beyond semantic search and templates, it provides vault access controls, encrypted communication, and secure credential storage. The monorepo uses Bun workspaces to coordinate the Obsidian plugin, MCP server, and shared type definitions.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work