things-mcp-server 0.1.0 → 0.1.2

package/README.md

@@ -67,30 +67,6 @@ Or in development:
 THINGS_AUTH_TOKEN=your_token_here pnpm dev
 ```
 
-## MCP Config (Local Source Checkout)
-
-This repository includes `mcp.config.example.json` for running the built local server:
-
-```json
-{
-  "mcpServers": {
-    "things": {
-      "command": "/opt/homebrew/bin/node",
-      "args": ["/Users/your-user/Code/things-mcp/dist/index.js"],
-      "env": {
-        "THINGS_AUTH_TOKEN": "your-token-here"
-      }
-    }
-  }
-}
-```
-
-Notes:
-
-- Run `pnpm build` first so `dist/index.js` exists.
-- Update `args[0]` to your actual local absolute path.
-- Keep `command` aligned with the same Node runtime used for install/build to avoid `better-sqlite3` ABI mismatch.
-
 ## Publish and Install (No Source Checkout)
 
 You can publish to npm and run it via `npx`, so client machines do not need this source repo.
@@ -118,7 +94,7 @@ MCP config example (installed on demand from npm):
 }
 ```
 
-Optional SQLite read path override:
+Optional SQLite read path override (only when auto-discovery fails):
 
 ```bash
 THINGS_DB_PATH="/Users/you/Library/Group Containers/JLMPQHK86H.com.culturedcode.ThingsMac/ThingsData-XXXX/Things Database.thingsdatabase/main.sqlite"
@@ -138,15 +114,16 @@ If `lastOpenError` includes `NODE_MODULE_VERSION` mismatch:
 
 1. Align Node runtime used by MCP host and by local install.
 2. Rebuild native module with that runtime: `pnpm rebuild better-sqlite3`.
-3. In MCP host config, prefer absolute Node path in `command` (for example `/opt/homebrew/bin/node`) instead of plain `node`.
+3. If you run via `npx`, make sure your MCP host resolves `npx/node` from the same runtime version used to install/rebuild dependencies.
+4. Restart the MCP host and reconnect the client.
 
 ## Tool Safety Notes
 
 - `things_add_area`, `things_add_todo`, `things_add_project`, `things_update_todo`, `things_complete_todo`, `things_move_todo`, and `things_delete_todo` all require `confirm=true`.
 - This server does not execute arbitrary scripts.
 - Reads are done via AppleScript.
-- URL-scheme-supported operations use Things URL scheme (`add_todo`, `add_project`, `update_todo`, `move_todo`, `complete_todo`, `show_item`).
-- AppleScript is used for unsupported write operations (`add_area`, `delete_todo`) and read operations.
+- URL-scheme-supported operations use Things URL scheme (`add_todo`, `add_project`, `move_todo`, `complete_todo`, `show_item`), and `update_todo` when heading placement is requested.
+- AppleScript is used for read operations, plus write operations `add_area`, `delete_todo`, and most `update_todo` cases.
 
 ## Read Detail Fields
 

package/dist/services/things-service.js

@@ -120,10 +120,18 @@ export class ThingsService {
         if (input.headingId) {
             assertThingsId(input.headingId);
         }
-        await this.urlSchemeAdapter.updateTodo(input);
+        const requiresUrlScheme = input.heading !== undefined || input.headingId !== undefined;
+        if (requiresUrlScheme) {
+            await this.urlSchemeAdapter.updateTodo(input);
+            return {
+                ok: true,
+                message: "Todo update request sent to Things via URL scheme."
+            };
+        }
+        await this.appleScriptAdapter.updateTodo(input);
         return {
             ok: true,
-            message: "Todo update request sent to Things via URL scheme."
+            message: "Todo updated via AppleScript."
         };
     }
     async completeTodo(input) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "things-mcp-server",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "MCP server for controlling Things on macOS",
   "type": "module",
   "main": "dist/index.js",