Adds /search/smart, /templates/execute, PUT /vault-cas/<path> (atomic compare-and-swap write), GET /open/<path>, and GET /ping REST routes to the Local REST API plugin, plus a presence heartbeat for smart-link device detection. Companion plugin for the multi-vault MCP router. No native binary, no telemetry.
This is an Obsidian plugin exposing 6 HTTP routes, not a traditional MCP server. Tool definitions are inferred from route handlers rather than explicitly registered via MCP protocol. Descriptions exist but are verbose and lack LLM-optimized structure. Input schemas are partially visible but inconsistently documented. No output schemas are documented. Error handling and recovery guidance are absent. The plugin bridges to Local REST API, which is a transport layer, not an MCP implementation.
Navigate Obsidian to a vault file (loopback-only, no auth; for clickable http links in chat/terminal contexts where obsidian:// URIs aren't dispatched)
Bare {"pong":true} probe for the smart-link resolver's local-mirror detection (loopback-only, no auth, no data; optional ?v=<name> answers 404 unless <name> matches THIS vault — multi-vault disambiguation, confirmation-only)
Smart environment sources handler for MCP router integration
Smart Connections semantic search via REST API
Templater template execution via REST API
Atomic compare-and-swap write to vault file
No input/output schemas visible for 4 of 6 tools (search/smart, templates/execute, vault-cas, smart-env-sources). Schemas are inferred from route handlers, not explicitly documented.
Descriptions are verbose (100+ chars) and lack LLM-optimized structure. 'Smart Connections semantic search via REST API' (52 chars) is acceptable, but /ping description (200+ chars) buries key details. Baseline: 10 - 1024 chars, optimal 50 - 200.
Tool names use HTTP verbs (POST, PUT, GET) instead of action verbs (search_, execute_, update_, open_). LLMs expect verb_noun naming (e.g. search_smart, execute_template). Route-based naming obscures intent.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 31 | 2026-07-28+ | v2 |
No error handling or recovery guidance documented. Tools do not indicate what to do on failure (retryable? user-fixable? fatal?). No examples of error responses or actionable error messages.
This is an Obsidian plugin, not an MCP server. It exposes HTTP routes via Local REST API plugin, but does not implement the MCP protocol itself. Tool definitions are inferred from route handlers, not registered via MCP.