Skip to main content
Glama
JujiuYey

Obsidian MCP Server

by JujiuYey

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OBSIDIAN_VAULT_PATHYesAbsolute path to your Obsidian vault

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_noteA

Read the content of a specific note

list_notesB

List all notes in the vault

create_noteC

Create a new note

update_noteB

Update the content or metadata of a note

delete_noteC

Delete a note

search_notesB

Search for notes using full-text search

search_by_tagC

Find notes that have a specific tag

list_tagsA

List all tags in the vault

list_foldersB

List all folders in the vault

create_folderC

Create a new folder

delete_folderB

Delete an empty folder

get_tag_notesB

Get all notes that contain a specific tag

add_tagB

Add a tag to a note

remove_tagB

Remove a tag from a note

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
notesList all notes in the Obsidian vault

TDQS

B3.2/5.0

Scored across 14 tools

Disambiguation2/5

get_tag_notes and search_by_tag both retrieve notes by tag, making them functionally identical and confusingly overlapping. Other tools are distinct, but this duplication creates significant ambiguity.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (read_note, create_note, list_tags). Minor deviations like search_by_tag (verb_preposition_noun) and get_tag_notes (slightly awkward compound noun) break the pattern but are still readable.

Tool Count5/5

With 14 tools covering notes, tags, folders, and search, the count is well-scoped for an Obsidian note management server. Each functional area has appropriate coverage without bloat.

Completeness4/5

Core CRUD for notes, tag management, folder operations, and full-text search are all present. Minor gaps like moving/renaming notes exist, but agents can accomplish most workflows using the current surface.

Maintenance

ActivityInactive
ResponsivenessNo issues