obsidian-tc

A turbocharged MCP server for Obsidian.

obsidian-tc quickstart: zero-config boot, search_text, read_note, and a write_note overwrite that requires confirmation

A static storyboard for now — docs/demo/quickstart.tape renders the animated version (docs/public/demo/quickstart.gif) once vhs is on your PATH.

What is obsidian-tc?

obsidian-tc is a Model Context Protocol server that exposes an Obsidian vault to AI agents through a broad set of typed tools, presented via a configurable tool-surface facade (a compact triad of meta-tools by default, or the full surface in flat mode). It runs locally or remotely, and supports multi-vault setups and signed-JWT auth. An optional companion plugin, TC Bridge, extends it with live-Obsidian features (command-palette dispatch, Templater, Dataview, and more) over the Obsidian Local REST API — the server runs without it, degrading bridge-only tools gracefully.

Memory you write with obsidian-tc is plain Markdown in your own vault, not a vendor-hosted feature — see Memory you own for the on-disk shape, the ACL/ audit pipeline every write goes through, and a session-bootstrap recipe.

v1.34.0 is the current release, published to npm with a container image on GHCR.

See Getting Started for install instructions, or browse the Tool Reference.

obsidian-tc sends no telemetry by default; usage telemetry is opt-in, anonymous, and never carries vault content — see Telemetry.