# You see the error message in the top right hand corner? Do I still need to worry ## Retrieval Notes - Session id: `14204f2f-2591-4ae2-b26a-4d9f247220dc` - Last activity: `2026-02-27T08:32:32.366Z` ## My Notes <!-- Add your notes here. This section is preserved across syncs. --> ## Conversation ### User You see the error message in the top right hand corner? Do I still need to worry about this? I think if I'm using the Obsidian CLI, I don't need to be worrying about Smart Connections and Smart Searching the API in the first place. Is that right? ### Assistant I need to check your knowledge base to understand your current semantic search setup and whether this error matters. ### Assistant **You're absolutely right.** You don't need the Smart Search REST API Plugin at all. Your system uses **Smart Connections directly via MCP** (Model Context Protocol on port 27124). The `/semantic-search` and `/research-query` skills call Smart Connections through MCP, not through a REST API. The "Smart Search REST API Plugin" is a **separate community plugin** that wraps Smart Connections in a REST API. It's redundant for your setup and causing this error because it's looking for something it doesn't need. **What to do:** 1. Disable or uninstall the "Smart Search REST API Plugin" from Community Plugins 2. Keep Smart Connections itself (you need that) 3. The MCP integration will continue working fine The error will disappear and nothing will break — your semantic search commands will work exactly as they do now. *Hai capito perfettamente: l'errore riguarda un plugin superfluo che cerca di fare da ponte verso qualcosa che già usi direttamente.* ### User "Your system uses Smart Connections directly via MCP (Model Context Protocol on port 27124). The /semantic-search and /research-query skills call Smart Connections through MCP, not through a REST API." could this dunt be done by the CLI? The Obsidian CLI instead now? ### Assistant Good question! Let me think about this... The Obsidian CLI's `eval` command **can** access plugin instances, including Smart Connections. So theoretically, yes - you could call Smart Connections' semantic search methods directly via CLI instead of going through MCP. Let me check what Smart Connections exposes: ### Assistant Ah, interesting discovery: **Smart Connections isn't running as an Obsidian plugin in your setup** - that's why it's accessible via MCP instead. ### Assistant **No, the CLI can't replace MCP here** because Smart Connections isn't running as an Obsidian plugin in your setup. Looking at your enabled plugins, Smart Connections isn't in the list. What's happening: - **Smart Connections is installed** (you saw it in the plugin list) - **But not enabled as a plugin** (not in the enabled list above) - **Instead, it's running as an MCP server** (on port 27124) This is actually the **modern architecture** for Smart Connections: - Runs as standalone MCP server (external process) - Claude Code connects to it via MCP protocol - Independent of Obsidian's plugin system - Provides clean API interface **The CLI approach would require:** 1. Smart Connections to be enabled as an Obsidian plugin 2. Then you could `eval` its methods 3. But you'd lose the MCP architecture **Stick with MCP** - it's cleaner, more robust, and already working. The CLI is excellent for Obsidian-native features (metadata, workspace, files), but Smart Connections is designed to run as an MCP server. *La tua architettura usa Smart Connections come server esterno, non come plugin interno — per questo MCP è necessario e il CLI non può sostituirlo.*