Obsidian笔记库MCP服务器

Obsidian Vault MCP Server

A Model Context Protocol (MCP) server that provides full programmatic access to an Obsidian vault through the Local REST API plugin. Runs as a Docker container and connects to Claude Desktop via stdio transport.

Tools (35)

Prerequisites

Obsidian Setup

1. Install the Local REST API plugin:
   • Obsidian Plugin Page
   • GitHub Repository
   • API Documentation
2. Enable the plugin in Settings > Community Plugins
3. Go to Settings > Local REST API and copy the API Key
4. Note the HTTPS port (default: 27124)

Docker Setup

• Docker Desktop installed and running

Build

docker build -t obsidian-mcp-server:latest .

Connect to Claude Desktop

Add the following to your Claude Desktop config file:

{
  "mcpServers": {
    "obsidian": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "OBSIDIAN_API_KEY=your-api-key-here",
        "-e", "OBSIDIAN_API_URL=https://host.docker.internal:27124",
        "--add-host=host.docker.internal:host-gateway",
        "obsidian-mcp-server:latest"
      ]
    }
  }
}

Replace your-api-key-here with the API key from the Obsidian plugin settings.

Restart Claude Desktop after saving.

Local Testing (without Docker)

export OBSIDIAN_API_KEY="your-api-key-here"
export OBSIDIAN_API_URL="https://127.0.0.1:27124"

pip install -r requirements.txt
python obsidian_server.py

# Test MCP handshake
echo '{"jsonrpc":"2.0","method":"tools/list","id":1}' | python obsidian_server.py

Environment Variables

Usage Examples

In Claude Desktop, you can ask:

• "Read my note at Daily Notes/2026-03-30.md"
• "Create a new note called Ideas/Project Alpha.md with brainstorming content"
• "Append today's meeting notes to my daily note"
• "Search my vault for all notes mentioning 'Docker'"
• "List all files in my Projects folder"
• "What's currently open in Obsidian?"
• "Show me all my tags"
• "Get today's daily note with metadata"
• "Run a Dataview query to list all notes tagged #project"
• "Set the frontmatter field 'status' to 'complete' on my project note"
• "Open my weekly note in a new pane"

File Path Conventions

Architecture

Claude Desktop  ->  MCP (stdio)  ->  Docker Container  ->  HTTPS  ->  Obsidian Local REST API  ->  Vault

The container reaches the host machine through host.docker.internal. The Local REST API normally uses a self-signed certificate, so certificate verification defaults to off. That default is only appropriate when the API stays on the same machine through 127.0.0.1 or host.docker.internal.

Set OBSIDIAN_TLS_VERIFY=true when the API uses a certificate trusted by the container. Do not expose the Local REST API port to the public internet.

Tests

python -m unittest discover -s tests -v

Troubleshooting

Container Exits Immediately

This is normal when launched manually without stdin attached. Claude Desktop provides stdin via the stdio transport.

Connection Issues

• Verify the Local REST API plugin is enabled in Obsidian
• Test the API directly: curl -k https://127.0.0.1:27124/
• Ensure Docker Desktop is running

Authentication Errors

• Verify the API key matches what the plugin shows in Obsidian settings
• Check the container logs for OBSIDIAN_API_KEY not set warnings

Tools Not Appearing in Claude Desktop

• Verify the image is built: docker images | grep obsidian
• Check claude_desktop_config.json syntax is valid JSON
• Restart Claude Desktop completely (quit and reopen)

Security

• API key passed via environment variable, never hardcoded in source
• Container runs as non-root user (mcpuser, UID 1000)
• Keep the Local REST API bound to the local machine
• Certificate verification can be enabled with OBSIDIAN_TLS_VERIFY=true
• Vault files remain on the host filesystem
• Lock down config files: chmod 600 on any file containing the API key