MCP Obsidian Docker MCP Server

Connect MCP Obsidian Docker to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Dockerized version of MCP Obsidian server for Obsidian Local REST API integration. The mcp obsidian docker mcp server is what makes that connection.

What the server does

This is a containerized version of MCP Obsidian, a server that interacts with Obsidian via the Local REST API community plugin.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: OBSIDIAN_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

1. Docker and Docker Compose installed 2. Obsidian with the Local REST API plugin installed and configured 3. API key from the Local REST API plugin

Where it fits

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by kmackett; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Obsidian Docker's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.