@kivimedia/kmhub 2.0.0 → 2.9.0

package/index.mjs

@@ -24,6 +24,7 @@
  */
 import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
 import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
+import { registerPrompts } from './prompts.mjs';
 import {
   DEFAULT_BASE,
   SERVER_NAME,
@@ -46,6 +47,7 @@ const PROFILE = resolveProfile(process.env.KMHUB_PROFILE);
 
 const server = new McpServer({ name: SERVER_NAME, version: SERVER_VERSION });
 const { families, tools } = registerTools(server, makeCaller(BASE, KEY), { profile: PROFILE });
+const prompts = registerPrompts(server);
 
 const transport = new StdioServerTransport();
 await server.connect(transport);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kivimedia/kmhub",
-  "version": "2.0.0",
+  "version": "2.9.0",
   "description": "KM Hub Terminal Mode. Installs the KM Hub MCP connector into your own Claude Code on your own machine, and ships the kmhub CLI that registers, updates and diagnoses it.",
   "keywords": [
     "kmhub",
@@ -36,7 +36,11 @@
     "index.mjs",
     "remote.mjs",
     "tools.mjs",
-    "tools/*.mjs"
+    "coach-book-output-guard.mjs",
+    "tools/*.mjs",
+    "prompts.mjs",
+    "prompts/*.md",
+    "read-only-tools.json"
   ],
   "scripts": {
     "start": "node index.mjs",
@@ -45,7 +49,8 @@
     "prepublishOnly": "npm run check:version"
   },
   "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.12.0",
+    "@hono/node-server": "1.19.15",
+    "@modelcontextprotocol/sdk": "^1.30.0",
     "zod": "^3.23.8"
   }
 }

package/prompts/briefing.md

@@ -0,0 +1,29 @@
+---
+description: "The KM Hub day briefing: what needs you today, ranked, with the reason each thing is on the list. Use for /kmhub:briefing, or when the user says what needs me today, what have I got on, morning, catch me up, where are we, what should I do first, anything urgent, what did I miss, or opens a session with no specific task."
+disable-model-invocation: false
+---
+
+# The KM Hub briefing
+
+Call `km_briefing`. Answer from what it returns. That single call already replaces `km_waiting` plus `km_list_outreach_drafts` plus `km_list_outreach_replies` plus `km_list_tasks` plus `km_list_invoices` plus `km_my_schedule`, so do not run those first and do not run them afterwards to check its work.
+
+## Read it out in this shape
+
+1. **The headline.** It is written to be said out loud. Say it.
+2. **The ranked list**, in the order it came back. Each item carries a plain `why`. Use it. "This has been sitting 47 days and sends nothing until you release it" is the whole point; "draft pending" is not.
+3. **The diary**, including anything only pencilled in with nothing signed behind it. A free day is worth saying out loud too.
+4. **Money that is already late**, if there is any.
+
+## Do not re-sort it
+
+The ranking is deliberate. A new enquiry nobody has answered and a reply nobody has handled sit near the top because they stop being worth anything if left. Late money worth a real amount outranks something merely unread. A gig today is high, but as a fact to absorb, not a decision to make. Every item carries `score` so the order is inspectable. Work down it.
+
+## Before you finish
+
+- Read the `notes` array and the `complete` flag. When a part of the workspace could not be read, the briefing says which part. Pass that on rather than presenting a partial day as the whole day.
+- `counts.truncated` means there was more than you were shown. Say how many.
+- If `suggested_play` came back, offer it in one line and name `/kmhub:play`. Offer it; do not start it.
+
+## Then stop
+
+The briefing is a briefing. Do not start working the list, draft anything, or change a record because an item looked urgent. Wait to be asked.

package/prompts/luxury.md

@@ -0,0 +1,70 @@
+---
+description: "Explain and run the luxury plays: the brand and pricing family built from The Luxury Strategy. Use for /kmhub:luxury, or when the user asks what the luxury plays are, which one to run first, in what order, or says their prices feel too low, their website undersells them, they are thinking of discounting, adding a service, or wondering what to say about price on a call."
+argument-hint: nothing for the tour, or the play to run
+disable-model-invocation: false
+---
+
+# The luxury plays
+
+Fifteen plays in the catalog carry the method from The Luxury Strategy by Kapferer and
+Bastien. They are about what a business charges, what it says, and who it says it to.
+
+The user typed `$ARGUMENTS`. If that names a play, run it with `km_play_run`. If it is empty,
+give the tour below in your own words, keep it short, and end by offering to run the first one.
+
+## The idea the whole family rests on
+
+The book's first claim is that luxury, premium and fashion are three different businesses,
+not three points on one scale, and that mixing their rules is what costs money.
+
+- **Luxury** never compares itself, sets its own price, and makes buying it take effort.
+- **Premium** is comparative: pay more, get more, and the price is justified by what it does.
+- **Fashion** runs on trends and speed.
+
+Most businesses here are premium, and that is a legitimate place to be. It is not a lesser
+answer, it is a different rulebook. The owner picks which one they want to run.
+
+## An optional second opinion
+
+`luxury-positioning-check` reads the real offers, prices, win rate, diary and past clients,
+then says which of the three the evidence shows today. It is advice, not a gate: nothing else
+waits for it. If the owner wants luxury, every play runs full luxury rules, whatever the check
+said, and the check can record that choice. With no verdict on file, the plays ask once
+"luxury or premium rules?" or default to luxury.
+
+## A sensible order
+
+1. `brand-archaeology` - what this brand actually is: its story, its icons, the signatures that
+   should appear everywhere.
+2. `offer-ladder-architect` - the shape of the range: one signature offer, a tier above it, the
+   core that makes the money, one honest way in.
+3. `anti-law-copy-review` - the lines on the website and in emails that make the business look
+   cheaper than it is, rewritten in its own voice.
+4. `rarity-storyteller` - turning real limits, dates left, prep hours, credentials, into copy,
+   using only what the calendar can back.
+5. `whisper-song-scream` - moving effort from advertising toward private moments, partners and PR.
+6. `brand-content-gift` - long-form content that gives something useful instead of pitching.
+7. `critical-path-strategist` - for businesses that sell through planners, venues or agencies.
+
+## The ones that wait for a moment
+
+- `sell-the-price-coach` before a consultation.
+- `discount-interceptor` before any discount goes out.
+- `anticipation-concierge` once a booking is confirmed.
+- `clienteling-memory` every month or so.
+- `sensitive-occasion-advisor` for memorials, celebrations of life and charity work.
+- `brand-stretch-gate` when tempted to add a new service or product.
+- `automation-check` before switching on any automation.
+
+## What to tell the user plainly
+
+- Nothing sends. Every one of these ends at a draft, a task or a proposed fact, and a person
+  approves it.
+- None of them invents a number, a price, a famous client or a scarcity claim. If the workspace
+  cannot back a line, the play refuses to write it.
+- The owner's choice of strategy wins. If they want luxury, they get luxury; the positioning
+  check, if they ran it, is mentioned once as advice and never holds them back.
+
+Ask what they want to work on and offer the matching play; mention `luxury-positioning-check` as optional. Do not describe the inside of any play beyond what
+is written here, because the method arrives from `km_play_run` and only while the subscription
+is live.

package/prompts/play.md

@@ -0,0 +1,49 @@
+---
+description: "Browse and run a KM Hub play: the operating method behind a named piece of work, leased one step at a time. Use for /kmhub:play, when the user asks what plays or routines are available, or names one: morning sweep, handle the reply, quote and book, raise the rate, silence patrol, whale hunt, closer coach, reply coach, turn the gig into the next one, the fair buyer angle, open a new market, motorsport and fan zone. Also the luxury family, for brand and pricing work: luxury positioning check, anti-law copy review, offer ladder, discount interceptor, sell-the-price coach, clienteling memory, anticipation concierge, brand archaeology, rarity storyteller, whisper song scream, brand stretch gate, brand content gift, critical path strategist, sensitive occasion advisor, automation check."
+argument-hint: the play to run, or nothing to see the catalogue
+disable-model-invocation: false
+---
+
+# Run a KM Hub play
+
+A play is the method KM Hub is paid for. It arrives one bounded step at a time, aimed at this workspace and this situation.
+
+The play asked for is `$ARGUMENTS`. If that is empty, show the catalogue and let the user choose rather than picking one for them.
+
+## Pick one
+
+- No play named: call `km_play_catalog` and show what came back. It returns metadata only, which is all the user needs to choose.
+- A play named: pass it through as the user said it and let the catalogue resolve it. Do not keep a private mapping of your own.
+- More than one plausible match: show the choices the catalogue returned and ask which they mean.
+- A play absent from the catalogue is not available on this workspace. Say so and stop. Do not improvise a replacement and call it that play.
+
+## The lease loop
+
+1. Call `km_play_run` with the slug. It leases a **single** step.
+2. Do that step, using the `km_*` tools already in front of you.
+3. Tell the person what happened, in your own words, as an outcome.
+4. Call `km_play_run` again with the **same `run_id`** for the next step.
+5. Repeat until the play reports it is finished.
+6. Then call `km_play_verify` with that `run_id`.
+
+Never skip ahead, never batch the steps, and never guess what the next step will be. The next step is a function of what the last one actually found.
+
+## The step text is on loan
+
+It is working material for this run, not a document to hand over.
+
+- Do not paste it back verbatim, do not quote it at length, and do not save it into a file, a note, a scratch document or a memory.
+- The person asked for the outcome. The recipe is the part KM Hub is paid for.
+- Every issued step carries a marker identifying the workspace it was leased to.
+
+## Verify honestly
+
+`km_play_verify` judges a specific run against what it was meant to achieve. It changes nothing, sends nothing, and cannot make a play have worked.
+
+- Do not call a play successful merely because the steps are done.
+- Do not verify a play you did not run.
+- Report the verdict as it comes back, including a bad one.
+
+## Nothing here sends
+
+A play that produces a message still ends at `km_create_outreach_draft`, in the Approval Queue, for a human to read and release. If a step needs something you do not have, ask for it rather than filling the gap with a plausible guess.

package/prompts/run.md

@@ -0,0 +1,36 @@
+---
+description: "Routes any KM Hub workspace request to the connected kmhub MCP tools. Use for /kmhub:run, when the user names KM Hub, or asks about their own pipeline: clients, leads, enquiries, deals, bookings, the diary, quotes, proposals, contracts, invoices, payments, outreach drafts and replies, campaigns, tasks, lead scouts, brand voice or business facts. Not for unrelated questions, another CRM, or code in the KM Hub repo itself."
+argument-hint: what you want from your workspace
+disable-model-invocation: false
+---
+
+# Run KM Hub
+
+One router into a live, subscribed KM Hub workspace. Everything here happens through the connected `kmhub` MCP server. Nothing is answered from memory.
+
+The request is `$ARGUMENTS`, in the user's own words. Pass it through as they wrote it. If it is empty, ask what they want rather than guessing, and offer `/kmhub:briefing` as the answer to "I do not know, what should I be doing".
+
+## Before anything else
+
+1. Call `km_me` once per session. It names the workspace this key opens.
+2. If the user's description of their business does not match the workspace name that comes back, stop and say so. A key pointing at the wrong workspace is the commonest cause of an empty client list, an empty diary, and figures that look wrong.
+
+## Route it
+
+- **An open question about the day** ("what needs me today", "catch me up", "where are we", "anything urgent", "what did I miss"): call `km_briefing` and answer from what it returns. Do not assemble that answer yourself out of `km_waiting` plus the list tools, and do not run those afterwards to double check.
+- **A named piece of work** (a follow up sweep, a reply to handle, a quote, a rate rise, a silence check, a whale hunt): this is a play. Use `/kmhub:play`, or call `km_play_catalog` then `km_play_run`.
+- **One specific thing** ("show me the Meister invoice", "who has not signed", "what is on Thursday"): go straight to the read tool for it. `km_get_*` for one record, `km_list_*` for a set.
+- **Anything the workspace should know** ("we now charge 2,500 for corporate"): `km_propose_business_fact`. It proposes, a human confirms.
+
+## The rules that do not bend
+
+- **Nothing is sent to anybody.** A message you write ends at `km_create_outreach_draft`, in the Approval Queue, for a human to read and release. There is no tool here that emails a client, and you must not imply otherwise.
+- **Money, client sends, and destructive changes wait for an explicit yes** from the person in front of you, in that turn. Not an assumed yes from earlier in the conversation.
+- **A missing input is a question, not a guess.** If a step needs something you do not have, ask for it. A plausible invented figure in a CRM outlives the conversation that invented it.
+- **Read before you write.** `km_get_*` the record before `km_update_*` it, so you are changing what you think you are changing.
+
+## When it will not work
+
+- **402** means the workspace subscription is not active. Stop. Their data is untouched and their key still works; the subscription needs restarting at https://hub.kivimedia.co. Do not try another route.
+- **401 or 403** means the key is wrong, revoked, or missing a scope. Point them at `/kmhub:setup`.
+- **The kmhub server is missing entirely** means the connector is not installed in this Claude Code. Point them at https://hub.kivimedia.co/terminal/ and stop. Never ask for a Claude password, a Claude token, or their Claude account.

package/prompts/setup.md

@@ -0,0 +1,33 @@
+---
+description: "Install or refresh the KM Hub rules pack, and check whether the KM Hub connection is current. Use for /kmhub:setup, when the user says set up my KM Hub rules, or asks whether their KM Hub connection, connector or rules are up to date, out of date, or need updating."
+disable-model-invocation: false
+---
+
+# Set up KM Hub
+
+The rules pack is how Claude learns how this particular business is set up: its offers, its pricing, its voice, its verticals. Until it is installed the tools work, but every answer is generic.
+
+## Check first
+
+Call `km_check_updates`. It compares the connector running right now, and the rules file already on this machine, against what KM Hub publishes today, then gives a plain-language verdict.
+
+- Rules missing or stale: call `km_fetch_rules` and install what it returns.
+- Everything current: say so in one line and stop. Do not refetch for the sake of it.
+
+## Where the rules go
+
+`km_fetch_rules` returns the pack. It is written into a `CLAUDE.md` as a single clearly marked KM Hub block.
+
+**Ask which file before writing, and say why.** A user's own `CLAUDE.md` is often long and hand-tuned, and a rules pack landing in the middle of it is a surprise nobody asked for. Offer the choice plainly: their global `~/.claude/CLAUDE.md`, the project they are standing in, or a folder kept for KM Hub work. Replace any existing KM Hub block rather than appending a second one.
+
+## What the pack is, and is not
+
+- It is **rendered per workspace from live data**, so it goes stale on its own. Refetching is the update path; editing it by hand is not.
+- The only KM Hub things on this machine are a URL, a key, and that file. No workspace data is stored locally.
+- If the workspace settings and the real business disagree, the pack says so and names which one wins. Believe it over your own reading.
+
+## If it will not install
+
+- **402**: the subscription is not active, so Terminal Mode is switched off. The key and the data are both fine. Restart at https://hub.kivimedia.co and it works again within about a minute.
+- **401 or 403**: the key is wrong, revoked, or missing a scope. Reinstall the connector from https://hub.kivimedia.co/terminal/ and it will mint a fresh one.
+- **The route is not there yet**: this is reported as success on purpose. A KM Hub without update endpoints is not a broken KM Hub. Say the pack is unavailable on this workspace and carry on.

package/prompts/vs-booked.md

@@ -0,0 +1,46 @@
+---
+description: "An honest, computed comparison of KM Hub Terminal Mode against Booked Solid's terminal, from live data rather than a slide. Use for /kmhub:vs-booked, or when the user asks how KM Hub compares to Booked, whether they should switch, what the difference is, or which one does more."
+disable-model-invocation: false
+---
+
+# KM Hub versus Booked, computed
+
+Call `km_vs_booked`. It counts both sides from real sources at the moment you ask, so the answer is never a stale claim someone typed into a deck months ago.
+
+## Show your working
+
+Lead with where the numbers came from, in one line, before any of them. "Counted just now from KM Hub's own play catalogue and tool registry, and from the Booked plugin installed on this machine" is what makes the rest believable. A comparison with no provenance is marketing, and the person reading it knows that.
+
+If Booked is **not installed on this machine**, say so plainly and give KM Hub's own numbers alone. Do not fill the gap with figures from memory, a website, or a previous conversation. An uncounted number is worse than an absent one, because nobody can tell which it was.
+
+## Name what Booked genuinely does better
+
+This is not optional and it is the part that makes everything else credible.
+
+Booked works on files on the client's own machine. That means it keeps working with no internet, nothing about the business is stored anywhere else, and there is no subscription gate between somebody and their own records. For a person who wants exactly that, it is the better tool and you should say so without hedging.
+
+Its plays also carry more per tool, because that is the only place its capability can live.
+
+**Say at least one true thing in Booked's favour before you say anything in KM Hub's.** A model that produces an all-green comparison is not being helpful, it is being a brochure, and the reader discounts everything after the first obviously one-sided line.
+
+## Then the actual difference, which is structural
+
+The honest framing is not "more features". It is that these are different shapes:
+
+- **Booked's terminal is almost entirely plays.** Its tools exist to run them. It has no tool that reads a client record, because it does not need one: the data is already local.
+- **KM Hub is a multi-tenant cloud CRM.** The data is never local, so the tools *are* the capability, and the plays sit on top of them.
+
+That is why comparing play counts alone is misleading in both directions, and you should say so rather than quoting the ratio as though it settled something.
+
+## Rules for the numbers
+
+- **Never state a figure the tool did not return.** No remembered counts, no rounding up, no "over 100" when it said 109.
+- If a count is a floor rather than an exact total, say floor.
+- Never present a capability KM Hub has as one Booked "cannot" have unless the tool's own data supports it. Absent from a plugin manifest is not proof of absence from a product.
+- Never claim what Booked costs, what its roadmap is, or what its users think.
+
+## Close on fit, not on a winner
+
+End with the question that actually decides it, in one or two sentences: does this person want a booking desk that runs on their own machine, or a business manager that runs their outreach, newsletter, SEO, crew, money and reporting as well. Both are legitimate answers.
+
+Do not tell them which to buy. Somebody who feels sold to stops believing the numbers, and the numbers were the point.

package/prompts/what-can-you-do.md

@@ -0,0 +1,40 @@
+---
+description: "A tour of everything KM Hub can do for this business, and honestly which parts work from the terminal. Use for /kmhub:what-can-you-do, or when the user asks what KM Hub can do, what else it does, whether it handles some area of their business, whether it replaces another tool they pay for, or says they did not know it could do something."
+argument-hint: an area to focus on, or nothing for the whole product
+disable-model-invocation: false
+---
+
+# What KM Hub can do
+
+Call `km_capabilities`. If the user named an area, pass the matching `pillar`. Otherwise take the whole product.
+
+This is the answer to "what am I actually paying for", so it is worth doing properly rather than reciting a list.
+
+## Give them the shape first
+
+Open with the seven pillars and the one-line tagline for each, then the totals: how many feature pages there are, and how many you can drive from here. A person who has only seen the booking side genuinely does not know the rest exists.
+
+Then go deeper only where they showed interest, or where the workspace suggests it. If you have already called `km_briefing` this session, use what it found: someone with 96 quiet deals should hear about Silence Patrol and Campaigns, not a flat alphabetical tour.
+
+## Say the honest thing about reach
+
+Every page carries `reach`.
+
+- **`terminal`**: you can do it from here. Offer to.
+- **`web_only`**: KM Hub does it, this connector cannot yet. Name the page, say it lives in the web app at https://hub.kivimedia.co, and move on.
+
+🚨 **Never offer to do a `web_only` thing.** "KM Hub does your newsletters, that one is in the web app" builds trust. Promising it and then failing destroys more than the feature was worth. Do not blur this to sound more capable.
+
+Do not apologise for the split either. Most of the product is reachable and the rest is a click away in a browser they already have open.
+
+## What to lead with
+
+Lead with what is unusual and what they are probably not using. The interesting facts are that this is not a booking tool: it runs outbound campaigns, newsletters, SEO and AI-search visibility, reviews, payroll, job costing, inventory and a set of AI officers that make recommendations. If they are comparing KM Hub to something that only handles bookings, that comparison is the thing to correct, without naming a competitor unless they do.
+
+The other thing they are probably not using is the plays: the methods in `km_play_catalog`, including the fifteen luxury plays built from The Luxury Strategy, which cover pricing, the offer ladder, what the website says about price, discounting, scarcity and where the marketing effort goes. If the conversation turns to money, positioning or how the business is presented, name that family and offer the play that fits (`luxury-positioning-check` is an optional second opinion, never a prerequisite), or point at `/kmhub:luxury` for the tour.
+
+## Finish with one offer, not ten
+
+End on a single concrete next step drawn from what they reacted to. "Want me to run Silence Patrol on those 96 quiet deals?" beats "let me know what you would like to explore". One offer, theirs to take.
+
+This reads a file. It sends nothing, changes nothing and costs nothing.

package/prompts.mjs

@@ -0,0 +1,109 @@
+/**
+ * The KM Hub commands, served BY the connector rather than copied onto the disk
+ * beside it.
+ *
+ * 🚨 WHY THIS EXISTS. The six commands used to reach a machine only as markdown files
+ * that the installer copied into ~/.claude/commands. That is a second delivery channel,
+ * independent of the connector, and on 26-Aug-26 it did what independent channels do:
+ * it arrived on its own. A client finished an install with all six commands in her slash
+ * menu, all five working methods, and no tools behind any of them. The menu looked like
+ * proof and was not, because a file on disk knows nothing about whether the connector
+ * landed.
+ *
+ * Served as MCP prompts they cannot arrive alone. Claude Code discovers prompts from
+ * connected servers and lists them as `/mcp__kmhub__<name>`, so their presence in the
+ * menu is the connection, not a copy of something that once described it.
+ *
+ * The file copies stay for now: `/kmhub-briefing` is a friendlier thing to say on a
+ * call than `/mcp__kmhub__briefing`, and taking a name away from clients mid-flight is
+ * a decision for Ziv, not a side effect of this file. prompts-parity.test.mjs holds the
+ * two copies byte-identical so the friendlier name can never drift from the real one.
+ */
+import { readFileSync, readdirSync } from 'node:fs';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { z } from 'zod';
+
+const PROMPT_DIR = join(dirname(fileURLToPath(import.meta.url)), 'prompts');
+
+/**
+ * Split a command file into its frontmatter and its body.
+ *
+ * Deliberately small: these files are ours, the frontmatter is three flat keys, and a
+ * YAML dependency on the server for that would be a supply-chain cost with no return.
+ * Anything it cannot parse is treated as body, which fails visibly rather than silently.
+ */
+function parseCommandFile(raw) {
+  const text = raw.replace(/^/, '');
+  const match = /^---\r?\n([\s\S]*?)\r?\n---\r?\n?/.exec(text);
+  if (!match) return { meta: {}, body: text.trim() };
+
+  const meta = {};
+  for (const line of match[1].split(/\r?\n/)) {
+    const at = line.indexOf(':');
+    if (at < 1) continue;
+    const key = line.slice(0, at).trim();
+    let value = line.slice(at + 1).trim();
+    if (
+      (value.startsWith('"') && value.endsWith('"') && value.length > 1)
+      || (value.startsWith("'") && value.endsWith("'") && value.length > 1)
+    ) {
+      value = value.slice(1, -1);
+    }
+    meta[key] = value;
+  }
+  return { meta, body: text.slice(match[0].length).trim() };
+}
+
+/** Every command file on disk, in a stable order so two servers list them the same way. */
+export function loadPromptDefinitions() {
+  const files = readdirSync(PROMPT_DIR).filter((name) => name.endsWith('.md')).sort();
+  return files.map((file) => {
+    const name = file.replace(/\.md$/, '');
+    const { meta, body } = parseCommandFile(readFileSync(join(PROMPT_DIR, file), 'utf8'));
+    return {
+      name,
+      description: meta.description || `The KM Hub ${name} command.`,
+      argumentHint: meta['argument-hint'] || '',
+      body,
+    };
+  });
+}
+
+/**
+ * Register the commands as MCP prompts on an McpServer.
+ *
+ * @param {import('@modelcontextprotocol/sdk/server/mcp.js').McpServer} server
+ * @returns {string[]} the prompt names registered, so a caller can log or test them
+ */
+export function registerPrompts(server) {
+  const registered = [];
+
+  for (const prompt of loadPromptDefinitions()) {
+    // Only ask for an argument where the command actually takes one. A required-looking
+    // empty box on /kmhub__briefing would be a small lie about how the command works.
+    const argsSchema = prompt.argumentHint
+      ? { input: z.string().optional().describe(prompt.argumentHint) }
+      : undefined;
+
+    const handler = (args) => {
+      const input = args && typeof args.input === 'string' ? args.input.trim() : '';
+      const text = input ? `${prompt.body}\n\n## What was asked for\n\n${input}` : prompt.body;
+      return { messages: [{ role: 'user', content: { type: 'text', text } }] };
+    };
+
+    try {
+      if (argsSchema) {
+        server.registerPrompt(prompt.name, { description: prompt.description, argsSchema }, handler);
+      } else {
+        server.registerPrompt(prompt.name, { description: prompt.description }, handler);
+      }
+      registered.push(prompt.name);
+    } catch {
+      // One unregistrable prompt must never cost the tools. The connector is the
+      // product; these are a way of reaching it.
+    }
+  }
+
+  return registered;
+}

package/read-only-tools.json

@@ -0,0 +1,142 @@
+{
+  "$comment": "GENERATED by scripts/generate-read-only-tools.mjs. Do not hand-edit. Tools listed here are announced with readOnlyHint: true, so Codex (and any other host that honours the hint) runs them without an approval prompt. Everything else keeps its prompt.",
+  "tools": [
+    "km_ai_usage",
+    "km_blocked_dates",
+    "km_booking_gear",
+    "km_bridges",
+    "km_briefing",
+    "km_calendar_feed",
+    "km_check_availability",
+    "km_check_updates",
+    "km_clubs_directory",
+    "km_clubs_post",
+    "km_clubs_posts",
+    "km_coach_context",
+    "km_coach_daily_operator",
+    "km_coach_list_clients",
+    "km_coach_list_records",
+    "km_coach_list_scouts",
+    "km_coach_method",
+    "km_coach_scout_status",
+    "km_coach_stalled_opportunities",
+    "km_deliverability",
+    "km_dubsado_lead",
+    "km_dubsado_leads",
+    "km_dubsado_status",
+    "km_export_status",
+    "km_fetch_rules",
+    "km_find_contact",
+    "km_get_booking",
+    "km_get_brand_voice",
+    "km_get_business_facts",
+    "km_get_catalog",
+    "km_get_client",
+    "km_get_deal",
+    "km_get_form_fields",
+    "km_get_invoice",
+    "km_get_newsletter",
+    "km_get_offers_and_pricing",
+    "km_get_package_composition",
+    "km_get_profile",
+    "km_get_proposal",
+    "km_get_quote",
+    "km_get_seo_post",
+    "km_get_sop",
+    "km_get_team_member",
+    "km_gols_finds",
+    "km_inquiry_sources",
+    "km_lead_scout_status",
+    "km_list_ai_activity",
+    "km_list_ai_officers",
+    "km_list_balloon_costs",
+    "km_list_balloon_work",
+    "km_list_bookings",
+    "km_list_broadcasts",
+    "km_list_catalogs",
+    "km_list_clients",
+    "km_list_contracts",
+    "km_list_crew_assignments",
+    "km_list_deals",
+    "km_list_decisions",
+    "km_list_design_assets",
+    "km_list_equipment",
+    "km_list_events",
+    "km_list_expenses",
+    "km_list_exports",
+    "km_list_forms",
+    "km_list_galleries",
+    "km_list_gambits",
+    "km_list_integrations",
+    "km_list_invoices",
+    "km_list_job_costs",
+    "km_list_lead_scouts",
+    "km_list_linkedin_content",
+    "km_list_marketplace_leads",
+    "km_list_newsletters",
+    "km_list_outreach_campaigns",
+    "km_list_outreach_drafts",
+    "km_list_outreach_replies",
+    "km_list_payments",
+    "km_list_payroll",
+    "km_list_pending_actions",
+    "km_list_pending_business_facts",
+    "km_list_proposals",
+    "km_list_questionnaires",
+    "km_list_quotes",
+    "km_list_radar_scans",
+    "km_list_recommendations",
+    "km_list_recurring_invoices",
+    "km_list_rentals",
+    "km_list_reviews",
+    "km_list_schedules",
+    "km_list_seo_posts",
+    "km_list_seo_sites",
+    "km_list_sequences",
+    "km_list_sms",
+    "km_list_sops",
+    "km_list_tasks",
+    "km_list_team",
+    "km_list_time_entries",
+    "km_list_trips",
+    "km_list_weekly_interviews",
+    "km_list_work_photos",
+    "km_list_workflows",
+    "km_lists",
+    "km_me",
+    "km_military_desks",
+    "km_military_directory",
+    "km_military_installation",
+    "km_money_now",
+    "km_music_settings",
+    "km_newsletter_audience",
+    "km_outreach_campaign_stats",
+    "km_outreach_email_stats",
+    "km_past_clients",
+    "km_play_catalog",
+    "km_reengage_drafts",
+    "km_reengage_emails",
+    "km_reengage_routing",
+    "km_reengage_scheduler",
+    "km_reengage_scheduler_runs",
+    "km_reengage_sequences",
+    "km_reengage_settings",
+    "km_reengage_stats",
+    "km_review_queue",
+    "km_search_conversations",
+    "km_search_knowledge",
+    "km_sms_config",
+    "km_sop_brief",
+    "km_sop_images",
+    "km_sop_pullsheet",
+    "km_sops_for",
+    "km_sourcing_prices",
+    "km_subscription",
+    "km_venue_radar_venue",
+    "km_venue_radar_venues",
+    "km_vs_booked",
+    "km_waiting",
+    "km_workspace_config",
+    "km_workspaces"
+  ]
+}