# obsidian-claude-code-mcp

> Obsidian plugin that lets Claude Code and Claude Desktop read and edit your vault

- Repository: https://github.com/iansinnott/obsidian-claude-code-mcp
- Category: Agent skills & plugins
- Stars: 355 · Forks: 54 · Language: TypeScript · License: 0BSD
- Experience: Some experience
- Page: https://ir.adyog.com/repos/iansinnott/obsidian-claude-code-mcp/

Your notes live in an Obsidian vault, but AI tools usually can't see them. This plugin starts a Model Context Protocol (MCP) server inside Obsidian. MCP is a standard way for AI clients to call tools, so the client can ask the plugin to open, create or change files.

It speaks two transports. Claude Code connects over WebSocket and finds your vault on its own through the /ide command. Claude Desktop and other clients connect over HTTP with SSE, on port 22360 by default. Claude Desktop needs the mcp-remote bridge, because it doesn't talk to HTTP servers directly.

The HTTP side deliberately uses the older 2024-11-05 HTTP with SSE spec, because the README says current clients don't yet support the newer Streamable HTTP. Tools are split into shared, IDE-only and MCP-only groups, and the README explains how to add your own.

## What it does

- **Two ways to connect**: WebSocket for Claude Code and HTTP/SSE for Claude Desktop and other MCP clients. Both can be connected at the same time.
- **File tools**: Shared tools let a client view, create, insert into and string-replace vault files. There is also an obsidian_api tool for reaching the Obsidian API.
- **Workspace context**: Clients can ask for the currently active file and the list of files in the vault.
- **Auto-discovery for Claude Code**: Run claude, use /ide and choose Obsidian. Claude Code finds the vault through lock files in its config directory.
- **Configurable ports**: You can change the HTTP port in settings so several vaults can run side by side. The plugin detects port conflicts.

## What you could build

- Ask Claude Code to summarize or reorganize notes in your vault from the terminal.
- Ask Claude Desktop what files are in your vault and have it draft new notes.
- Run several vaults at once, each on its own port, with an AI client attached to each.
- Add a custom tool to the plugin so MCP clients can do something specific to your vault.
- Point any MCP client that supports HTTP with SSE at your notes.

## Who it's for

Obsidian users who already use Claude Code or Claude Desktop; for Claude Desktop you need Node.js and to be comfortable editing a JSON config file.

## Get started

Install and enable the plugin in Obsidian. Then run claude in a terminal, use /ide and choose Obsidian. For Claude Desktop, add the mcp-remote entry from the README to its config file and restart it.

```
claude
```

Tags: obsidian, mcp, claude-code, notes, plugin