MCP server that interacts with Obsidian via the Obsidian rest API community plugin
MCP server to interact with Obsidian via the Local REST API community plugin. The server implements multiple tools to interact with Obsidian: listfilesinvault: Lists all files and directories in the root directory of your Obsidian vault listfilesindir: Lists all files and directories in a specific Obsidian directory getfilecontents: Return the content of a single file in your vault. search:…
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
MCP server to interact with Obsidian via the Local REST API community plugin. The server implements multiple tools to interact with Obsidian: listfilesinvault: Lists all files and directories in the root directory of your Obsidian vault listfilesindir: Lists all files and directories in a specific Obsidian directory getfilecontents: Return the content of a single file in your vault. search: Search for documents matching a specified text query across all files in the vault patchcontent: Insert…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.