home / mcp / obsidian mcp server
MCP server that interacts with Obsidian via the Obsidian rest API community plugin
Configuration
View docs{
"mcpServers": {
"markuspfundstein-mcp-obsidian": {
"command": "uvx",
"args": [
"mcp-obsidian"
],
"env": {
"OBSIDIAN_HOST": "<your_obsidian_host>",
"OBSIDIAN_PORT": "<your_obsidian_port>",
"OBSIDIAN_API_KEY": "<YOUR_API_KEY>"
}
}
}
}This MCP server lets Obsidian talk to your vault through the Local REST API plugin. It exposes a set of tools you can invoke from an MCP client to read, search, modify, and manage your Obsidian notes from outside Obsidian, enabling automated workflows and integrations.
You use this MCP server by running it as a local service and then connecting to it with an MCP client. The server provides tools to list files in your vault, read file contents, search across notes, and modify notes by inserting or appending content, as well as deleting files. Start a client that issues the documented MCP commands for these tools, and the server will perform the requested actions against your Obsidian vault in real time. When you issue operations, you control which vault directory you target by configuring the server with the Obsidian API connection details. If you need to summarize notes, extract sections, or append context to existing notes, you can chain tool calls and save results back into the vault.
Prerequisites you need before starting: a working Obsidian vault with the Local REST API community plugin enabled, Node.js and npm (or uv/uvx as specified by the MCP tooling), and access to configure environment variables for API keys and host information.
1. Install and enable the Obsidian Local REST API plugin in Obsidian and copy the API key from its settings. 2. Ensure Obsidian is reachable at the host and port you will configure (default host is 127.0.0.1 and default port is 27124 if not specified). 3. Create an MCP configuration that points to your Obsidian API key and host details. 4. Run the MCP server configuration and start the server. 5. Connect an MCP client to the running server and begin issuing tool commands to interact with your vault.
Below you’ll find concrete configuration examples for enabling the Obsidian MCP server. Include the exact blocks in your setup to ensure MCP clients can start and connect to the server. The configurations shown are the published and development variants that reference the same underlying Obsidian API settings.
Lists all files and directories in the root directory of your Obsidian vault.
Lists all files and directories in a specific Obsidian directory.
Return the content of a single file in your vault.
Search for documents matching a specified text query across all files in the vault.
Insert content into an existing note relative to a heading, block reference, or frontmatter field.
Append content to a new or existing file in the vault.
Delete a file or directory from your vault.