Back to Browse

Obsidian Mcp Secure MCP Server

ProductivityModerate7.0MCP RegistryLocal
Free

Server data from the Official MCP Registry

Secure MCP server for Obsidian with OWASP Top 10 controls and full audit logging.

About

Secure MCP server for Obsidian with OWASP Top 10 controls and full audit logging.

Security Report

7.0
Moderate7.0Low Risk

Valid MCP server (2 strong, 4 medium validity signals). 3 known CVEs in dependencies (0 critical, 3 high severity) Package registry verified. Imported from the Official MCP Registry.

3 files analyzed Β· 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

file_system

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

API Key generated by Obsidian's Local REST API plugin (Settings -> Local REST API -> API Key)Required

Environment variable: OBSIDIAN_API_KEY

Host of the Local REST API (default: http://127.0.0.1)Optional

Environment variable: OBSIDIAN_HOST

Port of the Local REST API (default: 27123)Optional

Environment variable: OBSIDIAN_PORT

Directory for audit logs (default: ./logs)Optional

Environment variable: LOG_DIR

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-dewtech-technologies-obsidian-mcp-secure": {
      "env": {
        "LOG_DIR": "your-log-dir-here",
        "OBSIDIAN_HOST": "your-obsidian-host-here",
        "OBSIDIAN_PORT": "your-obsidian-port-here",
        "OBSIDIAN_API_KEY": "your-obsidian-api-key-here"
      },
      "args": [
        "-y",
        "obsidian-mcp-secure"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

obsidian-mcp-secure

npm version npm downloads MCP Registry license npm audit CI coverage Smithery

Secure Model Context Protocol server that turns your Obsidian vault into a reliable data source for any MCP-compatible AI client β€” built from scratch with OWASP Top 10 controls and full audit logging.

Listed on the official Anthropic MCP Registry as io.github.dewtech-technologies/obsidian-mcp-secure.


🧭 Positioning β€” this is NOT a plugin for Obsidian

It's the opposite: it's a bridge that lets Claude Desktop (or any MCP client) read and write inside Obsidian safely. Your AI assistant stays where it lives; your vault becomes a structured, auditable datasource it can reach.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   MCP    β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   HTTP   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   FS   β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                 β”‚  stdio   β”‚                      β”‚  :27123  β”‚                    β”‚        β”‚             β”‚
β”‚ Claude Desktop  β”‚ ───────▢ β”‚ obsidian-mcp-secure  β”‚ ───────▢ β”‚  Local REST API    β”‚ ─────▢ β”‚  Vault .md  β”‚
β”‚  (AI client)    β”‚          β”‚  (this package)      β”‚          β”‚ (Obsidian plugin)  β”‚        β”‚             β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜        β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Role in the pipelineComponent
Where you talkClaude Desktop (or any MCP client)
Bridge / access controlobsidian-mcp-secure (this package)
Data gateway inside ObsidianLocal REST API plugin (by Adam Coddington)
Your knowledge.md files in your vault

One-liner: Claude is the brain, this MCP is the arm, Obsidian is the memory.

Why another Obsidian + AI integration?

There are plugins that put Claude inside Obsidian. This is the inverse, and it exists because:

  • Your assistant is Claude Desktop β€” that's where the general-purpose conversations happen. Your notes become one of many contexts Claude can reach, alongside web, GitHub, filesystems, etc.
  • Security is a first-class concern β€” deliberate attack surface, no shell access, path traversal blocked, inputs validated with Zod, every call audited.
  • Zero build, zero account β€” npx obsidian-mcp-secure and done. Works on Windows, macOS, Linux the same way.
  • Composability β€” combine this MCP with fetch, filesystem, git, GitHub, etc., and Claude can cross-reference your vault with external sources in a single conversation.

πŸ› οΈ Available Tools

ToolPurpose
read_noteRead a note by path
list_notesList files/folders in the vault or a subdirectory
create_noteCreate a new .md note
edit_noteOverwrite an existing note (previous content goes to the audit log)
delete_noteDelete a note β€” requires confirm: true (Zod rejects otherwise)
search_notesFull-text / tag search using Obsidian's own search engine
find_note_by_nameFind notes by partial name β€” case-insensitive, no exact path needed
list_tagsEnumerate all tags in the vault with usage count; sortable by name or frequency
create_backlinksAdd [[wikilinks]] to a ## Relacionadas section in a note β€” explicit and auditable

πŸ”’ Security β€” OWASP Top 10

ControlImplementation
A01 β€” Broken Access ControlPath traversal blocked (../, ..\\, encoded variants); .md extension enforced
A02 β€” Cryptographic FailuresAPI key read from .env or process env; never hardcoded, never logged
A03 β€” InjectionAll inputs validated with Zod schemas; no eval, no exec, no shell
A04 β€” Insecure Design512 KB max note size; 50-result cap on search; destructive ops require explicit confirm: true
A05 β€” Security MisconfigurationOnly 127.0.0.1 / localhost accepted as host
A09 β€” Logging & MonitoringFull audit log via winston with size-based rotation (5 MB / 10 files)

Every tool call emits an audit line with action, params (sanitized), success, error, and timestamp.


⚑ Installation

Prerequisites

  1. Obsidian Desktop with a vault open
  2. The Local REST API plugin (by Adam Coddington) β€” install from Community Plugins, enable it, and:
    • Turn on "Enable Non-encrypted (HTTP) Server" (simpler than HTTPS self-signed certs)
    • Copy the API Key shown in the plugin settings
  3. Node.js 18+
  4. Claude Desktop (or another MCP-compatible client)

Configure Claude Desktop

Open %APPDATA%\Claude\claude_desktop_config.json on Windows (or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS) and add:

{
  "mcpServers": {
    "obsidian-secure": {
      "command": "npx",
      "args": ["-y", "obsidian-mcp-secure"],
      "env": {
        "OBSIDIAN_API_KEY": "your-api-key-from-the-plugin",
        "OBSIDIAN_HOST": "http://127.0.0.1",
        "OBSIDIAN_PORT": "27123",
        "LOG_DIR": "C:/path/to/your/logs"
      }
    }
  }
}

Windows tip: if npx fails silently, switch "command": "npx" to "command": "npx.cmd". Some Claude Desktop builds don't resolve bare npx on PATH.

Restart Claude Desktop (tray β†’ Quit, then reopen) and the 9 tools will show up under obsidian-secure.


🀝 Recommended companions

The real power of MCPs is composability. To reproduce the "read my note β†’ fetch a URL β†’ tell me if I'm applying it correctly" workflow, add the official fetch MCP alongside this one:

{
  "mcpServers": {
    "obsidian-secure": { "...": "as above" },
    "fetch": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch"]
    }
  }
}

Now Claude has both your vault and the live web in a single conversation.


πŸ’¬ Example prompts

With obsidian-secure + fetch enabled:

"Read my note Projeto API Atendimento.md, then fetch https://developers.facebook.com/docs/whatsapp and tell me if my implementation matches the latest best practices."

"Search my vault for the tag #ideia and summarize the three ideas that appear most often. Then create a new note called Ideias recorrentes.md with the summary."

"Read Atomic Habits - Resumo.md, fetch https://jamesclear.com/atomic-habits, and point out where my notes drifted from the original."

Claude will orchestrate the tool calls automatically β€” no manual chaining.


🧩 Comparison with in-Obsidian plugins

If your workflow lives inside Obsidian's sidebar, plugins like obsidian-claude-code are the right fit. This MCP targets a different shape:

Dimensionobsidian-claude-code (in-Obsidian)obsidian-mcp-secure (this)
Where the AI livesSidebar inside ObsidianClaude Desktop (or any MCP client)
Setupgit clone + bun buildnpx obsidian-mcp-secure
ToolsRead/Write/Edit + Bash + Grep + Glob + WebFetch9 purpose-built, Zod-validated tools
Security postureFull shell access to dev machineTight allowlist, audited, OWASP Top 10
DistributionManual clone, requires Bunnpm + official MCP Registry
Composability with other sourcesInside its own sandboxAny MCP-compatible client can mix it with fetch, GitHub, filesystem, etc.
Best forDev who lives in ObsidianProfessional whose main surface is Claude Desktop

Both are valid β€” they occupy different niches.


πŸ”§ Environment variables

VariableRequiredDefaultDescription
OBSIDIAN_API_KEYβœ…β€”API key from the Local REST API plugin
OBSIDIAN_HOSThttp://127.0.0.1Host (only 127.0.0.1 and localhost are accepted)
OBSIDIAN_PORT27123Port of the plugin's HTTP server
LOG_DIR./logsDirectory for the audit log files

πŸ—ΊοΈ Roadmap

βœ… Shipped in v1.2.1

  • Bug fix: find_note_by_name searches full path (folder + filename)
  • Bug fix: list_tags normalizes all API response formats (object, array of strings, array of objects with tagCount/taggedFilesCount)

βœ… Shipped in v1.2.0

  • DXT package for one-click install in Claude Desktop (npm run build:dxt)

βœ… Shipped in v1.1.0

  • find_note_by_name β€” partial, case-insensitive name match across the entire vault
  • create_backlinks β€” connect related notes with [[wikilinks]] (explicit, auditable)
  • list_tags β€” enumerate all tags in the vault with usage count
  • Unit test suite (70 tests β€” utils, handlers, HTTP client) with Vitest
  • CI pipeline on every PR: tests + coverage + npm audit + static security analysis

πŸ”œ Up next

  • Smithery listing
  • Read-only mode flag for shared / multi-user setups

Ideas and PRs welcome β€” see CONTRIBUTING.md.


πŸ“œ License

MIT β€” see LICENSE.

πŸ™ Credits


Security issues? See SECURITY.md for disclosure instructions.

Reviews

No reviews yet

Be the first to review this server!