What problem does it solve? Setting up Obsidian with the Local REST API plugin and wiring it into Claude Code as MCP servers involves many failure-prone steps: resolving vault paths, installing Obsidian per-OS, enabling community plugins, reading API keys, avoiding port collisions, and registering one MCP server per vault. This Skill codifies that entire procedure so the bridge works end to end. ## Core Features & Use Cases - Vault discovery and diagnosis: Scan every vault on the machine via vault_ops.py scan and diagnose, including vaults the plugin config has never heard of. - Guided installation: OS-specific Obsidian install paths (winget, Homebrew, Flatpak, AppImage) plus the manual Local REST API community plugin prerequisite. - MCP registration and repair: Register one obsidian-<name> MCP server per vault against its HTTP port, fix port collisions, reload stale Obsidian windows, and re-register after key rotation. - Use Case: A user says "set up Obsidian" or reports that mcp__obsidian__* tools stopped working; the Skill walks through scan, plugin enablement, registration, config writing, and a final diagnose verification. ## Quick Start Ask the assistant to set up Obsidian and configure the vault bridge, or to diagnose why the obsidian MCP tools are not connecting.
