obsidian-mcp-server and obsidian-http-mcp
These two projects are **competitors**, as they are both implementations of an MCP (Model Context Protocol) server for Obsidian vaults, offering similar functionality to expose vault data to AI agents and development tools.
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.
This project acts as a bridge, enabling external AI assistants and other software tools to interact directly with your Obsidian knowledge vault. It takes your Obsidian notes, tags, and frontmatter as input, allowing these tools to read, write, search, and manage your knowledge base. It's designed for developers and power users who want to integrate Obsidian into automated workflows or AI-powered applications.
About obsidian-http-mcp
NasAndNora/obsidian-http-mcp
First HTTP-native MCP server for Obsidian - Compatible with any MCP client (Claude Code, Codex, Gemini, etc.) without stdio bugs
This tool helps you manage your Obsidian notes directly using AI assistants like Claude Code, Codex, or Gemini, without encountering frustrating technical errors. It acts as a bridge, taking commands from your AI to perform actions like creating, editing, finding, or moving notes, and then showing you the results within your AI conversation. Knowledge workers, writers, researchers, or anyone who uses Obsidian for note-taking and wants to integrate AI for seamless vault management would use this.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work