How do I get my Obsidian API key?
Open Obsidian, go to Settings → Community Plugins, find “Local REST API,” click its settings gear, and copy the “API Key” field.
@kmackett
Basic information
Dockerized version of MCP Obsidian server for Obsidian Local REST API integration
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
MCP Obsidian Docker is a containerized version of the MCP Obsidian server that interacts with Obsidian via the Local REST API community plugin. It requires Docker, Docker Compose, and an Obsidian vault with the Local REST API plugin installed and an API key.
Clone the repository, configure the OBSIDIAN_API_KEY in a .env file, then build and start the container with docker-compose up -d. The server will be available on port 27124. Verify the container with docker-compose ps and inspect logs with docker-compose logs -f.
.env file./logs directorydocker-compose restartOpen Obsidian, go to Settings → Community Plugins, find “Local REST API,” click its settings gear, and copy the “API Key” field.
Copy `.env.example` to `.env`, then edit the file and replace `your_api_key_here` with your actual API key.
The MCP Obsidian server is available at port 27124 by default. If there is a port conflict, modify the port mapping in `docker-compose.yml`.
Run `docker-compose ps` to see if the container is running, and `docker-compose logs -f` to view logs for authentication or connection errors.
Generate a new key in Obsidian, update the `OBSIDIAN_API_KEY` in your `.env` file, and run `docker-compose restart`.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab

The official Semantic-UI-React integration

Orcha is a unified context layer for AI tools and agents. It stores and indexes and exposes organizational, team, or individual knowledge. Files, structured databases, and connected sources live in one workspace, and age
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.
Project context your AI can query through MCP — with source evidence.
Comments