Log inSubmit server
Obsidian MCP Secure logo

Obsidian MCP Secure

Connects MCP-compatible AI clients to an Obsidian vault through audited, validated note-management tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Obsidian MCP Secure

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "obsidian-mcp-secure": {
      "command": "npx",
      "args": [
        "-y",
        "obsidian-mcp-secure"
      ],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_VALUE_HERE",
        "OBSIDIAN_HOST": "YOUR_VALUE_HERE",
        "OBSIDIAN_PORT": "YOUR_VALUE_HERE",
        "LOG_DIR": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 9 tools correctly (6d ago).

Overview

obsidian-mcp-secure MCP server connects MCP-compatible AI clients to an Obsidian vault through the Local REST API plugin. It exposes tools for reading, searching, creating, editing, deleting, and linking Markdown notes, plus listing files and tags. Requests use validated paths and inputs, while destructive operations require confirmation and every call is written to a rotating audit log. Reach for it when your AI workflow runs in Claude Desktop or another MCP client and needs controlled access to Obsidian notes.

Use cases

  • Read notes from an Obsidian vault in Claude Desktop
  • Search vault content and tags by topic
  • Create or update Markdown notes from an AI workflow
  • Add related-note wiki links with an auditable operation
  • Combine vault notes with fetched web content

Key features

  • Read, create, edit, and delete Markdown notes
  • Search full text and tags through Obsidian
  • Find notes by case-insensitive partial name
  • List vault files, folders, and tag usage
  • Create backlinks in a related-notes section
  • Validate inputs and write rotating audit logs

Tools9

What Obsidian MCP Secure lets your agent do. Expand a tool for its parameters.

Verified live~828 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 42d

What it can do

From the 9 tools this server returned when we ran it.

Can delete or modify data · 1Read-only tools · 8
Network at startup3 connections
Files written at startup2
Install scriptsNone
npm provenanceNot published
Package age177 days
Maintainers1

Observed 2026-10-18 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14h ago via OSV.dev · obsidian-mcp-secure (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads160Package downloads in the last 30 days.
Last commit5mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed9Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Obsidian MCP Secure works

What obsidian-mcp-secure does

The obsidian-mcp-secure MCP server provides a bridge between an MCP-compatible AI client and an Obsidian vault. It is not an Obsidian plugin: the AI client remains the user-facing application, while this package sends requests to Obsidian's Local REST API plugin.

The server works with Markdown notes and vault folders. It can retrieve notes, inspect directory contents, create or replace notes, remove notes, search note content and tags, find notes by partial name, enumerate tags with usage counts, and add wiki links under a ## Relacionadas section. This makes it suitable for assistants that need to inspect or update a local knowledge base from outside Obsidian.

How it works

Obsidian Desktop must have the target vault open with the Local REST API plugin enabled. The plugin provides an HTTP endpoint, normally on 127.0.0.1:27123, and the MCP process uses the plugin's API key to access the vault. An MCP client communicates with the package over standard input and output; the package then communicates with the local REST API over HTTP.

The server accepts only localhost-style hosts, blocks traversal patterns including encoded variants, and requires the .md extension for note paths. Zod schemas validate tool inputs. Note content is limited to 512 KB, searches return at most 50 results, and deleting a note requires an explicit confirm: true value. Each tool call records its action, sanitized parameters, outcome, error information, and timestamp.

Setup and configuration

Install Node.js 18 or newer, Obsidian Desktop, and the Local REST API plugin by Adam Coddington. Enable the plugin's non-encrypted HTTP server and copy its API key. The package can then be launched with npx obsidian-mcp-secure from an MCP client's server configuration.

Set OBSIDIAN_API_KEY to the key from the plugin. OBSIDIAN_HOST defaults to http://127.0.0.1, OBSIDIAN_PORT defaults to 27123, and LOG_DIR defaults to ./logs. The host setting accepts only 127.0.0.1 or localhost. On Windows, Claude Desktop configurations may need npx.cmd instead of npx if the executable is not resolved.

Tools and capabilities

The nine exposed tools are:

  • read_note reads a note by path.
  • list_notes lists files and folders in the vault or a subdirectory.
  • create_note creates a new Markdown note.
  • edit_note replaces an existing note and preserves the previous content in the audit log.
  • delete_note removes a note only when confirmation is supplied.
  • search_notes searches full text or tags using Obsidian's search engine.
  • find_note_by_name finds notes by a case-insensitive partial name.
  • list_tags reports tags and their usage counts, with sorting by name or frequency.
  • create_backlinks adds [[wikilinks]] to a note's ## Relacionadas section.

The obsidian-mcp-secure MCP server can be used alongside other MCP servers, such as a fetch server, so an AI client can combine vault data with external content in one conversation. That companion setup is optional and is not part of this package.

Limitations and notes

The Local REST API plugin and an open Obsidian vault are prerequisites. The server is designed for local access and rejects non-local hosts, so it is not a general remote vault gateway. It provides no shell, eval, or exec access. Deletion is intentionally guarded, and search results and note size are capped by the server's validation rules.

Audit files use Winston with size-based rotation at 5 MB and up to 10 files. The API key is read from environment configuration and is not intended to be hardcoded or logged. The obsidian-mcp-secure MCP server is therefore best suited to clients that can launch standard-input/standard-output MCP processes and keep the local Obsidian and REST API components available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Obsidian MCP Secure

obsidian-mcp-secure is an MCP server that connects Claude Desktop or another MCP client to an Obsidian vault through the Local REST API plugin. Its main tools read, search, create, edit, delete, and link Markdown notes, while also listing vault files and tags with validated inputs and audit logging.

Install Node.js 18 or newer, Obsidian Desktop, and the Local REST API plugin, then launch the server with `npx obsidian-mcp-secure` in your MCP client configuration. Enable the plugin's non-encrypted HTTP server and provide its API key through `OBSIDIAN_API_KEY`.

`OBSIDIAN_API_KEY` is required, while `OBSIDIAN_HOST`, `OBSIDIAN_PORT`, and `LOG_DIR` are optional. The defaults are `http://127.0.0.1`, port `27123`, and `./logs`; only localhost hosts are accepted.

Because it uses a standard stdio MCP process, a compatible client must be able to launch the configured `npx` command and pass the documented environment variables.

It logs every tool call with the action, sanitized parameters, success status, error information, and timestamp. Winston rotates audit logs by size at 5 MB and retains up to 10 files; the API key is not logged.

Related MCP servers

All in Monitoring All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewObsidian MCP Secure AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/obsidian-mcp-secure?style=directory)](https://allmcps.com/mcp/obsidian-mcp-secure)
HTML Embed
<a href="https://allmcps.com/mcp/obsidian-mcp-secure"><img src="https://allmcps.com/api/badge/obsidian-mcp-secure?style=directory" alt="Obsidian MCP Secure on AllMCPs" /></a>