obsidian-mcp
Verified Safeby igorilic
Overview
Integrate AI assistants with Obsidian vaults to manage notes, track tasks, and facilitate knowledge discovery through a Model Context Protocol (MCP) server.
Installation
OBSIDIAN_VAULT_PATH=/path/to/your/obsidian/vault node dist/index.jsEnvironment Variables
- OBSIDIAN_VAULT_PATH
- MCP_TRANSPORT
- MCP_HTTP_PORT
Security Notes
The server primarily interacts with the local file system within the configured 'OBSIDIAN_VAULT_PATH'. It uses `path.join` and `path.relative` to construct file paths, which helps mitigate directory traversal attacks within the vault. There are no direct uses of `eval` or obvious obfuscation. Network risks are present if the HTTP server (default port 3000, mapped to 9111 by Docker) is exposed to untrusted networks without proper access controls. The critical security aspect is ensuring the `OBSIDIAN_VAULT_PATH` environment variable is set to a specific, trusted Obsidian vault directory and not a broad system path (e.g., `/`) which could allow the AI to read/write arbitrary files outside the intended scope.
Similar Servers
mcp-obsidian
Provides a secure, universal AI bridge for Obsidian vaults, enabling MCP-compatible AI assistants to read, write, and manage notes.
obsidian-mcp-plugin
This plugin connects your Obsidian vault to AI assistants through MCP (Model Context Protocol), enabling them to understand and navigate your notes as a connected knowledge graph.
mcp-obsidian
Enables LLMs (like Claude) to programmatically interact with an Obsidian vault through the Local REST API plugin.
obsidian-mcp-server
Provides an OpenAI-compatible local Model Context Protocol (MCP) server within Obsidian, enabling external AI assistants and tools to semantically search the vault and perform file system operations.