obsidian-bridge
Provides tools for reading, writing, searching, patching, and organizing notes in an Obsidian vault through the Obsidian Local REST API, including daily notes, tags, append/patch, and opening notes in the Obsidian UI.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@obsidian-bridge Log my standup update to today's daily note"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Obsidian Bridge
Connect Cursor agents to your local Obsidian vault — calmly, securely, and with production-grade tooling.
Obsidian Bridge is a Cursor Plugin that ships an MCP server for reading, writing, searching, patching, and organizing notes through the Obsidian Local REST API. Vault traffic stays on your machine; the API key never leaves Cursor Configure / your environment.
Highlights
Local-first MCP bridge (
127.0.0.1:27124by default)Daily notes, search, tags, append/patch, open-in-Obsidian
Setup + note-writing skills, vault-safety rules, hub-and-spoke graph guidance
Typed TypeScript server, tests, and CI
Related MCP server: Obsidian-MCP-For-Cursor
Install (Cursor Marketplace)
Install / enable Local REST API in Obsidian
(obsidian://show-plugin?id=obsidian-local-rest-api) and copy the API key.Build once so the plugin ships the MCP binary:
npm install
npm run buildIn Cursor, add this GitHub repo as a marketplace:
https://github.com/dkdottk/obsidian-bridge
(prefer GitHub overfile://— Cursor’s sandbox blocksgit ls-remoteon the file protocol).Install Obsidian Bridge → Plugins → Configure → paste the API key.
Ask Cursor: “Check Obsidian status.”
Defaults: https://127.0.0.1:27124.
Marketplace layout
.cursor-plugin/marketplace.json ← required for Cursor marketplace import
plugins/obsidian-bridge/ ← the installable plugin
.cursor-plugin/plugin.json
mcp.json
skills/ rules/ assets/ dist/What the agent can do
Capture to daily notes
Create, append, and patch notes
Search the vault and browse tags
Open notes in the Obsidian UI
Run Obsidian commands when you explicitly ask
Keep vault graphs readable (hub-and-spoke / MOC linking)
Plugin components
Piece | Role |
MCP server | Vault tools over Local REST API |
| Three-step connect flow |
| Capture / organize habits |
| Index/hub/leaf linking rules |
Vault safety + hub-spoke rules | Always-on guardrails |
Develop
npm install
npm run ciUseful scripts:
npm run build— compile todist/and sync into the pluginnpm test— Vitest suitenpm run typecheck— max-strict TypeScriptnpm run lint— ESLint
See docs/setup.md, docs/architecture.md, and docs/tools.md.
Security
Your API key stays in Cursor plugin variables / local environment. It is never committed and never logged. The bridge only calls a localhost endpoint you control. See SECURITY.md.
Author
Danylo Kravchenko · dkdottk@gmail.com
License
AGPL-3.0-only — free to use, study, modify, and share.
If you distribute a modified version, or run a modified version as a network service, you must offer the corresponding source under AGPL-3.0. See the LICENSE for full terms.
Available Tools
15 toolsobsidian_appendAppend to NoteA
Append markdown to the end of a note (creates the note if needed).
Inputs: path (required), content (required).
obsidian_command_executeExecute Obsidian CommandADestructive
Execute an Obsidian command by id. Only use when the user explicitly asks for it.
Inputs: commandId (required).
obsidian_commands_listList Obsidian CommandsA
List available Obsidian commands.
Inputs: no named parameters.
obsidian_createCreate or Replace NoteA
Create a note or replace its entire contents.
Inputs: path (required), content (required).
obsidian_daily_appendAppend to Daily NoteA
Append markdown to today's daily note (creates it if missing).
Inputs: content (required).
obsidian_daily_readRead Daily NoteA
Read today's daily note using OBSIDIAN_DAILY_NOTE_PATH (default Daily/YYYY-MM-DD.md).
Inputs: no named parameters.
obsidian_deleteDelete NoteADestructive
Delete a note. By default moves to trash; set permanent=true only when the user explicitly asks.
Inputs: path (required), permanent.
obsidian_files_by_tagFiles by TagB
Find notes that contain a given tag via vault search.
Inputs: tag (required).
obsidian_listList Vault PathA
List files and folders at a vault directory (root when path is omitted).
Inputs: path.
obsidian_openOpen Note in ObsidianB
Open a note in the Obsidian UI.
Inputs: path (required), newLeaf.
obsidian_patchPatch Note SectionB
Insert, prepend, or replace content relative to a heading, block reference, or frontmatter field.
Inputs: path (required), target (required), content (required), operation (required), +1 more.
obsidian_readRead NoteA
Read a note as markdown, or as structured JSON metadata when asJson is true.
Inputs: path (required), asJson.
obsidian_searchSearch VaultB
Full-text search across the vault using Obsidian's simple search.
Inputs: query (required), contextLength.
obsidian_statusObsidian StatusA
Check whether Obsidian Local REST API is reachable and authenticated.
Inputs: no named parameters.
obsidian_tags_listList TagsA
List all tags in the vault with usage counts.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Most tools have clear distinct purposes, but the overlapping modify operations (create, append, patch) and specialized daily note variants (daily_read, daily_append) could potentially be confused by an agent without careful reading. Overall, descriptions help disambiguate.
Tool names share the 'obsidian_' prefix but mix verb-only names (create, append, read), verb-object names (daily_read, daily_append), noun-verb names (tags_list, commands_list), and a noun phrase (files_by_tag). This inconsistency makes the set less predictable.
With 15 tools, the server is well-scoped for Obsidian vault management, covering CRUD, search, tags, daily notes, commands, and UI interaction. It's slightly on the higher end but still appropriate for the breadth of functionality.
The core note lifecycle is covered (create, read, update via append/patch, delete), along with search, tags, daily notes, and command execution. Minor gaps exist such as no rename/move or folder creation, but these are not critical for most workflows.
Maintenance
Related MCP Connectors
Hosted MCP server for Obsidian Sync vaults: read, search, edit notes. Not affiliated with Obsidian.
Markdown-based note-taking with a hosted MCP server. Your notes serve you and your AI.
Google Keep-style notes app with an MCP server for AI agents to read/write notes.
Search your AI chat history (ChatGPT, Claude, Codex) from any MCP client. Remote, private, read-only
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA local MCP server that wraps the Obsidian CLI to give AI assistants direct access to read, edit, and manage notes within an Obsidian vault. It enables advanced operations such as frontmatter property management, context-aware searching, and the execution of internal Obsidian commands.2MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Obsidian vaults, optimised for Cursor agents — safe note editing, lean tool surface, direct filesystem access.-
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with Obsidian via the Local REST API, enabling file operations, search, and content editing in your vault.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server to interact with Obsidian via the Local REST API community plugin, enabling file listing, search, content manipulation, and note management.MIT