obsidian-playwright-mcp
Provides tools for accessing and interacting with the Obsidian application via Chrome DevTools Protocol, allowing screenshots, executing JavaScript in the Obsidian context, capturing console logs, and automating UI actions for plugin debugging and testing.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
obsidian-playwright-mcp
MCP server that lets AI assistants "see" and interact with the Obsidian app itself — not just read vault files.
Why This Exists
Obsidian plugins are debugged by AI today by reading source files, but that's blind. This server connects to Obsidian's Electron process via Chrome DevTools Protocol (CDP), letting Claude/any agent:
Screenshot the app to see what's actually rendering
Execute JavaScript in the running app context to query plugin state, trigger commands, inspect the DOM
Capture console logs to see errors in real time
Automate UI actions for testing plugins or validating layouts
Perfect for debugging why a plugin isn't rendering, testing UI state changes, or verifying behavior end-to-end.
Related MCP server: Chrome DevTools MCP
Gotchas
Obsidian must launch with
--remote-debugging-port=8315— standard startup doesn't enable CDPSingle connection at a time — only one agent can connect per Obsidian instance
Console logs captured only after connect — startup logs are missed
Requires Node.js v18+ and Windows (Obsidian.exe path is hardcoded)
Quick Start
Launch Obsidian with debug port:
Start-Process "C:\Users\patri\AppData\Local\Programs\Obsidian\Obsidian.exe" -ArgumentList "--remote-debugging-port=8315"Configure MCP (
.claude/mcp_config.json):{ "mcpServers": { "obsidian-automation": { "command": "node", "args": ["C:/Projects/02-Dormant-or-Ideas/obsidian-playwright-mcp/obsidian-mcp-server.js"] } } }
Tools
Tool | Purpose |
| Establish CDP connection (run first) |
| Run JavaScript: |
| Capture current window state |
| Fetch console output (filter by type: |
| Get vault name, active file, window title |
| Close connection |
Example: Debug a Plugin
// Connect
connect_to_obsidian()
// Returns: { success: true, title: "Home - MyVault - Obsidian v1.x" }
// Is the plugin loaded?
execute_in_renderer({ code: `!!app.plugins.plugins['my-plugin']` })
// Returns: { success: true, result: true }
// What's in the console?
get_console_logs({ filter: "error", limit: 5 })
// Returns: { logs: [{ type: "error", text: "Plugin init failed: ..." }] }
// Screenshot the error state
take_screenshot({ filename: "error-state.png" })Tech Stack
Node.js + Playwright (CDP connectivity)
@modelcontextprotocol/sdk (MCP protocol)
Status: Dormant (Jan 2026). See SKILL.md for detailed examples.
Screenshots
TODO (Patrik): add screenshots here.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Live browser debugging for AI assistants — DOM, console, network via MCP.
Connect AI assistants to your GitHub-hosted Obsidian vault to seamlessly access, search, and analy…
Give AI agents a real cloud Chrome: open sessions, navigate, read pages, click, type and screenshot.
Connect AI assistants to your approved computer for files, commands, browser and desktop tasks.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, and screenshot capture through Chrome DevTools.262,562,190 npm3Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automation, debugging, performance analysis, network monitoring, and DOM interaction through Chrome DevTools Protocol.Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceEnables AI coding assistants to control and inspect a live Chrome browser for automated debugging, performance analysis, and web interaction. It leverages Puppeteer and Chrome DevTools to provide capabilities like network monitoring, console logging, and automated browser actions.-
- AlicenseNot gradedqualityDmaintenanceEnables AI-powered automation, debugging, and observability of Electron applications through Chrome DevTools Protocol integration, providing real-time UI interaction and inspection capabilities.94 npm27MIT