TypeScript MCP server for Obsidian with a filesystem-first LLM Wiki layer, Dataview / Canvas / Kanban / Mermaid / Marp / Templates tools, and both
Connect Kobsidian to Claude, Cursor or any other MCP client and it stops being a tab you switch to. TypeScript MCP server for Obsidian with a filesystem-first LLM Wiki layer, Dataview / Canvas / Kanban / Mermaid / Marp / Templates tools, and both stdio and Streamable HTTP transports. The kobsidian mcp server is what makes that connection.
Inspired by Andrej Karpathy's LLM Wiki idea. You curate the sources; the LLM does the bookkeeping.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Smithery — The Smithery tool exposed by this serverTLDR — No combination of plugins makes kObsidian depend on Obsidian being running — the REST-bridged tools just return a clear error if the plugin isn'tConfiguration is passed through the environment: OBSIDIAN_VAULT_PATH, OBSIDIAN_API_URL, OBSIDIAN_REST_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
The server ships on npm as kobsidian-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Kobsidian's toolset — Smithery, TLDR — is a fair guide to whether it matches your workflow. It is maintained by bezata; 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 |
|---|---|
| Smithery | The Smithery tool exposed by this server. |
| TLDR | No combination of plugins makes kObsidian depend on Obsidian being running — the REST-bridged tools just return a clear error if the plugin isn't reachable, and the filesystem-first tools keep working. |
{
"mcpServers": {
"kobsidian": {
"command": "npx",
"args": ["-y", "kobsidian-mcp"],
"env": {
"OBSIDIAN_VAULT_PATH": "your-value",
"OBSIDIAN_API_URL": "your-value",
"OBSIDIAN_REST_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| OBSIDIAN_VAULT_PATH | Filesystem location the server is allowed to use. | Optional |
| OBSIDIAN_API_URL | Endpoint or connection string the server talks to. | Yes |
| OBSIDIAN_REST_API_KEY | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.