MCP Obsidian (kaliab) MCP Server Integration
Alternative Obsidian MCP server with deep vault integration — full file system access to your notes.
Technical Integration & Multi-Client Support
The MCP Obsidian (kaliab) MCP Integration translates REST paths, operational endpoints, and tool schemas into standardized Model Context Protocol JSON-RPC 2.0 messages. This allows AI assistants like Claude Desktop, Cursor IDE, VS Code (Cline/Roo Code), and Zed Editor to run tool queries and execute functions seamlessly.
Add stdio configuration block to claude_desktop_config.json.
Configure workspace root at .cursor/mcp.json or Settings -> MCP.
Insert server JSON payload into cline_mcp_settings.json.
Specification & Compatibility Table
| Property | Specification Detail |
|---|---|
| Target Integration | MCP Obsidian (kaliab) (mcp-obsidian) |
| Directory Category | productivity |
| Protocol Spec | JSON-RPC 2.0 (stdio) |
| Canonical Path | /mcp-server/mcp-obsidian/ |
Frequently Asked Questions
How do I access the full JSON configuration for MCP Obsidian (kaliab)?
Click 'Open Full MCP Obsidian (kaliab) MCP Config' above to view the complete parameter schema, environment variable setup, and copy-pasteable JSON configs for Claude Desktop, Cursor, and VS Code.
Does MCP Obsidian (kaliab) require authentication secrets?
Authentication depends on upstream API requirements. Check the environment variable table on the detail page to view required API keys and header tokens.
More in Productivity
Browse by Category
Explore MCP server integrations organized by platform and use case.