coddingtonbear/obsidian-local-rest-api

MCPcommunity
coddingtonbearMITUpdated 4mo agoGitHub

A secure REST API and Model Context Protocol (MCP) server for your vault.

Give your scripts, browser extensions, and AI agents a direct line into your Obsidian vault via a secure, authenticated REST API. Interactive API docs: Access your vault through the REST API or the built-in MCP server — both interfaces expose the same core capabilities, so scripts, browser extensions, and AI agents all speak the same language. Read, create, update, or delete notes — full CRUD on…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
2kGitHub stars
297Forks
4mo agoLast update
Package
Authorcoddingtonbear
LicenseMIT
Sourcegithub
GitHubcoddingtonbear/obsidian-local-rest-api
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface19 tools · 4 privileged
Security scan✓ CleanvHEAD · 3mo 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

19 tools · 4 privileged
Statically extracted from the published packagevHEAD · 3mo 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.

my_toolNo description published

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

vault_listNo description published

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

custom_toolNo description published

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

removable_toolNo description published

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

vault_readNo description published

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

vault_writeprivilegedNo description published

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

vault_appendNo description published

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

vault_patchNo description published

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

vault_deleteprivilegedNo description published

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

vault_moveNo description published

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

vault_get_document_mapNo description published

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

active_file_get_pathNo description published

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

periodic_note_get_pathNo description published

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

search_queryNo description published

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

search_simpleNo description published

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

tag_listNo description published

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

command_listprivilegedNo description published

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

command_executeprivilegedNo description published

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

open_fileNo description published

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

0 of 19 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

Give your scripts, browser extensions, and AI agents a direct line into your Obsidian vault via a secure, authenticated REST API. Interactive API docs: Access your vault through the REST API or the built-in MCP server — both interfaces expose the same core capabilities, so scripts, browser extensions, and AI agents all speak the same language. Read, create, update, or delete notes — full CRUD on any file in your vault, including binary files Surgically patch specific sections — target a…

Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · 4 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

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.

Topics

Related in notes & productivity