Easy Obsidian MCP

What louis030195/easy-obsidian-mcp MCP server does

The louis030195/easy-obsidian-mcp MCP server exposes an Obsidian vault to compatible AI clients through MCP. It is intended for knowledge-management tasks involving local notes, folders, metadata, tags, links, and tasks. The supplied tool list focuses on finding and inspecting vault content rather than sending data to an external hosted service.

The repository describes support for creating, reading, updating, and searching notes, while the explicitly listed MCP tools cover reading, listing, searching, Dataview queries, and graph analysis. Developers should verify the available tool definitions in the installed package if note mutation is required.

How it works

The server runs locally through the npm package @louis030195/mcp-obsidian, launched with npx. AI clients communicate with it over the MCP server configuration. Vault operations can use filesystem access, and the README documents an optional Obsidian Local REST API plugin for full features.

Simple search checks file contents for a text query. Fuzzy search is useful when the spelling or wording is uncertain and is described as working even when the Obsidian API is unavailable. Graph search examines links between notes, including orphan detection and relationship discovery, and also works without the API.

Dataview search accepts DQL, Obsidian Dataview’s query language. Queries can filter, sort, group, and transform results using fields such as frontmatter, inline fields, tags, folders, links, file names, paths, dates, and tasks. DQL processing is sequential, so later commands receive the results of earlier commands.

Setup and configuration

The louis030195/easy-obsidian-mcp MCP server can be added to Claude Desktop or Cursor by defining an MCP entry with the npx -y @louis030195/mcp-obsidian command. The README also gives a Claude Code command using the same package.

For the optional full-feature path, install and enable Obsidian’s Community Plugins feature named Local REST API, then place its API key in the OBSIDIAN_API_KEY environment variable. The README marks this API setup as optional. If connection problems occur, check that Obsidian is running, the Local REST API plugin is enabled when needed, and the configured key is correct.

Tools and capabilities

• obsidian_simple_search searches all vault files for matching text.
• obsidian_fuzzy_search finds notes using approximate matching.
• obsidian_dataview_search runs DQL queries over note metadata and relationships.
• obsidian_get_file_content retrieves the complete content of a specified file.
• obsidian_list_files lists files and folders at the vault root or within a selected directory.
• obsidian_graph_search analyzes note links, finds orphaned notes, and builds link relationships.

Together, these tools support searches for tags, folders, backlinks, note titles, and structured metadata. Examples include listing notes from a folder, finding notes linked to a page, and selecting files modified during a period.

Limitations and notes

The tool list does not enumerate a dedicated create-note or update-note operation, despite the broader repository description mentioning create and update interactions. Confirm mutation support before designing workflows that write to a vault. Dataview queries must use DQL syntax rather than SQL syntax. API-dependent behavior may require Obsidian to be running with Local REST API enabled, while fuzzy and graph searches are specifically described as usable without the API.