Claude Code IDE for Obsidian
Integrates with Obsidian to allow Claude Code to read selections, open files, show diffs, and run terminal commands within an Obsidian vault.
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.
Claude Code IDE for Obsidian
Connects the Claude Code CLI to Obsidian the same way the VS Code extension does: Claude can read your selection and open files, open files, show diffs you keep/reject, and run inside an embedded terminal.
Protocol is the WebSocket MCP variant reverse-engineered from the VS Code extension —
compatible with coder/claudecode.nvim.
Build
npm install
npm run build # -> main.js + styles.css
npm test # protocol self-check (no Obsidian needed)Install: copy main.js, styles.css, manifest.json into
<vault>/.obsidian/plugins/obsidian-claude-code-ide/, then enable it in
Settings → Community plugins.
Related MCP server: obsidian-mcp-server
Use
Enabling the plugin starts a WebSocket server on 127.0.0.1, writes
~/.claude/ide/<port>.lock, and is ready. Two ways to connect Claude:
Embedded terminal (auto-connect): ribbon icon → Claude Code terminal, or the command palette. Spawns
claudewith the env vars already set; it connects on its own.Passive mode (no native deps): in any terminal,
cdinto the vault and runclaude, then/ide→ pick Obsidian.
node-pty (embedded terminal only)
The terminal needs node-pty, a native module that must match Obsidian's Electron ABI.
It's an optional dependency — if it can't load, the terminal pane prints the passive-mode
steps instead and everything else still works.
To enable it, rebuild against Obsidian's Electron:
npx electron-rebuild -v <obsidian-electron-version> -m node_modules/node-ptyFind the Electron version in Obsidian via Help → Debug info. Copy the rebuilt
node_modules/node-pty next to main.js in the plugin folder.
Layout
File | Concern |
| WS server, JSON-RPC/MCP, auth, lock file (Obsidian-free, tested) |
| The 11 MCP tool handlers (Obsidian-free, tested) |
| Plugin lifecycle + Obsidian |
|
|
| xterm.js + node-pty terminal |
Not done
executeCode/getDiagnostics— no Obsidian equivalent (getDiagnosticsreturns[]).isDirtyis alwaysfalse(Obsidian autosaves; real dirty state isn't exposed).
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
Work on your own computers from Claude or ChatGPT: run commands, edit and search files.
Use your Mac, Windows or Linux computer from ChatGPT, Claude or Codex: files, commands, documents.
Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.
Read and write your Fresh Jots notes from Claude, Cursor, and any MCP client.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables Claude Code read/write access to an Obsidian vault, including creating, editing, searching, and browsing notes.81MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude.ai to your local Obsidian vault for full CRUD access, search, and daily note creation via the Model Context Protocol.14MIT
- AlicenseAqualityBmaintenanceEnables capturing Claude conversations as Obsidian notes and searching the vault from chat, using the Obsidian CLI.23102 npm2MIT
- AlicenseNot gradedqualityCmaintenanceConnects Obsidian to coding agents like Claude Code and Codex by exposing tools to access vault context (active file, selection, open editors, workspace folders), and includes a built-in terminal to run agents directly inside Obsidian.3MIT