Server facts
kobsidian MCP Server
Project
- Author
- bezata
- Repository
- github.com/bezata/kObsidian
- License
- Not specified
- Category
- Memory & Knowledge
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 8
- Last commit
- Data as of
Tags
- Obsidian
- llm wiki
Overview
Obsidian research collections and engineering wikis are the focus of kObsidian’s filesystem-based MCP tools. Users can initialize a wiki organized into source, concept, and entity pages, then ingest existing notes or supplied Markdown. Ingestion records activity and returns proposed cross-reference edits for the agent to apply separately through note tools, keeping those changes visible in the conversation transcript. Topic queries rank relevant pages for subsequent reading, while summary merging adds cited material to concept or entity pages. Wiki audits identify disconnected pages, unresolved links, aging content, missing pages, and discrepancies between the index and stored files.
Beyond the wiki workflow, kObsidian supports note creation and editing, frontmatter changes, tag searches, backlinks, task metadata, and vault statistics. It also works with Kanban boards, Canvas documents, Marp decks, and supported fenced code blocks. Vault selection controls where filesystem operations run, with individual calls able to override that choice. Most filesystem tools work without Obsidian running or plugins installed. Live workspace actions require the Local REST API plugin; runtime DQL queries and Templater execution additionally depend on their respective plugins.
kobsidian setup notes
- kobsidian records stdio only; confirm a network transport upstream before planning remote access.
- kobsidian has no recorded license; confirm reuse terms in its repository.