mcp-obsidian

MCPcommunity
v1.0.0Henry MaoUnknownUpdated 1y agonpm

Model Context Protocol server for Obsidian Vaults

This is a connector to allow Claude Desktop (or any MCP client) to read and search an Obsidian vault. This will also work for any Markdown directory. Make sure Claude Desktop is installed. Then, simply modify your Claude Desktop config locationed here: /Library/Application\ Support/Claude/claudedesktopconfig.json If you don't have this config, you can create an empty file at this location. Add…

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1y agoLast update
Package
AuthorHenry Mao
LicenseUnknown
Version1.0.0
Sourcenpm
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies38 resolved · 1 with advisories
Tool surface2 tools · none privileged
Security scan⚠ Warnings (1)v1.0.0 · 1mo agoHow well does this scan work?
EvalsNone
IndexedMay 24, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev1.0.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

read_notesNo description published

This tool published no description. Forge does not invent one.

search_notesNo description published

This tool published no description. Forge does not invent one.

0 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

This is a connector to allow Claude Desktop (or any MCP client) to read and search an Obsidian vault. This will also work for any Markdown directory. Make sure Claude Desktop is installed. Then, simply modify your Claude Desktop config locationed here: /Library/Application\ Support/Claude/claudedesktopconfig.json If you don't have this config, you can create an empty file at this location. Add the following to the mcpServers array, replacing <path-to-your-vault> with the path to your Obsidi

Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in notes & productivity