obsidian-developer

Inspect and automate Obsidian vaults via the obsidian-devtools MCP server.

7|3|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-developer
Source: https://github.com/Zpankz/mcp-skillset/tree/main/obsidian-developer
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers and power users automate and debug Obsidian workflows by exposing a programmable MCP server to inspect UI, query internal APIs, and orchestrate automated tasks across vaults.

Core Features & Use Cases

  • Live exploration of Obsidian APIs via obsidian-devtools, including vault, workspace, and plugins (with frontmatter and canvas support)
  • Create canvases and automate workflows across notes using patterns and the SDK
  • Use cases include building automated dashboards from vault metadata, batch frontmatter updates, and scripted inspections for plugin development

Quick Start

Connect Obsidian with obsidian_launch_debug and begin exploring APIs with obsidian_discover_api, then run code samples with obsidian_eval and leverage patterns/ for common tasks.

Frequently Asked Questions about obsidian-developer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Obsidian workflows using internal APIs and frontmatter?

You can automate Obsidian workflows by connecting through the obsidian-devtools MCP server, discovering internal APIs with obsidian_discover_api, and executing scripts via obsidian_eval for batch frontmatter updates and vault metadata operations.

What is the obsidian-devtools MCP server used for in plugin development?

The obsidian-devtools MCP server exposes Obsidian internal APIs for live exploration, UI inspection, and scripted debugging, enabling developers to query vault, workspace, and plugin APIs during plugin development.

Can I create Obsidian canvases programmatically through scripting?

Yes, Obsidian canvas automation is supported through the devtools MCP server, allowing you to create canvases and automate workflows across notes using documented patterns and the SDK for repeatable scripting tasks.

How do I inspect Obsidian internal APIs for debugging and UI exploration?

Obsidian API inspection starts by launching debug mode with obsidian_launch_debug, then using obsidian_discover_api to explore vault, workspace, and plugin APIs, followed by running code samples through obsidian_eval for live debugging.

Does Obsidian automation with devtools MCP require CDP and a running vault?

Yes, Obsidian automation requires a running vault connected via obsidian_launch_debug, which enables runtime CDP execution to inspect UI, query APIs, and return safe values for scripting and debugging workflows.

What are the limitations of automating Obsidian with the devtools MCP server?

Obsidian devtools MCP automation is limited to environments supporting CDP execution and requires a running vault instance, making it suited for development and scripting workflows rather than headless or serverless vault processing.