@bli-cockpit/mcp 0.1.45 → 0.1.47

package/README.md

@@ -34,7 +34,7 @@ about what an agent can reach.
 
 <!-- BEGIN GENERATED verb census — `npm run mcp:readme` -->
 
-**94 of 98 Tower verbs have an MCP twin.**
+**94 of 99 Tower verbs have an MCP twin.**
 Each tool goes through the SAME door its CLI verb calls, with the same
 collector device token — never a second route and never a service-role
 reader. `src/verb-census.test.ts` fails when a verb is in none of the
@@ -152,7 +152,8 @@ A claim about the verb's nature, not a backlog.
 | `cockpit brief edit` | opens the person's own $EDITOR on this machine and files what they changed; an agent has no editor to open (commands/editor.ts) |
 | `cockpit cal add-ical` | carries a calendar's SECRET iCal ADDRESS — a permanent, unauthenticated, read-anything-on-that-calendar URL. The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so attaching a calendar stays a thing a person does at a terminal (BLI-3709) |
 | `cockpit mail add-imap` | carries a Google app password. The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so attaching a mailbox stays a thing a person does at a terminal (BLI-3708) |
-| `cockpit notes connect` | carries a notetaker API key (Fathom today, Granola next). The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so connecting a notetaker stays a thing a person does at a terminal or in Tower's Settings (BLI-4383) |
+| `cockpit notes connect` | carries a notetaker API key (Fellow or Circleback). The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so connecting a notetaker stays a thing a person does at a terminal or in Tower's Settings (BLI-4383) |
+| `cockpit notes webhook` | carries the VENDOR's webhook signing secret, the key an HMAC over every delivered payload is checked against. Exactly the ruling `notes connect` already carries, for the same credential shape: the CLI reads it from STDIN so it never lands in an argument list, and an MCP tool argument travels through a model's context window and whatever transcript store sits behind it (BLI-4394) |
 
 <!-- END GENERATED verb census -->
 

package/dist/notes-account-tools.js

@@ -30,10 +30,11 @@ export function registerNotesAccountTools(server, deps) {
     const register = registrarFor(server);
     register("notes_accounts", {
         title: "List connected notetakers",
-        description: "Every notetaker account (Fathom, and later Granola) connected to Tower that you may see: name, provider, "
-            + "health and when it was last read. Start here when you need an account id. Connecting one is NOT available "
-            + "here on purpose — it carries an API key, so it is done at a terminal with `cockpit notes connect "
-            + "--provider fathom --key-stdin` or in Tower's Settings.",
+        description: "Every notetaker account (Fellow or Circleback; Otter and Granola are named but not connectable) connected to "
+            + "Tower that you may see: name, provider, workspace, health and when it was last read. Start here when you "
+            + "need an account id. Connecting one is NOT available here on purpose — it carries an API key, so it is done "
+            + "at a terminal with `cockpit notes connect --provider fellow --workspace <subdomain> --key-stdin` or in "
+            + "Tower's Settings.",
         inputSchema: {},
     }, async () => withSession(deps, async (session) => {
         const response = await callAgentDoor(session, deps.fetchImpl, "GET", "/api/notes/accounts");
@@ -41,7 +42,7 @@ export function registerNotesAccountTools(server, deps) {
             return errorResult(doorFailureText("notes_accounts", response));
         const accounts = (Array.isArray(response.body.accounts) ? response.body.accounts : []);
         return textResult(accounts.length === 0
-            ? "No notetaker is connected. A person connects one with `cockpit notes connect --provider fathom --key-stdin`, or in Tower's Settings."
+            ? "No notetaker is connected. A person connects one with `cockpit notes connect --provider fellow --workspace <subdomain> --key-stdin`, or in Tower's Settings."
             : `${accounts.length} notetaker(s).\n${accounts.map(accountLine).join("\n")}`, { accounts });
     }));
     register("notes_sync", {

package/dist/verb-census.js

@@ -355,7 +355,8 @@ export const TERMINAL_ONLY = {
     "mail add-imap": "carries a Google app password. The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so attaching a mailbox stays a thing a person does at a terminal (BLI-3708)",
     "cal add-ical": "carries a calendar's SECRET iCal ADDRESS — a permanent, unauthenticated, read-anything-on-that-calendar URL. The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so attaching a calendar stays a thing a person does at a terminal (BLI-3709)",
     "brief edit": "opens the person's own $EDITOR on this machine and files what they changed; an agent has no editor to open (commands/editor.ts)",
-    "notes connect": "carries a notetaker API key (Fathom today, Granola next). The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so connecting a notetaker stays a thing a person does at a terminal or in Tower's Settings (BLI-4383)",
+    "notes connect": "carries a notetaker API key (Fellow or Circleback). The CLI reads it from STDIN precisely so it never lands in an argument list; an MCP tool argument travels through a model's context window and whatever transcript store sits behind it, so connecting a notetaker stays a thing a person does at a terminal or in Tower's Settings (BLI-4383)",
+    "notes webhook": "carries the VENDOR's webhook signing secret, the key an HMAC over every delivered payload is checked against. Exactly the ruling `notes connect` already carries, for the same credential shape: the CLI reads it from STDIN so it never lands in an argument list, and an MCP tool argument travels through a model's context window and whatever transcript store sits behind it (BLI-4394)",
 };
 /**
  * Verbs owed a twin, with who owes it. This list should only ever shrink.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bli-cockpit/mcp",
-  "version": "0.1.45",
+  "version": "0.1.47",
   "private": false,
   "description": "bli-tower: an MCP server over BLI Cockpit's agent doors: JARVIS (jarvis_*), documents (docs_*), channels (msg_*), issues (work_*), the daily page (brief_*), meeting notes (notes_*), the ops board (ops_status/slack_*), settings/team/model, Scout and the workbook, plus the legacy event-stream tools (emit_event, get_ticket_timeline, get_active_tickets).",
   "type": "module",