$ loading_
Securely manage and sync Obsidian vault content with path-scoped permissions.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "fenced-obsidian-sync-mcp" yet — see the docs or source repo.
Design a least-privilege configuration for my Obsidian MCP server: only allow listing and reading Markdown files under /projects/**, and forbid create, edit, delete, and access to other folders. Provide the capability set and security notes.
A least-privilege configuration defining allowed paths, permitted actions, and security boundaries.
Help me plan Obsidian MCP permissions: allow creating and updating documents under /team/wiki/**, but disallow deletion; allow read-only access to /team/archive/**. Output the recommended tool registration scope and permission notes.
A folder-based permission plan explaining which actions are registered and which remain unavailable by default.
Review this Obsidian MCP capability configuration for violations of the deny-by-default principle. Identify overly broad path scopes, excessive permissions, or unnecessary tools, and suggest tighter alternatives.
A permission audit highlighting risks and recommending safer, tighter configuration changes.
Let AI search and edit local Obsidian Markdown notes directly.
Enable AI to read and write Obsidian vaults in local or headless setups.
Connect to and manage an Obsidian vault for searching, editing, and organizing notes.
Securely access GitHub-backed Obsidian vaults from MCP clients via OAuth.
Connect to Obsidian vaults to read, search, and precisely edit notes.
Securely let AI read, write, search, and scrape content for Obsidian notes.