Obsidian Model Context Protocol Tools
A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault.
에이전트 강화
게시자가 제공하는 설치 방식입니다. PlugMCP 엔드포인트가 아닙니다.
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault.
A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault. This server exposes a rich, read-only toolkit of obsidian_-prefixed MCP tools for working with vault metadata (tags, links, frontmatter), filenames, and more
This server exposes a rich, read-only toolkit of obsidian_-prefixed MCP tools for working with vault metadata (tags, links, frontmatter), filenames, and full-text content.
git clone https://github.com/dp-veritas/mcp-obsidian-tools.git
cd mcp-obsidian-tools
npm install
npm run build
This will compile the TypeScript code and create the dist/ directory with the executable files.
After building, you need to add this server to your MCP client's configuration. The configuration format varies by client, but generally follows this pattern:
Quick Start: See
example-mcp-config.jsonfor Cursor/VSCode format, orexample-claude-desktop-config.jsonfor Claude Desktop format.
Add an entry to your MCP client's configuration file (usually mcpServers or mcp.servers):
{
"mcpServers": {
"obsidian": {
"command": "node",
"args": ["/absolute/path/to/mcp-obsidian-tools/dist/index.js", "/path/to/your/vault"]
}
}
}
Important: Use absolute paths for both the server location and your vault path.
The vault path can be:
/Users/username/Documents/MyVault./my-vault (relative to current working directory)~/Documents/MyVaultAdd to your Cursor MCP settings file (location varies by OS):
{
"mcpServers": {
"obsidian": {
"command": "node",
"args": ["/Users/username/path/to/mcp-obsidian-tools/dist/index.js", "/Users/username/Documents/MyVault"]
}
}
}
Add to your User Settings JSON (Ctrl+Shift+P → Preferences: Open User Settings (JSON)) or create .vscode/mcp.json:
{
"mcp": {
"servers": {
"obsidian": {
"command": "node",
"args": ["/Users/username/path/to/mcp-obsidian-tools/dist/index.js", "/Users/username/Documents/MyVault"]
}
}
}
}
Add to Claude Desktop's MCP configuration file (location varies by OS). Claude Desktop configs can include a preferences section:
{
"preferences": {
"quickEntryShortcut": {
"accelerator": "Alt+Space"
}
},
"mcpServers": {
"obsidian": {
"command": "node",
"args": ["/Users/username/path/to/mcp-obsidian-tools/dist/index.js", "/Users/username/Documents/MyVault"]
}
}
}
Note: See
example-claude-desktop-config.jsonfor a complete Claude Desktop example. Seeexample-mcp-config.jsonfor Cursor/VSCode format.
If you prefer to install globally so you can use it from anywhere:
npm install -g .
Then configure with:
{
"mcpServers": {
"obsidian": {
"command": "mcp-obsidian-tools",
"args": ["/path/to/your/vault"]
}
}
}
Once configured, the following MCP tools will be available:
obsidian_search_notes: Search for notes by filename (case-insensitive, supports simple regex / wildcards). Returns relative paths of matching .md files.
obsidian_read_notes: Read the contents of multiple notes by relative path. Each note is returned with its path header; failures are reported per-note. Set headersOnly: true to return only headings (lines starting with #) for quick title/structure extraction.
obsidian_list_tags: Scan all Markdown files and list all tags (frontmatter tags and inline #tags) with occurrence counts. Optional startsWith filter.
obsidian_notes_by_tag: Given one or more tag names, return all note paths that contain those tags (frontmatter or inline). Optional match of "any" or "all".
obsidian_get_frontmatter: Return parsed YAML frontmatter as JSON for a given note path (e.g. author, tags, created).
obsidian_backlinks: Given a target note path or name, list all notes that link to it, via Obsidian wikilinks ([[Note Name]]) or markdown links ([Display](path)).
obsidian_search_content: Full-text search inside note contents (not filenames). Supports simple wildcard patterns; can return just paths or snippets with context.
obsidian_query: Natural-language query over the vault, with optional date filtering based on frontmatter dates (e.g. created: YYYY-MM-DDTHH:MM:SS).
obsidian_count_files: Count the total number of markdown files in the vault or a specific subfolder. Supports fuzzy folder lookup - if a folder like "History 101" isn't at the root, automatically searches the entire vault for matching folders. Returns total count and breakdown by immediate subfolders. Set includeNames: true to also get a list of file names (up to 100). Useful for understanding vault size, organization, and listing files in a folder.
All tools are read-only and are strictly confined to the vault directory (and its real/symlinked path) via path validation.
Which of my entries concern the overton window?Show interview candidate notes I've logged from the last 6 monthsAny daily notes about board-related topics this month?npm run build and the dist/ directory existsnode --version)dist/index.js file is executable (chmod +x dist/index.js)Tool-calling quality depends on your LLM. Some models (especially smaller ones) may struggle to format correct parameters for MCP tools, particularly with:
If you encounter unexpected errors, try:
Note: Complex cross-referencing queries (e.g., "How does X relate to Y across my vault?") may require 10-30+ tool calls as the model iterates through different search strategies. This is normal behavior, not a failure.
To watch for changes during development:
npm run watch
See LICENSE file for details.
A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault. This server
개요
A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault. This server exposes a rich, read-only toolkit of obsidian_-prefixed MCP tools for working with vault metadata (tags, links, frontmatter), filenames, and more
도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
MCP Obsidian Tools은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-10-28. A Model Context Protocol (MCP) server that allows MCP clients (Cursor, VSCode, Claude Desktop, etc.) to read and search any directory containing Markdown notes, such as an Obsidian vault. This server exposes a rich, read-only toolkit of obsidian_-prefixed MCP tools for working with vault metadata (tags, links, frontmatter), filenames, and more