mcp-obsidian-via-rest
Verified Safeby OleksandrKucherenko
Overview
An MCP server that enables AI assistants to read, search, and interact with Obsidian notes via its Local REST API, supporting multiple network transports and self-healing connections.
Installation
bun run src/index.tsEnvironment Variables
- API_KEY
- API_HOST
- API_PORT
- API_URLS
- MCP_TRANSPORTS
- MCP_HTTP_PORT
- MCP_HTTP_HOST
- MCP_HTTP_PATH
- MCP_HTTP_TOKEN
- API_TEST_TIMEOUT
- API_RETRY_INTERVAL
- DEBUG
- NODE_ENV
Security Notes
The Obsidian API client uses `rejectUnauthorized: false` for HTTPS connections, which is a significant security risk in general but might be a practical necessity for local, self-signed Obsidian REST APIs. The HTTP transport defaults to binding on `0.0.0.0` (all interfaces), requiring external firewall configuration (as advised in documentation) to prevent unauthorized access. Test secrets (API keys, VNC passwords) are present in test-specific Docker Compose files, which is acceptable for non-production code. Authentication for the HTTP transport is implemented via Bearer tokens, which is a good practice when enabled.
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.