AI-Native MCP server for Obsidian vaults with task-oriented, intelligent tools designed for LLM workflows
If you want an AI assistant working directly with Obsidian Local Rest Api MCP, the obsidian local rest api mcp mcp server is the bridge. AI-Native MCP server for Obsidian vaults with task-oriented, intelligent tools designed for LLM workflows.
An AI-Native MCP (Model Context Protocol) server that provides intelligent, task-oriented tools for interacting with Obsidian vaults through a local REST API.
Once connected, the assistant can call these 9 tools directly:
list_directory — The list_directory tool exposed by this serverread_file — The read_file tool exposed by this serverwrite_file — The write_file tool exposed by this serverdelete_item — The delete_item tool exposed by this servercreate_or_update_note — The create_or_update_note tool exposed by this serverget_daily_note — The get_daily_note tool exposed by this serverget_recent_notes — The get_recent_notes tool exposed by this serversearch_vault — The search_vault tool exposed by this serverfind_related_notes — The find_related_notes tool exposed by this serverThe server is distributed via npm as obsidian-local-rest-api-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 3 environment variables: OBSIDIAN_API_URL, OBSIDIAN_API_KEY, DEBUG. Keep credentials in your client's env block or a secrets manager rather than committing them.
Productivity servers pay off through capture: the tasks and notes that never get filed are the ones where opening the app is more friction than the thought is worth. Obsidian Local Rest Api MCP sits in that group, and the shape of its toolset — list_directory, read_file, write_file among others — tells you what it is really for. Worth comparing against the other productivity servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| list_directory | The list_directory tool exposed by this server. |
| read_file | The read_file tool exposed by this server. |
| write_file | The write_file tool exposed by this server. |
| delete_item | The delete_item tool exposed by this server. |
| create_or_update_note | The create_or_update_note tool exposed by this server. |
| get_daily_note | The get_daily_note tool exposed by this server. |
| get_recent_notes | The get_recent_notes tool exposed by this server. |
| search_vault | The search_vault tool exposed by this server. |
| find_related_notes | The find_related_notes tool exposed by this server. |
{
"mcpServers": {
"obsidian-vault": {
"command": "npx",
"args": ["obsidian-local-rest-api-mcp"],
"env": {
"OBSIDIAN_API_URL": "http://obsidian-local-rest-api.test",
"OBSIDIAN_API_KEY": "your-api-key-if-needed"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OBSIDIAN_API_URL | Endpoint or connection string the server talks to. | Yes |
| OBSIDIAN_API_KEY | Credential the server authenticates with. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.