The Local REST API plugin also provides an MCP endpoint for the open Obsidian vault. For Cursor, 3 routes are explicitly documented by the integration maintainer.
The Local REST API plugin also provides an MCP endpoint for the open Obsidian vault.
Platforms: Windows, macOS, Linux
The maintainer documents Cursor setup for this connection.
Obsidian with the Local REST API community plugin installed and authenticated local access configured.
Access is limited to the configured vault and enabled plugin endpoints; authentication is required.
The Obsidian Local REST API plugin exposes authenticated HTTP operations for vault notes and commands.
Platforms: Windows, macOS, Linux
The native interface is documented, but no setup for this coding agent is established by this source.
Obsidian with the Local REST API plugin enabled and the client configured with its API key and endpoint.
HTTP access requires authentication and the running plugin; MCP client setup belongs to the separate MCP connection.
A local-first MCP server for searching and editing Obsidian vault files.
Platforms: Not documented
MCP support suggests compatibility; this client is not documented by the maintainer.
Node.js and a path to a local Obsidian vault.
The core tools read and write vault files directly; the optional REST bridge requires a separate plugin.
A server for reading and editing an Obsidian vault through MCP.
Platforms: Not documented
MCP support suggests compatibility; this client is not documented by the maintainer.
Node.js 22 or newer and an accessible vault folder; CouchDB is optional.
Filesystem mode edits vault files without requiring the Obsidian application; optional sync mode uses CouchDB.
A local vault server with MCP tools for searching and navigating Obsidian notes.
Platforms: Windows, macOS, Linux
The integration documentation explicitly names this client.
A local Obsidian vault and a compatible server binary.
The server operates on vault files; optional semantic search has additional dependencies.
A local MCP server that delegates vault access to the running Obsidian application.
Platforms: Windows, macOS, Linux
The integration documentation explicitly names this client.
A running Obsidian instance and the VaultGate local server.
The npm server supports desktop platforms; the optional tray companion is macOS Apple Silicon only.
| Integration | Cursor compatibility | Requirements |
|---|---|---|
| Obsidian Local REST API · MCP | Documented setup Setup guide | Obsidian with the Local REST API community plugin installed and authenticated local access configured. |
| Obsidian Local REST API | Not documented | Obsidian with the Local REST API plugin enabled and the client configured with its API key and endpoint. |
| Obsidian MCP Complete | MCP compatibility (inferred) | Node.js and a path to a local Obsidian vault. |
| Obsidian Sync MCP | MCP compatibility (inferred) | Node.js 22 or newer and an accessible vault folder; CouchDB is optional. |
| Obsidian MCP · lstpsche | Documented setup Setup guide | A local Obsidian vault and a compatible server binary. |
| VaultGate MCP | Documented setup Setup guide | A running Obsidian instance and the VaultGate local server. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Cursor and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All Obsidian integrations