Skip to main content
Glama
Obsidian MCP Server

Obsidian MCP Server

by CtrlAltAdapt

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OBSIDIAN_API_KEYNoAPI key for authentication
OBSIDIAN_API_BASE_URLNoBase URL for Obsidian Local REST APIhttp://localhost:27123

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
}
logging
{}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
obsidian-get-noteC

Retrieve the content of a note by filename

obsidian-create-noteC

Create a new note with specified content

obsidian-update-noteC

Update an existing note with new content

obsidian-delete-noteC

Delete a note from the vault

obsidian-search-notesC

Search for notes containing specific text

obsidian-list-filesC

List all files and folders in the vault or a specific path

obsidian-get-vault-infoC

Get information about the Obsidian vault

obsidian-create-folderC

Create a new folder in the vault

obsidian-get-tagsB

Get all tags used in the vault

obsidian-pingB

Check if the Obsidian Local REST API server is accessible

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
obsidian-vault-filesComplete listing of all files and folders in the Obsidian vault
obsidian-vault-infoGeneral information about the Obsidian vault
obsidian-tagsAll tags used throughout the Obsidian vault

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct resource and action: note CRUD, search, file listing, folder creation, tag retrieval, vault info, and ping. The only potentially broad tools are get-vault-info and list-files, but their descriptions make their boundaries clear.

Naming Consistency4/5

All tools use a consistent obsidian- kebab-case prefix, and nearly all follow a verb_noun pattern. The main deviation is obsidian-ping, which has no noun, and get-vault-info adds a compound noun, but overall the convention is predictable.

Tool Count5/5

Ten tools is well-scoped for an Obsidian vault server, covering core note operations, search, listing, folders, tags, and connectivity. Each tool has a clear purpose without redundant operations.

Completeness4/5

The surface covers complete note CRUD plus search, listing, tags, folder creation, vault info, and health checking. Minor gaps exist around renaming/moving notes and full folder lifecycle (no delete or rename folder), but core workflows are workable.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues