@cpenned/mcp 0.9.1 → 0.11.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cpenned/mcp",
-  "version": "0.9.1",
+  "version": "0.11.0",
   "description": "MCP server for Open Brain - a thin adapter over the /v1 HTTP API.",
   "type": "module",
   "license": "MIT",
@@ -31,6 +31,7 @@
   "main": "./dist/index.js",
   "files": [
     "dist",
+    "dist-ui",
     "skills",
     "README.md",
     "LICENSE"
@@ -39,19 +40,20 @@
     "access": "public"
   },
   "scripts": {
-    "build": "node scripts/bundle-skills.mjs && tsc -p tsconfig.json",
-    "typecheck": "tsc -p tsconfig.json --noEmit",
+    "build": "node scripts/bundle-skills.mjs && node scripts/build-ui.mjs && tsc -p tsconfig.json",
+    "typecheck": "tsc -p tsconfig.json --noEmit && tsc -p ui/tsconfig.json",
     "test": "vitest run",
     "start": "node dist/index.js",
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@mcp-ui/server": "^6.1.0",
+    "@modelcontextprotocol/ext-apps": "^1.7.5",
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.6.7"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",
+    "esbuild": "^0.27.0",
     "typescript": "^5.6.0",
     "vitest": "^4.1.8"
   }

package/skills/open-brain-mcp/SKILL.md

@@ -222,10 +222,16 @@ pre-guessing constraints.
 - **AI**: `find_tasks` (hybrid keyword + semantic search), `ai_triage`
   (brain dump → garden-assigned tasks, recurring habits, reading-list
   saves/edits/cancels, and books - see Workflows).
-- **UI (read-only)**: `ui_view`, `ui_review_queue`, `ui_garden_board`,
-  `ui_habits` return `ui://` HTML resources. `ui_view` and `ui_habits` take a
-  `cursor`; when a page is cut short the result adds a text note with the
-  cursor for the next page.
+- **Cards (MCP Apps)**: in hosts that render MCP Apps, these tools also show
+  an interactive card: `get_task` / `create_task` / `update_task` (task card:
+  Done, Defer to tomorrow, Open), `get_view` (agenda, tick to complete),
+  `create_tasks` and `ai_triage` (what was created, with Undo), `get_reviews`
+  (Reviewed / Contacted), `list_habits` (check in for today) and
+  `review_garden` (board by status). The JSON result is unchanged, so keep
+  reading it. When the user acts on a card, a model-context note says what
+  changed; trust it over the earlier result and don't redo the action. To
+  show the user a list visually, call the matching tool rather than pasting
+  a long text list. (The old `ui_*` tools are gone.)
 - **Settings**: `get_settings`, `update_settings` (the default review period
   applied to new tasks/projects; `defaultReviewInterval: null` disables it;
   `defaultTimezone`, an IANA string, is also settable - it's what date-only
@@ -241,6 +247,15 @@ pre-guessing constraints.
   `notifications: {emailOnMention, emailOnAssign}`), `update_profile
   {displayName?, notifications?: {emailOnMention?, emailOnAssign?}}` (pass at
   least one; display name 1-60 chars; avatar upload is web-only).
+- **History** (every write from every surface, with before/after values):
+  `list_history` (filters `entityType`, `entityId`, `source`, `actor`,
+  `since`/`until` as epoch ms or ISO date/time, `batchId`, `limit` 1-200
+  default 50, `cursor`; newest first, `{ items, hasMore, nextCursor }`),
+  `get_history_entry {id}`, `revert_change {id}` or `revert_change
+  {batchId}` (plus `force?`). Entries carry `summary` (human line),
+  `actor`, `source`, `at`, `fields`, `before`/`after` (changed fields only;
+  a missing key means unset), `batchId`, `revertOf`, `revertedBy`,
+  `revertable`. See the undo workflow below.
 - **Keys**: `create_key` (optional `includeGrants` to let the new key see
   gardens shared with its owner - only settable if the calling key itself
   has it), `list_keys`, `rotate_key`, `revoke_key`. `rotate_key` and
@@ -331,6 +346,21 @@ pre-guessing constraints.
   link it to a person at the same time, pass `tagIds`/`personIds` inline
   instead of following up with separate calls.
 
+- **Undo a change** → `list_history` filtered by `entityId` (or `since`)
+  to find the entry, check `revertable`, then `revert_change {id}`. A bulk or
+  multi-entity action shares one `batchId`; undo all of it with
+  `revert_change {batchId}`. Update reverts write `before` back only for
+  fields whose current value still equals `after`; fields edited since come
+  back as `conflicts` (`{field, expected, current}`) and are left alone.
+  Show the user the conflicts and only re-run with `force: true` if they want
+  them overwritten. Reverting a create soft-deletes (tasks/projects
+  canceled, gardens/people/habits archived, books/reading/Strava deleted;
+  tags and saved lists are hard-deleted), reverting a delete restores (a
+  hard-deleted tag/saved list returns under `newEntityId`), tag/link
+  add/remove invert. The result is `{ batchId, results, entries }` with a
+  per-entity `status` (`reverted`, `partial`, `conflict`, `noop`,
+  `skipped`). To redo, revert the returned `batchId`.
+
 ## Gotchas
 
 - Tools act on the vault behind the configured API key. If the user's web tasks
@@ -339,7 +369,10 @@ pre-guessing constraints.
 - Scopes gate tools: resource tools need `<resource>:read|write` (people tools
   `people:read|write`, settings tools `settings:read|write`, reading list tools
   `reading:read|write`, Strava tools `strava:read|write`, book tools
-  `books:read|write`, calendar tools `calendar:read|write`), review tools
+  `books:read|write`, calendar tools `calendar:read|write`), history tools
+  `history:read` (rows only for entity types the key can also read) and
+  `revert_change` `history:write` plus the write scope of each entity it
+  touches, review tools
   `reviews:*`, `find_tasks` needs `ai:invoke` + `tasks:read`, `ai_triage` needs
   `ai:invoke` + `tasks:write`, `reading:write`, `habits:write`, and
   `books:write` (it can create any of those), the `*_key` tools need `keys:manage`. A missing scope returns a
@@ -348,6 +381,10 @@ pre-guessing constraints.
   web-only flow, `POST /v1/uploads` before setting `coverStorageId`), but a
   key used for that flow needs `books:write` alongside `tasks:write`/
   `projects:write`.
+- `revert_change` fails with a 400 "Invalid revert" for changes that are not
+  revertable (`revertable: false`: system rows, recurrence spawns, settings,
+  keys, webhooks, attachments, oversized values). Check the flag before
+  offering an undo.
 - `sync_strava_activities` requires a Strava account already connected (via
   the web UI's Settings page) — it does nothing useful if nobody has
   authorized the app yet.