myhotlunchbox-mcp 0.2.0 → 0.3.0

package/.claude-plugin/marketplace.json

@@ -7,7 +7,7 @@
   },
   "metadata": {
     "description": "MCP server for My Hot Lunchbox — order school lunches, manage students, and track payments via natural language",
-    "version": "0.2.0"
+    "version": "0.3.0"
   },
   "plugins": [
     {
@@ -15,7 +15,7 @@
       "displayName": "My Hot Lunchbox",
       "source": "./",
       "description": "MCP server for My Hot Lunchbox — school lunch calendar, ordering, and payments. Signs in server-side with the parent account credentials.",
-      "version": "0.2.0",
+      "version": "0.3.0",
       "author": {
         "name": "Chris Hall"
       },

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "myhotlunchbox-mcp",
   "displayName": "My Hot Lunchbox",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "MCP server for My Hot Lunchbox — order school lunches, manage students, and track payments via natural language",
   "author": {
     "name": "Chris Hall",

package/README.md

@@ -71,18 +71,38 @@ directory); existing files are never overwritten.
 Every mutating tool takes `confirm`. Without `confirm: true` it makes **no**
 network call and returns a dry-run preview of exactly what it would send.
 
-`mhlb_checkout` charges a real payment method, so it takes one extra safeguard:
-an `expectedTotal` that must match the total in the payment payload. Price the
-cart with `mhlb_init_checkout`, read the total it reports, and pass that figure.
-A stale cart fails closed instead of paying a different amount.
-
-### Unverified writes
-
-The write endpoints' paths, verbs and query parameters were extracted from the
-site's own compiled API client and are reliable. Their **request bodies have not
-been exercised against a live account** — every such tool says so in its
-description. Inspect the dry-run preview before confirming, and re-read the
-resource afterwards: a `200` is not proof a write persisted.
+`mhlb_checkout` charges a real payment method. The server prices the charge from
+`orderIds`, so nothing client-side can bind the amount — there is no total in the
+request to check against. `expectedTotal` is therefore **attribution, not a
+guard**: you state what you expected, and it is recorded in the dry run and in
+the result so an unexpected charge is traceable to the call that made it. What
+the tool does refuse outright is paying a non-zero total with no `orderIds`.
+
+### Writes: shapes captured, acceptance unverified
+
+`npm run capture:writes` runs every mutating tool against a local proxy that
+forwards reads to the real service but answers writes itself, so the payloads
+are built from genuine server models and nothing happens upstream. It also
+proves all 13 refuse to send anything without `confirm: true`.
+
+What that established, and corrected: `mhlb_delete_order` and
+`mhlb_unsubscribe_order` take `{orderId, eventDate, studentId, isRepeated,
+isSubscribed}` — not the order model — and checkout takes
+`{orderIds, checkoutType, couponCode, giftCardCode, schoolDonations}`.
+
+**What is still unverified is whether the server accepts these bodies.** Shape
+is not acceptance; only a real write shows that, and none has been made. Inspect
+the dry-run preview before confirming, and re-read afterwards — a `200` is not
+proof a write persisted.
+
+Two limits on `mhlb_checkout` specifically:
+
+- It can only pay with a card **already saved** on the account. Paying with a
+  new card needs a Stripe token minted by Stripe.js in a browser, which no
+  server-side client can produce.
+- It generates an idempotency key and returns it. If a checkout fails
+  ambiguously, retry with that same `idempotencyKey` rather than a fresh call —
+  that is what stops a retry becoming a second charge.
 
 ## Ordering is read-modify-write
 

package/dist/auth.js

@@ -1,6 +1,7 @@
 import { McpToolError, truncateErrorMessage } from '@chrischall/mcp-utils';
 import { TokenManager } from '@chrischall/mcp-utils/session';
 import { API_PREFIX, OAUTH_SCOPE } from './config.js';
+import { createTokenCache, reportCacheWriteFailure } from './token-cache.js';
 /** Fallback lifetime when the server omits `expires_in`. */
 const DEFAULT_TOKEN_LIFETIME_S = 3600;
 /**
@@ -132,13 +133,24 @@ export class MhlbAuth {
         if (this.loginInFlight)
             return this.loginInFlight;
         this.loginInFlight = (async () => {
-            const body = await this.passwordLogin();
             const manager = new TokenManager({
-                initial: {
-                    accessToken: this.assertAccessToken(body),
-                    refreshToken: body.refresh_token,
-                    expiresAt: MhlbAuth.expiryOf(body),
+                // The FUNCTION form, so the cache is consulted before the password
+                // grant runs at all — the eager object form skips persistence, which
+                // would mean a cache that is written and never read.
+                initial: async () => {
+                    const body = await this.passwordLogin();
+                    return {
+                        accessToken: this.assertAccessToken(body),
+                        refreshToken: body.refresh_token,
+                        expiresAt: MhlbAuth.expiryOf(body),
+                    };
                 },
+                persistence: createTokenCache() ?? undefined,
+                onPersistError: reportCacheWriteFailure,
+                // `refresh` below already recovers from a revoked refresh token by
+                // falling back to a full login, so the library's own re-mint-on-revoked
+                // recovery would only add a third attempt after both have failed.
+                isRefreshRevoked: () => false,
                 refresh: async (refreshToken) => {
                     let next;
                     try {