Development
obsidian-sync-mcp
by io.github.es617 · v0.5.2
Give AI agents access to your Obsidian vault via local files or Self-hosted LiveSync.
- GitHub stars
- 27
- Transport
- Streamable HTTP (remote)
- Auth
- None required
- Test status
- untested
Install & run
Run the server locally with the package command below.
terminal
$npx -y obsidian-sync-mcpConnect this MCP server to your AI agent
MCP servers plug into any MCP-compatible client (Claude Desktop, Cursor, your own agent runtime, and more). The steps are the same everywhere:
- 1. Make sure the runtime is available. This server is remote — you only need network access to its endpoint; nothing to install locally.
- 2. Add it to your MCP client config. Point your client at the remote URL above. Most clients accept an MCP servers map keyed by a name of your choosing.
- 3. No credentials needed. This server declares no required secrets — it should work out of the box.
- 4. Restart your client and verify.The server’s tools should appear in your agent’s tool list, ready to call.
Want this running without wiring configs yourself? Run this with Alfe →
Developmentnpm
Data from the official MCP registry · last updated 2026-03-30 · ★ 27 stars via GitHub.