Skip to main content
Glama
cks850711

Obsidian CLI MCP Server

by cks850711

obsidian_exec

Executes any official Obsidian CLI command to search, read, create, and manage notes in your vault, returning the output.

Instructions

Execute any official Obsidian CLI command and return its output.

This tool wraps the obsidian CLI binary installed on the host machine. Pass the sub-command and arguments as a single string (without the leading obsidian binary name).

Blocked commands (configurable): eval, restart, devtools, dev:cdp, dev:css, dev:debug, dev:dom, dev:mobile

Common examples: command="search query="meeting notes" limit=10" command="read file=MyNote" command="tasks todo" command="tags counts sort=count" command="create name=NewNote content="Hello world"" command="properties file=MyNote" command="backlinks file=MyNote" command="files folder=Projects ext=md" command="bookmarks" command="help search"

For a full list of commands, use: command="help"

Args:

  • command (string, required): The CLI sub-command and arguments

  • vault (string, optional): Target vault name

Returns: The raw stdout from the CLI. If the command fails, stderr and exit code are included.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vaultNoTarget a specific vault by name. Omit to use the active vault.
commandYesThe Obsidian CLI command to execute, e.g. "search query=hello limit=5" or "read file=MyNote". Do NOT include the leading `obsidian` binary name — just the sub-command and its arguments.
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided; description covers returned stdout/stderr/exit code and blocked commands. Lacks details on side effects or security implications, but acceptable for a CLI wrapper.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections, front-loaded purpose, examples, args, and returns. No superfluous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 2-param tool with no output schema, description covers all necessary aspects: usage, blocked commands, return format, and examples.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds value by explaining command format (excluding leading 'obsidian') and giving concrete examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it executes Obsidian CLI commands and returns output. Distinguishes from sibling tool by focusing on execution, while the sibling manages blocked commands.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides extensive examples and mentions blocked commands and how to get full list via 'help'. Does not explicitly state when not to use it, but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cks850711/obsidian-cli-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server