MCP Server for Obsidian Vault Access via Local REST API
MCP Server for Obsidian Vault Access via Local REST API. Exposed over MCP by the mcp obsidian via rest mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
This MCP server exposes the following tools and resources to AI assistants:
Everything the assistant can do here goes through one of these:
get_note_content — Retrieve content and metadata of an Obsidian noteobsidian_search — Search notes using a query stringobsidian_semantic_search — Semantic search for notesTools — The Tools tool exposed by this serverResources — The Resources tool exposed by this serverSetup — This setting will allow you to connect to the Local REST API from any network interface (not only localhost, which is critical for WSL2 setup)You will need 8 environment variables: API_KEY, API_URLS, DEBUG, MCP_HTTP_PATH, API_HOST, API_PORT, OBSIDIAN_API_KEY, WSL_GATEWAY_IP. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Obsidian Via Rest's toolset — get_note_content, obsidian_search, obsidian_semantic_search and 3 more — is a fair guide to whether it matches your workflow. It is maintained by OleksandrKucherenko; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| get_note_content | Retrieve content and metadata of an Obsidian note |
| obsidian_search | Search notes using a query string |
| obsidian_semantic_search | Semantic search for notes |
| Tools | The Tools tool exposed by this server. |
| Resources | The Resources tool exposed by this server. |
| Setup | This setting will allow you to connect to the Local REST API from any network interface (not only localhost, which is critical for WSL2 setup). |
```jsonc
{
"mcpServers": {
"obsidian": {
"type": "streamable-http",
"url": "http://localhost:3000/mcp",
"headers": {
"Authorization": "Bearer <your-secret-token-here>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| API_KEY | Credential the server authenticates with. | Yes |
| API_URLS | Endpoint or connection string the server talks to. | Yes |
| DEBUG | Configuration value read at startup. | Optional |
| MCP_HTTP_PATH | Filesystem location the server is allowed to use. | Optional |
| API_HOST | Endpoint or connection string the server talks to. | Optional |
| API_PORT | Configuration value read at startup. | Optional |
| OBSIDIAN_API_KEY | Credential the server authenticates with. | Yes |
| WSL_GATEWAY_IP | 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.