Exposes Obsidian vaults to AI assistants through a local REST API using the Model Context Protocol.
Exposes Obsidian vaults to AI assistants through a local REST API using the Model Context Protocol.
An MCP (Model Context Protocol) server implementation that provides access to Obsidian vaults through a local REST API. This server allows AI assistants to interact with Obsidian notes and manage vault content through a standardized interface.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| listNotes | List all notes in the vault or a specific folder |
| readNote | Read the contents of a specific note |
| writeNote | Create or update a note |
| searchNotes | Search for notes using a query string |
| getMetadata | Get metadata for a specific note |
{
"mcpServers": {
"obsidian-rest": {
"command": "npx",
"args": ["-y", "PublikPrinciple/obsidian-mcp-rest"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.