Obsidian Claude Code

An Obsidian plugin that implements an MCP (Model Context Protocol) server to enable Claude Code integration with Obsidian vaults.

This plugin allows Claude Code and other MCP clients (like Claude Desktop) to interact with your Obsidian vault, providing AI-powered assistance with direct access to your notes and files.

- Dual Transport MCP Server: Supports both WebSocket (for Claude Code) and HTTP/SSE (for Claude Desktop)
- Auto-Discovery: Claude Code automatically finds and connects to your vault
- File Operations: Read and write vault files through MCP protocol
- Workspace Context: Provides current active file and vault structure to Claude
- Multiple Client Support: Connect both Claude Code and Claude Desktop simultaneously
- Configurable Ports: Avoid conflicts when running multiple vaults

This plugin serves as an MCP server that various Claude clients can connect to. Here's how to configure different clients:

Claude Desktop requires a special configuration to connect to the Obsidian MCP server because it does not directly support HTTP transports. We will usemcp-remote, a tool that creates a localstdiobridge to the server's HTTP endpoint.
-

Install and enablethis plugin in Obsidian.

Make sure you have Node.js installed, asnpx(which comes with Node.js) is used to run the bridge tool.

Locate your Claude Desktop config file:

- macOS:$HOME/Library/Application Support/Claude/claude_desktop_config.json
- Windows:%APPDATA%\Claude\claude_desktop_config.json

Add the Obsidian MCP serverto your config using themcp-remotecommand.npxwill automatically download and run it for you.

{ "mcpServers": { "obsidian": { "command": "npx", "args": ["mcp-remote", "http://localhost:22360/sse"], "env": {} } } }

Restart Claude Desktopafter making the configuration change.

Test the connectionby asking Claude about your vault: "What files are in my Obsidian vault?"

Other MCP Clients (with direct HTTP support)

If you are using an MCP client that directly supports the legacy "HTTP with SSE" transport, you can use a simpler configuration without themcp-remotebridge.

{ "mcpServers": { "obsidian": { "url": "http://localhost:22360/sse", "env": {} } } }

Claude Code automatically discovers and connects to Obsidian vaults through WebSocket.
- Install and enablethis plugin in Obsidian
- Run Claude Codein your terminal:claude
- Select your vaultusing the/idecommand
- Choose "Obsidian"from the IDE list
- Claude Code will automatically connect via WebSocket

Default Port: The plugin uses port22360by default to avoid conflicts with common development services.
- Go toObsidian Settings→Community Plugins→Claude Code→Settings
- Change the"HTTP Server Port"in the MCP Server Configuration section
- Update your Claude Desktop configto use the new port:

{ "mcpServers": { "obsidian": { "url": "http://localhost:22360/mcp", "env": {} } } }

NOTE: You can change the port in the settings.

Multiple Vaults: If you run multiple Obsidian vaults with this plugin, each vault needs a unique port. The plugin will automatically detect port conflicts and guide you to configure different ports.

[!IMPORTANT] This plugin intentionally uses an older MCP specification for HTTP transport. The latest"Streamable HTTP" protocol (2025-03-26)is not yet supported by most MCP clients, including Claude Code and Claude Desktop.

To ensure compatibility, we use the legacy"HTTP with SSE" protocol (2024-11-05). Adhering to the newest specification will lead to connection failures with current tools.

- Update yourmanifest.jsonwith your new version number, such as1.0.1, and the minimum Obsidian version required for your latest release.
- Update yourversions.jsonfile with"new-plugin-version": "minimum-obsidian-version"so older versions of Obsidian can download an older version of your plugin that's compatible.
- Create new GitHub release using your new version number as the "Tag version". Use the exact version number, don't include a prefixv. See here for an example:https://github.com/obsidianmd/obsidian-sample-plugin/releases
- Upload the filesmanifest.json,main.js,styles.cssas binary attachments. Note: The manifest.json file must be in two places, first the root path of your repository and also in the release.
- Publish the release.

Score CLAUDE.md/AGENTS.md, validate clarx-manifest.json, generate CI workflows, and pull repo scan findings into Cursor, Claude, or Grok.