Skip to main content
Glama
claude-obsidian

claude-obsidian

by harunzybk

claude-obsidian MCP

A Model Context Protocol (MCP) server that connects Claude Desktop to your Obsidian vault — making Obsidian the single source of truth for all your PM work: PRDs, processes, Jira notes, meeting notes, and ideas.


What This Enables

Once installed, you can talk to Claude naturally and it will automatically manage your Obsidian notes:

Say to Claude

What happens

"Create a PRD for the new onboarding flow"

Creates a structured PRD in PRDs/

"Log notes for PROJ-123, it's about payment timeout"

Creates Jira/PROJ-123.md with full context

"Create meeting notes for today's sprint planning"

Creates a structured meeting note in Meetings/

"Capture this thought: we should rethink the checkout UX"

Saves to Ideas/ with timestamp

"Document the deployment process"

Creates a process SOP in Processes/

"Search my notes for authentication"

Full-text search across your entire vault

"Show me my vault overview"

Lists all folders and note counts

"Set up my vault structure"

Creates all folders + index notes in one shot


Related MCP server: Obsidian Nexus

Prerequisites

1. Obsidian + Local REST API Plugin

  1. Open Obsidian

  2. Go to Settings → Community plugins → Browse

  3. Search for "Local REST API" and install it

  4. Enable it, then go to Settings → Local REST API

  5. Copy the API Key shown there — you'll need it in Step 3 below

  6. Leave Obsidian open while using Claude (the plugin serves on localhost:27124)

Note: Your vault is at /Users/harunzeybek/Documents

2. Node.js

Requires Node.js 18 or later. Check with:

node --version

Installation

Step 1 — Clone & Build

git clone https://github.com/harunzybk/claude-obsidian.git
cd claude-obsidian
npm install
npm run build

Step 2 — Note the full path to the built server

pwd
# e.g. /Users/harunzeybek/Repositories/claude-obsidian

The server binary is at: <that path>/dist/index.js

Step 3 — Configure Claude Desktop

Open your Claude Desktop config file:

open ~/Library/Application\ Support/Claude/claude_desktop_config.json

Add the following inside the "mcpServers" object (replace YOUR_API_KEY with the key from Step 1):

{
  "mcpServers": {
    "obsidian": {
      "command": "node",
      "args": ["/Users/harunzeybek/Repositories/claude-obsidian/dist/index.js"],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_API_KEY",
        "OBSIDIAN_VAULT_PATH": "/Users/harunzeybek/Documents",
        "OBSIDIAN_USE_HTTPS": "true"
      }
    }
  }
}

If the file doesn't exist yet, create it with the full content above.

Step 4 — Restart Claude Desktop

Quit and reopen Claude Desktop. You should see "obsidian" listed as a connected MCP server (look for the 🔌 icon or check Settings → Developer).

Step 5 — Initialize Your Vault Structure

In Claude Desktop, say:

"Set up my Obsidian vault structure"

Claude will create all folders and index notes automatically.


Available Tools

Note Operations

Tool

Description

create_note

Create a new note at any path

read_note

Read a note's full content

update_note

Replace a note's content

append_to_note

Add content to the end of a note

delete_note

Delete a note

list_notes

List files in a folder

Tool

Description

search_notes

Full-text search across the vault

search_by_tag

Find notes by Obsidian #tag

Vault Management

Tool

Description

list_folders

List folders

create_folder

Create a new folder

get_vault_overview

Top-level structure + note counts

PM Templates

Tool

Description

create_prd

Structured PRD with goals, requirements, success metrics

create_process_doc

SOP / process documentation

log_jira_note

Rich Jira ticket context notes

capture_thought

Quick idea / brain dump

create_meeting_note

Meeting notes with agenda + action items

create_project_note

Project overview and tracking

setup_vault_structure

Initialize all folders + index notes


Vault Folder Structure

Your Vault (Documents/)
├── Home.md               ← Start here — links to everything
├── PRDs/                 ← Product Requirements Documents
├── Processes/            ← SOPs and process documentation
├── Jira/                 ← Jira ticket context notes
├── Meetings/             ← Meeting notes (YYYY-MM-DD-title.md)
├── Ideas/                ← Quick thoughts and brain dumps
├── Projects/             ← Project tracking notes
└── Resources/            ← Reference materials

Troubleshooting

Claude says it can't connect to Obsidian

  • Make sure Obsidian is open

  • Check that "Local REST API" plugin is enabled in Obsidian

  • Verify the API key in your claude_desktop_config.json is correct

"Cannot find module" error

  • Run npm run build again in the project folder

  • Make sure the path in claude_desktop_config.json points to dist/index.js, not src/index.ts

HTTPS certificate error

  • Set "OBSIDIAN_USE_HTTPS": "false" in your config (HTTP mode)


Development

npm run dev      # Watch mode — recompiles on change
npm run build    # Production build
npm start        # Run the compiled server

License

MIT © harunzybk

Available Tools

18 tools
append_to_noteAppend to NoteA

Append text to the end of an existing note. Great for adding updates, new entries, or continuing a log.

Inputs: path (required), content (required).

capture_thoughtCapture ThoughtA

Quickly capture a thought, idea, or brain dump to the Ideas/ folder. Use this for fleeting ideas, shower thoughts, or anything that needs to be captured fast before it's lost. No structure required.

Inputs: title (required), content (required), tags, relatedTo.

create_folderCreate FolderA

Create a new folder in the Obsidian vault by writing a hidden .gitkeep placeholder. Obsidian creates folders on demand when files are written into them.

Inputs: folderPath (required).

create_meeting_noteCreate Meeting NoteA

Create a structured meeting note in the Meetings/ folder. Includes attendees, agenda, discussion notes, decisions made, and action items.

Inputs: title (required), date, notes, agenda, +5 more.

create_noteCreate NoteA

Create a new note in the Obsidian vault at the specified path. If the note already exists it will be overwritten. Use forward-slash separated paths like 'PRDs/my-feature.md'.

Inputs: path (required), content (required), overwrite.

create_prdCreate PRDA

Create a structured Product Requirements Document (PRD) in the PRDs/ folder. Fills in a rich template with problem statement, goals, user stories, requirements, success metrics, and open questions. Perfect for feature documentation.

Inputs: title (required), summary (required), goals, author, +8 more.

create_process_docCreate Process DocA

Create a process documentation or SOP (Standard Operating Procedure) note in the Processes/ folder. Includes steps, owners, tools, and edge cases.

Inputs: title (required), purpose (required), team, owner, +6 more.

create_project_noteCreate Project NoteA

Create a project overview and tracking note in the Projects/ folder. Acts as the single source of truth for a project — links to PRDs, Jira epics, meeting notes, and tracks milestones.

Inputs: name (required), description (required), team, owner, +7 more.

delete_noteDelete NoteA

Permanently delete a note from the Obsidian vault.

Inputs: path (required).

get_vault_overviewGet Vault OverviewA

Get a high-level overview of the vault structure — top-level folders and file counts. Use this to understand the current state of the knowledge base.

Inputs: no named parameters.

list_foldersList FoldersA

List all folders in the Obsidian vault or within a specific directory.

Inputs: parent.

list_notesList NotesB

List all files and folders in a given vault directory. Leave 'folder' empty to list the vault root.

Inputs: folder.

log_jira_noteLog Jira NoteA

Save structured notes for a Jira ticket to the Jira/ folder. Captures the ticket summary, context, decisions, blockers, and links. Great for keeping rich context alongside Jira's limited fields.

Inputs: summary (required), ticketKey (required), type, notes, +9 more.

read_noteRead NoteA

Read the full markdown content of a note from the Obsidian vault.

Inputs: path (required).

search_by_tagSearch by TagB

Find all notes that contain a specific Obsidian tag (e.g. #prd, #jira, #process). Do not include the # prefix — just the tag name.

Inputs: tag (required), limit.

search_notesSearch NotesA

Perform a full-text search across all notes in the Obsidian vault. Returns matching file paths with context snippets. Use this to find existing PRDs, processes, Jira notes, or any content.

Inputs: query (required), limit, contextLength.

setup_vault_structureSetup Vault StructureA

Initialize the recommended PM vault folder structure with index notes in each folder. Run this once to set up your Obsidian vault for PM work. Creates: PRDs/, Processes/, Jira/, Meetings/, Ideas/, Projects/, Resources/

Inputs: no named parameters.

update_noteUpdate NoteA

Replace the entire content of an existing note in the Obsidian vault.

Inputs: path (required), content (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with specialized create_* variants for different note types. However, some overlap exists between list_notes, list_folders, and get_vault_overview, which all provide structural information about the vault.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_note, list_folders, search_notes). Even multi-word tools like get_vault_overview and setup_vault_structure maintain the convention.

    Tool Count4/5

    At 18 tools, the server is slightly on the heavier side, but the count is justified by the broad domain of managing a knowledge vault with multiple specialized note templates. Each tool serves a distinct role in the workflow.

    Completeness4/5

    The tool surface covers full CRUD for notes, folder creation, search, and domain-specific templates for PRDs, processes, meetings, projects, Jira notes, and ideas. Minor gaps include lack of folder rename/delete and note move operations, but these can be worked around.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Desktop to Obsidian vaults to enable reading, writing, searching, and intelligent organization of markdown notes. It features pre-configured structures for personal and family data management through natural conversation.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude.ai to your local Obsidian vault for full CRUD access, search, and daily note creation via the Model Context Protocol.
      14
      MIT