vault-cortex 0.2.2 → 0.2.3

package/dist/messages.js

@@ -33,19 +33,30 @@ Connect your MCP client:
   URL:        http://localhost:${port}/mcp
   ${tokenLine}
 
-OAuth clients (Claude Desktop, Claude Code, most MCP clients):
-  1. Add the URL above as a remote MCP server, leaving Client
-     ID/Secret empty ("remote" = HTTP — the server still runs on
-     your machine)
+Claude Code:
+  1. claude mcp add --transport http vault-cortex http://localhost:${port}/mcp
   2. Approve the browser consent page with the token above
-  3. Done — the client holds auto-refreshing access tokens; the
+  3. Done. The client holds auto-refreshing access tokens; the
      token never sits in client config
 
+Claude Desktop only accepts https URLs in its connector dialog, so
+register the server in claude_desktop_config.json via the mcp-remote
+bridge instead:
+  "vault-cortex": {
+    "command": "npx",
+    "args": ["-y", "mcp-remote", "http://localhost:${port}/mcp",
+      "--header", "Authorization: Bearer <token above>"]
+  }
+
+Other OAuth clients (Cursor, most MCP clients) add the URL above as a
+remote MCP server, leaving Client ID/Secret empty ("remote" = HTTP —
+the server still runs on your machine), then approve the consent page.
+
 Clients without OAuth, scripts, and curl send the token directly:
   curl -H "Authorization: Bearer <token>" http://localhost:${port}/mcp
 
-Note: claude.ai (web) cannot reach localhost — use Claude Desktop or
-Claude Code for a local server.
+Note: claude.ai (web) cannot reach localhost — use Claude Code for local
+access, or Claude Desktop with the mcp-remote bridge.
 
 Smoke test:
   curl http://localhost:${port}/healthz
@@ -71,6 +82,14 @@ export const buildRemoteConnectMessage = (params) => {
     const approveLine = tokenWritten
         ? `approve with your MCP_AUTH_TOKEN:\n  ${token}`
         : `approve with the existing MCP_AUTH_TOKEN in ${targetDir}/.env`;
+    const httpUrlWarning = publicUrl.startsWith("https://")
+        ? ""
+        : `
+
+Note: claude.ai and Claude Desktop only accept https URLs — set up
+HTTPS when you're ready for those clients (see the HTTPS section in
+the remote guide). Claude Code works with http:
+  claude mcp add --transport http vault-cortex ${publicUrl}/mcp`;
     // Flush-left on purpose: template literals keep leading whitespace, so
     // indenting these lines would indent the rendered output.
     const connectMessage = `${startLine}
@@ -80,7 +99,7 @@ Connect your MCP client:
 
 OAuth clients (Claude Desktop, Claude Code, claude.ai): add a remote MCP
 server with that URL and leave Client ID/Secret empty — a consent page
-opens; ${approveLine}
+opens; ${approveLine}${httpUrlWarning}
 
 Optional settings (timezone, memory folder, port, logging, sync
 behavior) are commented out in ${targetDir}/.env — uncomment, set a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vault-cortex",
-  "version": "0.2.2",
+  "version": "0.2.3",
   "description": "Set up a Vault Cortex MCP server for your Obsidian vault in one command: npx vault-cortex init",
   "license": "MIT",
   "type": "module",

package/templates/local/docker-compose.yml

@@ -6,6 +6,8 @@
 # 1. cp .env.example .env   (then fill in MCP_AUTH_TOKEN and VAULT_PATH)
 # 2. docker compose up
 # 3. Connect your MCP client to http://localhost:8000/mcp
+#    (Claude Desktop's connector dialog requires https — register a
+#    localhost server via the mcp-remote bridge; see the local README)
 #
 # Full docs: https://github.com/aliasunder/vault-cortex