mcp-obsidian-cli: Instructions file for Claude Code

CLAUDE.md

mcp-obsidian-cli CLAUDE.md is an instructions file for Claude Code from stonematt/mcp-obsidian-cli. It costs 1,010 tokens per session, scanned A, original, MIT.

A set of project instructions for mcp-obsidian-cli, an npm program that lets AI assistants use Obsidian's command-line interface. Obsidian is a note-taking app, and the app must be open for these commands to work.

In plain words
What is it for?
Use it when developing, running, or testing the mcp-obsidian-cli server, including its JavaScript files, command-line entry point, and MCP connections.
Why use it?
It records the repository's required file format, communication method, runtime assumptions, and testing commands so code changes follow the project's rules.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is stonematt/mcp-obsidian-cli's own configuration. It tells Claude Code how to work on mcp-obsidian-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-obsidian-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to stonematt/mcp-obsidian-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/stonematt/mcp-obsidian-cli/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/stonematt/mcp-obsidian-cli

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for mcp-obsidian-cli CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/stonematt/mcp-obsidian-cli/claude-md/github.svg)](https://agentmods.dev/instructions/stonematt/mcp-obsidian-cli/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/stonematt/mcp-obsidian-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/stonematt/mcp-obsidian-cli/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mcp-obsidian-cli CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/stonematt/mcp-obsidian-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/stonematt/mcp-obsidian-cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,010 This file is loaded in full into every session.
When invoked 1,010 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.01010 $0.01010
Opus 5.5 $0.00404 $0.00404
Sonnet 5.5 $0.00202 $0.00202
Haiku 4.5 $0.00101 $0.00101

Measured 2mo ago against content hash b09621d187de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcp-obsidian-cli CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project

mcp-obsidian-cli — An MCP server distributed via npm/npx that wraps the Obsidian CLI plugin, exposing Obsidian's full native API surface to AI assistants. All operations go through the obsidian CLI binary (IPC to running Obsidian instance); there is no direct Obsidian API access.

Constraints

  • ES modules only — "type": "module" in package.json; MCP SDK requires ESM
  • Zero build step — plain .js files, no TypeScript, no bundler
  • Stdio transport — MCP server communicates over stdin/stdout
  • Obsidian must be running — CLI commands fail if the app isn't open

Commands

# Run the server
node bin/server.js   # or: npm start

# Run tests (Node.js built-in test runner)
npm test             # runs everything under test/*.test.js

# Run via npx (as end users would)
npx mcp-obsidian-cli

Tests use node:test — no test framework dependency. test/run.test.js spawns bin/server.js as a child process to assert exit code and the running banner; test/server.test.js exercises createServer end-to-end via the SDK's InMemoryTransport with a fake ObsidianCli. The current contract is warn-and-continue when Obsidian is not detected — the server stays up; tool calls return OBSIDIAN_NOT_RUNNING until the app is opened.

Architecture

Three pieces, no top-level side effects in server.js:

  • bin/server.js (entrypoint) — the only file that performs I/O at module load. Reads config, prompts, and package.json#version; probes the CLI path via resolveCliPath; builds the ObsidianCli adapter; calls createServer(...); connects StdioServerTransport. Fatal errors here are the only path that calls process.exit.
  • server.js (createServer factory) — pure factory that returns a wired McpServer. Registers the generic obsidian pass-through tool, ~13 typed convenience tools, and four MCP prompts. Takes cli, prompts, manifest (reserved for #10), version, knownVaults, and runtimeVault as injected deps. Importing this file is silent.
  • lib/obsidian-cli.js — adapter around the obsidian-cli subprocess. createObsidianCli({cliPath, vault, timeoutMs, execFile}) returns { exec, getVault, setVault }; result shape is {stdout, stderr, error|null} with error.type ∈ {CLI_NOT_FOUND, TIMEOUT, EXECUTION_ERROR}. Also exports resolveCliPath (PATH / known paths / pgrep fallback) and createObsidianRunningChecker (TTL-cached pgrep probe). All probes are dependency-injectable for tests.

Read the full file on GitHub · 65 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 65 lines · 1,010 tokens per session scan A b09621d187de

Subscribe to this mod's changes

mcp-obsidian-cli CLAUDE.md is an instructions file published in the GitHub repository stonematt/mcp-obsidian-cli (2 stars, last pushed 18d ago), licensed MIT. It adds 1,010 tokens to every session, about $0.0040 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens