obsidian-cli-rest
by dsebastien·★ 14·Score 42
Turns Obsidian CLI commands into an HTTP API and MCP server for automation and AI assistant integration.
Overview
This plugin transforms Obsidian's command-line interface into a programmatic API accessible through both REST endpoints and MCP protocol. It exposes virtually all Obsidian CLI commands organized into categories like files, search, properties, daily notes, tasks, and more. The server runs locally with API key authentication and can be configured for network access. Its MCP implementation uses a 'Code Mode' pattern with just two tools (search and execute) that enable progressive discovery of all commands regardless of their number.
Try asking AI
After installing, here are 6 things you can ask your AI assistant:
When to choose this
Choose this if you need to programmatically control your Obsidian vault or connect AI assistants to your notes via MCP.
When NOT to choose this
Don't choose this if you need access to Obsidian GUI features or if you're concerned about potential security risks of exposing your vault via API.
Tools this server exposes
12 tools extracted from the READMEsearchDiscover commands by name, description, or category
executeRun any CLI command by name
filesList files in your vault
createCreate new notes
readRead content of existing notes
appendAdd content to the end of notes
property:setSet frontmatter properties in notes
daily:readRead today's daily note
tagsList tags and get tag information
tasksList and manage tasks
pluginsList, install, enable, disable, and uninstall plugins
templatesList, read, and insert templates
Comparable tools
Installation
Installation
- In Obsidian, go to **Settings → Community plugins**
- Disable **Restricted mode** if enabled
- Search for **REST and MCP server**, install and enable it
Claude Desktop Configuration
Add to your claude_desktop_config.json:
{
"mcpServers": {
"obsidian": {
"command": "http",
"args": ["http://127.0.0.1:27124/mcp"],
"env": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Configuration
- Copy your API key from **Settings > REST and MCP server > Security**
- The server starts automatically on port 27124
FAQ
- Is this plugin secure for network access?
- By default it only runs on localhost. For network access, you can change the bind address to 0.0.0.0 in settings, but an API key is always required. Dangerous commands are blocked by default.
- How many MCP tools are exposed?
- Only two tools are exposed regardless of the number of CLI commands: 'search' to discover commands, and 'execute' to run them. This follows the 'Code Mode' pattern for efficient discovery.
Compare obsidian-cli-rest with
Last updated · Auto-generated from public README + GitHub signals.