obsidian-devtools

Inspect and automate Obsidian app state via Chrome DevTools Protocol.

7|3|Updated Jan 15, 2026

Search Tags:#automation #debugging #obsidian #devtools #chrome-devtools #dom-inspection #plugin-debugging

Ready to run

npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-devtools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian-devtools
Source: https://github.com/Zpankz/mcp-skillset/tree/main/obsidian-devtools
Command: npx skills add https://github.com/Zpankz/mcp-skillset --skill obsidian-devtools

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inspecting and debugging the Obsidian application state can be tedious without a dedicated interface. This Skill provides a streamlined way to access and manipulate Obsidian internals via the Chrome DevTools Protocol, reducing debugging time and enabling automation of common workflows.

Core Features & Use Cases

Execute JavaScript in the Obsidian context to query vault data, plugins, and UI state.
Inspect the DOM and UI state to understand rendering and interactions for plugins and themes.
Read console logs to diagnose plugin failures and runtime errors.
Use cases include debugging plugins, automating repetitive workflows, and validating state transitions during development.

Quick Start

Start the obsidian-devtools server and attach to Obsidian with remote debugging enabled to begin inspecting the app.

Frequently Asked Questions about obsidian-devtools

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

FAQPage Schema

How do I debug Obsidian plugins using Chrome DevTools Protocol?▼

Obsidian debugging with Chrome DevTools Protocol allows you to execute JavaScript to query vault data, inspect DOM elements, and read console logs to diagnose plugin failures and runtime errors.

Can I automate repetitive workflows in Obsidian through remote debugging?▼

Yes, automating Obsidian workflows via remote debugging allows you to execute JavaScript to manipulate app internals, access vault data, and automate repetitive interactions across workflows.

Does Obsidian support DOM inspection for monitoring UI state during theme development?▼

Yes, inspecting Obsidian DOM and UI state via Chrome DevTools Protocol enables you to understand rendering interactions, monitor UI state, and validate state transitions during plugin and theme development.

What is the best way to access Obsidian app state and vault data programmatically?▼

Accessing Obsidian app state programmatically is best achieved by attaching via Chrome DevTools Protocol to execute JavaScript, query vault data, inspect plugins, and monitor UI state across workflows.

How do I read console logs in Obsidian to diagnose runtime errors?▼

To read Obsidian console logs and diagnose runtime errors, attach to the application via the Chrome DevTools Protocol to capture console output, inspect DOM, and execute JavaScript for debugging plugins.

Do I need to enable remote debugging to inspect Obsidian internals?▼

Yes, enabling remote debugging is required to attach the DevTools server to Obsidian, providing the interface to inspect app internals, execute JavaScript, read console logs, and automate workflows.