obsidian-mcp-server

The server demonstrates strong security practices. It includes robust path validation to prevent traversal attacks and ensures symlink targets are within allowed directories. REST API commands are limited to an explicit allowlist. API keys are discovered from Obsidian plugin configuration, cached in memory, and not serialized to disk. Rate limiting is implemented globally, per-vault, and per-operation to prevent abuse. File locking is used to ensure data integrity during concurrent access. Auto-configuration logic is designed to add safe parent paths (under user home directory) to allowed locations, avoiding system directories. The primary communication channel is stdio, limiting external network attack surface directly from this server process.