Developer · Local MCP server
kObsidian
Filesystem-first MCP for Obsidian - an LLM-maintained wiki inspired by Karpathy's LLM Wiki.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.bezata/kobsidian-mcp- Version
- 0.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-23
- Updated
- 2026-04-23
- Publisher
- bezata (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/bezata) · how
- Listed under
- Obsidian MCP servers
- Website
- github.com/bezata/kObsidian
- Repository
- github.com/bezata/kObsidian
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | kobsidian-mcp | 0.2.1 | stdio |
How to connect kObsidian
kObsidian runs locally from a Node.js package published to the npm registry: kobsidian-mcp version 0.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y kobsidian-mcp@0.2.1. It reads these environment variables: OBSIDIAN_VAULT_PATH (required), OBSIDIAN_API_URL, OBSIDIAN_API_VERIFY_TLS and OBSIDIAN_REST_API_KEY (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"kobsidian-mcp": {
"command": "npx",
"args": [
"-y",
"kobsidian-mcp@0.2.1"
],
"env": {
"OBSIDIAN_VAULT_PATH": "<value>",
"OBSIDIAN_API_URL": "<value>",
"OBSIDIAN_API_VERIFY_TLS": "<value>",
"OBSIDIAN_REST_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| KnowlPersistent memory for Claude Code, Cursor and Codex. Facts retire when they change. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Knowledge Graph RDBMSA label property graph on SQLite/Postgres with multi-ontology routing and a gated MCP server. | Local · stdio |
| Knowledge GridSearch log events, investigate anomalies, and manage cases in your Knowledge Grid tenant. | Remote · HTTPLive check: sign-in required |
| knowmindAI agent memory & knowledge graph, hosted in Germany (GDPR). Recall, relations, store via MCP. | Local · stdio |
| KodaVerification and memory layer for coding-agent workflows. | Local · stdio |
| KogniteHosted agent memory: store, search, and recall facts across sessions from any MCP client. | Remote · HTTPLive check: sign-in required |
| Kolada SeKolada (RKA) MCP - Sweden's municipal & regional key-performance-indicator (KPI) database. | Remote · HTTPLive check: ✓ handshake |
| Koma Gate MCPClassifies prompt injection, jailbreaks, and out-of-scope user input before agents act on it. | Local · stdio |