obsidian-mcp-tools and Obsidian-MCP

These are complements designed for different integration patterns: one provides semantic search and templating within existing MCP clients, while the other enables bidirectional sync specifically between Claude Code and Obsidian, allowing users to leverage both capabilities together depending on their workflow needs.

obsidian-mcp-tools
42
Emerging
Obsidian-MCP
34
Emerging
Maintenance 2/25
Adoption 10/25
Maturity 9/25
Community 21/25
Maintenance 10/25
Adoption 3/25
Maturity 9/25
Community 12/25
Stars: 637
Forks: 92
Downloads: —
Commits (30d): 0
Language: TypeScript
License: MIT
Stars: 3
Forks: 1
Downloads: —
Commits (30d): 0
Language: JavaScript
License: MIT
Stale 6m No Package No Dependents
No Package No Dependents

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.

About Obsidian-MCP

AdrianV101/Obsidian-MCP

MCP server for bidirectional knowledge flow between Claude Code and Obsidian vaults

Related comparisons

obsidian-mcp-tools and obsidian-mcp-server obsidian-mcp-tools and mcp-obsidian obsidian-mcp-tools and obsidian-mcp-server obsidian-mcp-tools and obsidian-mcp-server obsidian-mcp-tools and flywheel-memory obsidian-mcp-tools and obsidian-mcp-server

Scores updated daily from GitHub, PyPI, and npm data. How scores work