MCP Obsidian Docker logo

MCP Obsidian Docker

by kmackett

This is a containerized version of MCP Obsidian, a server that interacts with Obsidian via the Local REST API community plugin. It allows you to easily run MCP Obsidian within a Docker container.

View on GitHub

Last updated: N/A

What is MCP Obsidian Docker?

MCP Obsidian Docker is a Docker image that packages the MCP Obsidian server, which interacts with Obsidian through the Local REST API plugin. It provides a convenient way to run MCP Obsidian in a containerized environment.

How to use MCP Obsidian Docker?

  1. Clone the repository. 2. Configure the API key from the Obsidian Local REST API plugin in the .env file. 3. Build and start the container using docker-compose up -d. 4. Access the server at port 27124 (or the configured port).

Key features of MCP Obsidian Docker

  • Containerized deployment

  • Simplified setup

  • Environment variable configuration

  • Logging support

  • Easy API key management

Use cases of MCP Obsidian Docker

  • Automating tasks in Obsidian

  • Integrating Obsidian with other applications

  • Running MCP Obsidian on different platforms

  • Creating custom workflows with Obsidian

  • Accessing Obsidian data programmatically

FAQ from MCP Obsidian Docker

How do I get my Obsidian API key?

Open Obsidian, go to Settings -> Community Plugins -> Local REST API -> Settings. The API key will be displayed there.

Why am I getting an authentication error?

Double-check that the API key in your .env file matches the one in your Obsidian Local REST API plugin settings. Also, ensure the Obsidian app is running.

What if port 27124 is already in use?

You can modify the port mapping in the docker-compose.yml file to use a different port.

Where are the logs stored?

Logs are stored in the ./logs directory, which is mounted as a volume in the container.

How do I update the API key?

Generate a new key in Obsidian, update your .env file with the new key, and restart the container using docker-compose restart.