@leadbay/mcp 0.12.0 → 0.13.0

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog — @leadbay/mcp
 
+## 0.13.0 — 2026-05-21
+
+- **Agent memory v1**: added always-on recall/capture/review tools backed by
+  local append-only JSONL at `~/.leadbay/memory/{account_id}/`.
+- Leads-touching tool responses now attach `_meta.agent_memory.summary` with
+  the consolidated top signals unless `LEADBAY_AGENT_MEMORY=off` is set.
+- Server instructions, prompt descriptions, and workflow prompts now teach the
+  memory protocol, including capture of new taste signals and review-gated
+  retractions.
+- Added `agent-memory://summary` resource and PostHog events for memory
+  capture/recall/prune.
+- **Pin bumps**: every active `@leadbay/mcp@0.12` install/runtime reference in
+  docs, generated client config, DXT, MCP Registry metadata, and Claude plugin
+  metadata is now `@0.13`.
+
+## 0.12.1 — 2026-05-21
+
+MCPB hotfix for Claude Desktop.
+
+- **Fix packaged-server startup**: the MCPB bundle now injects a Node `createRequire` shim before esbuild's ESM wrapper so CommonJS dependencies can still require Node built-ins such as `perf_hooks`. This fixes the Claude Desktop disconnect where the server exited during initialization.
+- **Packaging guardrail**: `@leadbay/dxt build` now runs the staged `server/index.js --version` before zipping, and the smoke suite extracts the MCPB and completes a real MCP initialize/tools-list handshake.
+- **Manifest refresh**: MCPB manifests now declare `manifest_version: "0.3"` and the smoke assertions match the current MCPB manifest spec.
+
 ## 0.12.0 — 2026-05-21
 
 Campaign and field-sales workflow release.

package/README.md

@@ -21,10 +21,31 @@ A Model Context Protocol server that lets Claude Desktop, Cursor, Claude Code, a
 
 > **0.3.0 behavior change** — composite write tools (`refine_prompt`, `report_outreach`, `adjust_audience`, `bulk_qualify_leads`, `enrich_titles`, `answer_clarification`, `import_leads`) are **ON by default**. Set `LEADBAY_MCP_WRITE=0` (or `--no-write` on `install`) to restore the previous read-only behavior. `leadbay-mcp install` now also registers Claude Code at `--scope user` so Leadbay is visible from any project. See [MIGRATION.md](./MIGRATION.md).
 
+## Agent memory
+
+Leadbay MCP keeps a local, per-account agent memory at
+`~/.leadbay/memory/{account_id}/`. It stores append-only JSONL learnings
+about user taste signals such as preferred sectors, regions, deal size,
+communication style, and qualification rules.
+
+The memory tools are always exposed:
+
+- `leadbay_agent_memory_recall` reads the consolidated top signals.
+- `leadbay_agent_memory_capture` appends a new learning after the user reveals
+  a material preference.
+- `leadbay_agent_memory_review` lists entries and gates retractions or org
+  promotion through user confirmation.
+
+The main leads-touching tools (`leadbay_account_status`,
+`leadbay_pull_leads`, `leadbay_pull_followups`,
+`leadbay_prepare_outreach`, `leadbay_research_lead_by_id`) also attach
+`_meta.agent_memory.summary` automatically. Set `LEADBAY_AGENT_MEMORY=off`
+to suppress this ambient metadata.
+
 ## 1. Install (one command)
 
 ```bash
-npx -y @leadbay/mcp@0.12 install --email you@yourcompany.com --region us
+npx -y @leadbay/mcp@0.13 install --email you@yourcompany.com --region us
 # (you'll be prompted for your password — it's not echoed)
 ```
 
@@ -67,14 +88,14 @@ Claude Desktop 2026 ships the DXT (Desktop Extension) system — the legacy `cla
 
 If you installed Node from the official [nodejs.org](https://nodejs.org) `.pkg`, `/usr/local/lib/node_modules` is root-owned. Any of these works:
 
-- **Use `npx` (recommended, no global install):** all examples above use `npx -y @leadbay/mcp@0.12 ...` — no global install needed.
+- **Use `npx` (recommended, no global install):** all examples above use `npx -y @leadbay/mcp@0.13 ...` — no global install needed.
 - **`sudo npm install -g @leadbay/mcp`** (enter your macOS password).
 - **Use a Node version manager** — [nvm](https://github.com/nvm-sh/nvm), [volta](https://volta.sh), [fnm](https://github.com/Schniz/fnm). They install Node under your home directory, so `npm install -g` works without sudo.
 
 ### If you'd rather mint a token without auto-install
 
 ```bash
-npx -y @leadbay/mcp@0.12 login \
+npx -y @leadbay/mcp@0.13 login \
   --email you@yourcompany.com \
   --region us
 ```
@@ -92,7 +113,7 @@ Edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) o
   "mcpServers": {
     "leadbay": {
       "command": "npx",
-      "args": ["-y", "@leadbay/mcp@0.12"],
+      "args": ["-y", "@leadbay/mcp@0.13"],
       "env": {
         "LEADBAY_TOKEN": "<paste-token-from-step-1>",
         "LEADBAY_REGION": "us"
@@ -113,7 +134,7 @@ In Cursor settings, add the MCP server:
   "mcp.servers": {
     "leadbay": {
       "command": "npx",
-      "args": ["-y", "@leadbay/mcp@0.12"],
+      "args": ["-y", "@leadbay/mcp@0.13"],
       "env": { "LEADBAY_TOKEN": "<paste-token>", "LEADBAY_REGION": "us" }
     }
   }
@@ -126,7 +147,7 @@ In Cursor settings, add the MCP server:
 claude mcp add leadbay --scope user \
   --env LEADBAY_TOKEN=<paste-token> \
   --env LEADBAY_REGION=us \
-  -- npx -y @leadbay/mcp@0.12
+  -- npx -y @leadbay/mcp@0.13
 ```
 
 > **`--scope user`** registers Leadbay globally for your account (visible from any project). Without it, `claude mcp add` defaults to project-local scope and the server only appears in conversations opened from the directory where you ran the command.
@@ -138,7 +159,7 @@ claude mcp add leadbay --scope user \
 Before starting Claude, run:
 
 ```bash
-LEADBAY_TOKEN=<paste-token> npx -y @leadbay/mcp@0.12 doctor
+LEADBAY_TOKEN=<paste-token> npx -y @leadbay/mcp@0.13 doctor
 ```
 
 Expected output:
@@ -366,14 +387,14 @@ The user's literal text replaces `verification.ref` in the outreach record, and
 | `No enrichment credits remaining` | Out of quota | Contact Leadbay support to extend quota |
 | Claude Desktop "loading forever" on first use | `npx` cold-start fetching the package | First run takes ~10s. Prefer `npm install -g @leadbay/mcp` for faster startup. |
 | Claude Desktop doesn't show Leadbay tools | Server crashed at startup | Check `~/Library/Logs/Claude/mcp*.log` (macOS) or `%APPDATA%\Claude\logs\mcp*.log` (Windows). |
-| Claude Code can't find Leadbay in a new conversation | MCP server installed at project scope (default before 0.3.0) | Re-run with `--scope user`: `claude mcp remove leadbay && claude mcp add leadbay --scope user --env LEADBAY_TOKEN=… --env LEADBAY_REGION=us -- npx -y @leadbay/mcp@0.12` |
+| Claude Code can't find Leadbay in a new conversation | MCP server installed at project scope (default before 0.3.0) | Re-run with `--scope user`: `claude mcp remove leadbay && claude mcp add leadbay --scope user --env LEADBAY_TOKEN=… --env LEADBAY_REGION=us -- npx -y @leadbay/mcp@0.13` |
 | Agent reports "tool not found" for `refine_prompt` / `adjust_audience` etc. | Pre-0.3.0 install with `LEADBAY_MCP_WRITE` unset (writes were off) | Either re-run `npx @leadbay/mcp install` or remove `LEADBAY_MCP_WRITE=0` from your client config (writes are on by default in 0.3.0+) |
 
 ## 5. Upgrade & rotation
 
-**Upgrade**: change the pinned minor in your config, e.g. `"@leadbay/mcp@0.2"` → `"@leadbay/mcp@0.12"`, then restart the client. **0.3.0 enables composite write tools by default** — see [MIGRATION.md](./MIGRATION.md). See also the [changelog](https://github.com/leadbay/leadclaw/releases).
+**Upgrade**: change the pinned minor in your config, e.g. `"@leadbay/mcp@0.2"` → `"@leadbay/mcp@0.13"`, then restart the client. **0.3.0 enables composite write tools by default** — see [MIGRATION.md](./MIGRATION.md). See also the [changelog](https://github.com/leadbay/leadclaw/releases).
 
-**Rotate token**: re-run `npx -y @leadbay/mcp@0.12 install --email you@yourcompany.com --region us` (or `login`) — the new session token replaces the old one in your MCP client config, and logging in again invalidates the prior session on most session backends.
+**Rotate token**: re-run `npx -y @leadbay/mcp@0.13 install --email you@yourcompany.com --region us` (or `login`) — the new session token replaces the old one in your MCP client config, and logging in again invalidates the prior session on most session backends.
 
 ## 6. Advanced
 
@@ -486,7 +507,7 @@ After your first authenticated call, your PostHog `distinctId` is set to your Le
   "mcpServers": {
     "leadbay": {
       "command": "npx",
-      "args": ["-y", "@leadbay/mcp@0.12"],
+      "args": ["-y", "@leadbay/mcp@0.13"],
       "env": {
         "LEADBAY_TOKEN": "u.…",
         "LEADBAY_REGION": "us",

package/dist/bin.js

@@ -1,6 +1,7 @@
 #!/usr/bin/env node
 import {
   LeadbayClient,
+  agentMemoryTools,
   compositeReadTools,
   compositeWriteTools,
   createClient,
@@ -8,8 +9,9 @@ import {
   formatLoginError,
   granularReadTools,
   granularWriteTools,
+  resolveAgentMemorySummary,
   resolveRegion
-} from "./chunk-J2Y4LCFM.js";
+} from "./chunk-4JLMRGFG.js";
 
 // src/bin.ts
 import { realpathSync } from "fs";
@@ -34,6 +36,11 @@ import {
 
 // src/prompts.generated.ts
 var leadbay_daily_check_in = `
+## MEMORY
+
+Before responding, glance at any \`_meta.agent_memory.summary\` returned by tool calls earlier in this session and reflect its top signals in your reasoning ("Filtering by your stated preference for healthcare"). After any material new taste signal from the user this conversation (sector, region, deal size, communication style, qualification rule, explicit retraction), call \`leadbay_agent_memory_capture\` to persist it: \`source:"user_stated"\` if literal, \`source:"inferred"\` with confidence <=6 if inferred.
+
+
 Run the Leadbay daily check-in for me. Treat this prompt the same way for any equivalent ask focused on NEW leads from the Discover wishlist: "get me leadbay leads", "best NEW leads to prospect today", "what's new today", "show me my batch", "let's prospect". For follow-up phrasings ("what should I follow up on", "leads I've already worked", "before my trip"), this is the wrong prompt \u2014 route to \`leadbay_followup_check_in\` instead. If the user's intent is ambiguous ("what should I work on?"), ASK once before picking an entry point.
 
 # Resilience rules for Leadbay long-running tools
@@ -411,6 +418,11 @@ If I declined the campaign step, end the turn \u2014 the map + drafts are enough
 Done. The map is the surface; the drafts are the action; the campaign is the persistence layer for managerial follow-up after the trip.
 `;
 var leadbay_prospecting_overview = `
+## MEMORY
+
+Before responding, glance at any \`_meta.agent_memory.summary\` returned by tool calls earlier in this session and reflect its top signals in your reasoning ("Filtering by your stated preference for healthcare"). After any material new taste signal from the user this conversation (sector, region, deal size, communication style, qualification rule, explicit retraction), call \`leadbay_agent_memory_capture\` to persist it: \`source:"user_stated"\` if literal, \`source:"inferred"\` with confidence <=6 if inferred.
+
+
 # Leadbay Prospecting \u2014 Orientation
 
 You are working with Leadbay through the \`leadbay_*\` MCP tools. This prompt orients you to the user's mental model so you don't re-discover the workflow each session.
@@ -674,6 +686,11 @@ IRON LAW \u2014 DO NOT ANSWER CLARIFICATIONS ON THE USER'S BEHALF. If the respon
 If the response status is \`applied\`, tell me Leadbay is regenerating intelligence and recommend I check back in a few minutes via \`leadbay_account_status\` (\`computing_intelligence\` flips to false when ready). If the status is anything else, name it explicitly.
 `;
 var leadbay_research_a_domain = `
+## MEMORY
+
+Before responding, glance at any \`_meta.agent_memory.summary\` returned by tool calls earlier in this session and reflect its top signals in your reasoning ("Filtering by your stated preference for healthcare"). After any material new taste signal from the user this conversation (sector, region, deal size, communication style, qualification rule, explicit retraction), call \`leadbay_agent_memory_capture\` to persist it: \`source:"user_stated"\` if literal, \`source:"inferred"\` with confidence <=6 if inferred.
+
+
 IRON LAW \u2014 NO FABRICATION. Every lead id, contact email, custom field id, mapping decision, and tool argument must trace to a value you read from the file the user attached or to an output from a leadbay_* tool call in this session. Do not invent values. Do not "fill in" a missing leadId with a name match. Do not synthesize a CRM id from a guess. If a value is missing, leave the field blank and say so.
 
 
@@ -1219,6 +1236,7 @@ function getPrompt(name, args = {}) {
 var LEAD_URI_RE = /^lead:\/\/([0-9a-f-]{36})\/profile$/i;
 var LENS_URI_RE = /^lens:\/\/(\d+)\/definition$/;
 var ORG_TASTE_URI = "org://taste-profile";
+var AGENT_MEMORY_SUMMARY_URI = "agent-memory://summary";
 function listResources() {
   return [
     {
@@ -1226,6 +1244,12 @@ function listResources() {
       name: "Org taste profile",
       description: "The org's qualification questions, intent tags, and ICP signals \u2014 the agent's knowledge base for what makes a lead a fit.",
       mimeType: "application/json"
+    },
+    {
+      uri: AGENT_MEMORY_SUMMARY_URI,
+      name: "Agent memory summary",
+      description: "Consolidated top Leadbay agent-memory signals for this account. Local-file, read-only resource.",
+      mimeType: "text/markdown"
     }
   ];
 }
@@ -1256,11 +1280,29 @@ function jsonContent(uri, value) {
     ]
   };
 }
+function textContent(uri, mimeType, text) {
+  return {
+    contents: [
+      {
+        uri,
+        mimeType,
+        text
+      }
+    ]
+  };
+}
 async function readResource(uri, client) {
   if (uri === ORG_TASTE_URI) {
     const taste = await client.resolveTasteProfile();
     return jsonContent(uri, taste);
   }
+  if (uri === AGENT_MEMORY_SUMMARY_URI) {
+    const me = await client.resolveMe();
+    const memory = await resolveAgentMemorySummary({
+      accountId: me.organization.id
+    });
+    return textContent(uri, "text/markdown", memory.summary);
+  }
   const leadMatch = LEAD_URI_RE.exec(uri);
   if (leadMatch) {
     const leadId = leadMatch[1];
@@ -1281,7 +1323,7 @@ async function readResource(uri, client) {
     return jsonContent(uri, { lensId, filter, scoring });
   }
   throw new Error(
-    `Unsupported resource URI: ${uri}. Supported schemes: lead://{uuid}/profile, lens://{id}/definition, org://taste-profile.`
+    `Unsupported resource URI: ${uri}. Supported schemes: lead://{uuid}/profile, lens://{id}/definition, org://taste-profile, agent-memory://summary.`
   );
 }
 
@@ -1307,6 +1349,9 @@ var EV_MCP_UPDATE_PROMPTED = "mcp update prompted";
 var EV_MCP_UPDATE_INSTALL_CLICKED = "mcp update install_clicked";
 var EV_MCP_UPDATE_DISMISSED = "mcp update dismissed";
 var EV_MCP_VERSION_UPDATED = "mcp version updated";
+var EV_AGENT_MEMORY_CAPTURED = "agent_memory_captured";
+var EV_AGENT_MEMORY_RECALLED = "agent_memory_recalled";
+var EV_AGENT_MEMORY_PRUNED = "agent_memory_pruned";
 
 // src/telemetry.ts
 var NOOP_TELEMETRY = {
@@ -1320,6 +1365,12 @@ var NOOP_TELEMETRY = {
   },
   captureStartup: () => {
   },
+  captureAgentMemoryCaptured: () => {
+  },
+  captureAgentMemoryRecalled: () => {
+  },
+  captureAgentMemoryPruned: () => {
+  },
   captureException: () => {
   },
   captureUpdateCheck: () => {
@@ -1504,6 +1555,15 @@ function initTelemetry(opts) {
     captureStartup(props) {
       emit(EV_STARTUP, { ...props });
     },
+    captureAgentMemoryCaptured(props) {
+      emit(EV_AGENT_MEMORY_CAPTURED, { ...props });
+    },
+    captureAgentMemoryRecalled(props) {
+      emit(EV_AGENT_MEMORY_RECALLED, { ...props });
+    },
+    captureAgentMemoryPruned(props) {
+      emit(EV_AGENT_MEMORY_PRUNED, { ...props });
+    },
     captureUpdateCheck(props) {
       emit(EV_MCP_UPDATE_CHECK, { ...props });
     },
@@ -1867,6 +1927,7 @@ function buildAcknowledgeUpdateTool(opts) {
 var VERIFICATION_MANDATE = "After every email, call, message, or meeting with a lead's contact, you MUST call leadbay_report_outreach with verification={source, ref} (gmail_message_id from the Gmail send, calendar_event_id from a booking, or user_confirmed='<the user's literal confirmation>'). Skipping or fabricating verification poisons the human team's pipeline.";
 var MENTAL_MODEL_PARAGRAPH = "How Leadbay works (mental model): Leadbay is a sales inbox, not a queryable database. Each day the user logs back in, a fresh batch of leads is delivered. Batch size is paced by how many leads the user has actually acted on recently \u2014 some workflows produce a big stream of smaller prospects, others a narrow stream of bigger ones. Pulling more won't produce more; the user acting on leads (outreach, skips, saves) does.";
 var QUOTA_AND_TOPUP_PARAGRAPH = "Quota & top-ups: when a tool returns QUOTA_EXCEEDED / 429, the user has TWO options \u2014 wait for the window reset (daily / weekly / monthly resets shown in leadbay_account_status), OR top up AI credits (top-ups clear the throttle IMMEDIATELY \u2014 they are not subject to the same window). Always offer BOTH options; default-recommending 'wait until tomorrow' is wrong when a 30-second top-up unblocks the same call. If the host exposes leadbay_create_topup_link, OFFER it on every quota wall: 'Want me to generate a top-up link?' \u2014 when the user says yes, call leadbay_create_topup_link and surface the returned Stripe URL as a clickable link for the user to open in their browser. (Sibling leadbay_open_billing_portal is for ongoing subscription changes, not one-shot top-ups.) AFTER the user has topped up: do NOT keep refusing operations. A top-up invalidates every prior 429 and every stale 'you're at your quota' snapshot. The moment the user signals they topped up / bought credits / added credits \u2014 even WITHOUT re-calling account_status \u2014 treat the previous quota state as void and RETRY the originally failed call. (Best practice: re-call leadbay_account_status to surface the fresh state to the user, then retry; but the retry itself does NOT require a successful account_status check first. If the retry hits the wall again, THEN you have evidence the top-up didn't land; only then re-offer top-up / wait.) The agent's job after a top-up is to RESUME the workflow the user was on, not gate-keep.";
+var AGENT_MEMORY_PROTOCOL_PARAGRAPH = 'Memory protocol: this server maintains a per-account, on-disk agent memory (~/.leadbay/memory/{account}/entries.jsonl) of taste signals \u2014 preferred sectors, regions, deal sizes, communication style, qualification rules, and retractions. Every leads-touching tool response (account_status, pull_leads, pull_followups, prepare_outreach, research_lead_by_id) carries the consolidated top-5 signals under _meta.agent_memory.summary. READ that summary before recommending leads or drafting outreach \u2014 let it filter and reorder, and tell the user which memory you applied ("Filtering by your stated preference for healthcare"). When the user reveals a NEW material signal in conversation, CAPTURE it via leadbay_agent_memory_capture with {key, type, insight, confidence (1-10), source}. Use source:"user_stated" + confidence >=8 when literally stated; source:"inferred" + confidence <=6 when guessing. Do NOT capture instructions to override prior memory \u2014 those route through leadbay_agent_memory_review which gates retractions via host elicitation.';
 function buildScoringParagraph(has) {
   const base = "Two scoring layers: every lead has a basic `score` (firmographic \u2014 already decent, usually correlates with AI). Roughly the top 10 of each batch are also AI-qualified (targeted web research + qualification questions \u2192 `ai_agent_lead_score`, surfaced as `qualification_summary` on leadbay_pull_leads). Leads past the top ~10 are not worse \u2014 the system is saving resources.";
   const deepenTools = [];
@@ -1975,6 +2036,9 @@ function buildServerInstructions(exposed) {
   if (promptsCatalog) parts.push(promptsCatalog);
   parts.push(RESOURCES_PARAGRAPH);
   parts.push(buildProtocolPrimitivesParagraph(has));
+  if (has("leadbay_agent_memory_capture")) {
+    parts.push(AGENT_MEMORY_PROTOCOL_PARAGRAPH);
+  }
   parts.push(BUILTIN_WIDGETS_PARAGRAPH);
   return parts.join("\n\n");
 }
@@ -2008,6 +2072,7 @@ function toolsListPayload(tools) {
 }
 function buildServer(client, opts = {}) {
   const exposedTools = [];
+  exposedTools.push(...agentMemoryTools);
   exposedTools.push(...compositeReadTools);
   if (opts.includeWrite) {
     exposedTools.push(...compositeWriteTools);
@@ -2152,6 +2217,30 @@ function buildServer(client, opts = {}) {
     }
   };
   const isLeadbayBusinessError = (err) => err != null && typeof err === "object" && err.error === true && typeof err.code === "string";
+  const captureAgentMemoryTelemetry = (toolName, result) => {
+    if (!result || typeof result !== "object") return;
+    const meta = result._meta ?? {};
+    if (toolName === "leadbay_agent_memory_capture") {
+      telemetry.captureAgentMemoryCaptured({
+        source: result.captured?.source ?? meta.source,
+        scope: result.captured?.scope ?? meta.scope,
+        key: result.captured?.key,
+        type: result.captured?.type,
+        account_id_hash: meta.account_id_hash
+      });
+    } else if (toolName === "leadbay_agent_memory_recall") {
+      telemetry.captureAgentMemoryRecalled({
+        entries_returned: result.entries_returned,
+        total_active: result.total_active,
+        account_id_hash: meta.account_id_hash
+      });
+    } else if (toolName === "leadbay_agent_memory_review" && result.changed === true && (result.action === "retract" || result.action === "prune")) {
+      telemetry.captureAgentMemoryPruned({
+        action: result.action,
+        account_id_hash: meta.account_id_hash
+      });
+    }
+  };
   server.setRequestHandler(CallToolRequestSchema, async (req, extra) => {
     const callStart = Date.now();
     const name = req.params.name;
@@ -2260,6 +2349,7 @@ function buildServer(client, opts = {}) {
           format: "markdown",
           bytes: mdBytes
         });
+        captureAgentMemoryTelemetry(name, env.structured);
         if (name === "leadbay_create_topup_link" && typeof env.structured?.url === "string") {
           telemetry.captureTopupLink({ tool: name });
         }
@@ -2289,6 +2379,7 @@ function buildServer(client, opts = {}) {
         format: "json",
         bytes: okBytes
       });
+      captureAgentMemoryTelemetry(name, result);
       if (name === "leadbay_create_topup_link" && typeof result?.url === "string") {
         telemetry.captureTopupLink({ tool: name });
       }
@@ -2542,7 +2633,7 @@ async function createDefaultUpdateStateStore(opts = {}) {
 
 // src/bin.ts
 import { createRequire } from "module";
-var VERSION = "0.12.0";
+var VERSION = "0.13.0";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 
@@ -2591,7 +2682,7 @@ EXAMPLE Claude Desktop config (~/Library/Application Support/Claude/claude_deskt
     "mcpServers": {
       "leadbay": {
         "command": "npx",
-        "args": ["-y", "@leadbay/mcp@0.12"],
+        "args": ["-y", "@leadbay/mcp@0.13"],
         "env": {
           "LEADBAY_TOKEN": "lb_...",
           "LEADBAY_REGION": "us",
@@ -2892,7 +2983,7 @@ async function runLogin(args) {
   let result;
   try {
     if (pinnedRegion && !allowFallback) {
-      const { REGIONS } = await import("./dist-YYVFSDMH.js");
+      const { REGIONS } = await import("./dist-LYTGM7OG.js");
       const baseUrl = REGIONS[pinnedRegion];
       const c = createClient({ region: pinnedRegion });
       const token = await loginAt(baseUrl, email, password);
@@ -2911,7 +3002,7 @@ async function runLogin(args) {
     mcpServers: {
       leadbay: {
         command: "npx",
-        args: ["-y", "@leadbay/mcp@0.12"],
+        args: ["-y", "@leadbay/mcp@0.13"],
         env: {
           LEADBAY_TOKEN: result.token,
           LEADBAY_REGION: result.region
@@ -2951,7 +3042,7 @@ Or for Claude Code (token included \u2014 same warning applies):
   claude mcp add leadbay --scope user \\
     --env LEADBAY_TOKEN=${result.token} \\
     --env LEADBAY_REGION=${result.region} \\
-    -- npx -y @leadbay/mcp@0.12
+    -- npx -y @leadbay/mcp@0.13
 
 Restart your MCP client to pick up the new server.
 `
@@ -3057,7 +3148,7 @@ For Claude Code, run:
   claude mcp add leadbay --scope user \\
     --env LEADBAY_TOKEN=$(jq -r .mcpServers.leadbay.env.LEADBAY_TOKEN ${quotedPath}) \\
     --env LEADBAY_REGION=${result.region} \\
-    -- npx -y @leadbay/mcp@0.12
+    -- npx -y @leadbay/mcp@0.13
 `
     );
   }
@@ -3237,7 +3328,7 @@ function buildClaudeCodeAddArgs(token, region, includeWrite, telemetryEnabled) {
     `LEADBAY_TELEMETRY_ENABLED=${telemetryEnabled ? "true" : "false"}`
   ];
   if (!includeWrite) args.push("--env", `LEADBAY_MCP_WRITE=0`);
-  args.push("--", "npx", "-y", "@leadbay/mcp@0.12");
+  args.push("--", "npx", "-y", "@leadbay/mcp@0.13");
   return args;
 }
 async function installInClaudeCode(token, region, includeWrite, telemetryEnabled) {
@@ -3287,7 +3378,7 @@ async function installInJsonConfig(configPath, token, region, includeWrite, tele
     if (!includeWrite) env.LEADBAY_MCP_WRITE = "0";
     parsed.mcpServers.leadbay = {
       command: "npx",
-      args: ["-y", "@leadbay/mcp@0.12"],
+      args: ["-y", "@leadbay/mcp@0.13"],
       env
     };
     const tmp = configPath + ".tmp";
@@ -3391,7 +3482,7 @@ leadbay-mcp install \u2014 detected MCP clients on this machine:
   let region;
   try {
     if (pinnedRegion && !allowFallback) {
-      const { REGIONS } = await import("./dist-YYVFSDMH.js");
+      const { REGIONS } = await import("./dist-LYTGM7OG.js");
       const baseUrl = REGIONS[pinnedRegion];
       token = await loginAt(baseUrl, email, password);
       region = pinnedRegion;
@@ -3464,7 +3555,7 @@ leadbay-mcp install \u2014 detected MCP clients on this machine:
   process.stderr.write(
     `
 The token was written into client config files but never printed to your terminal.
-Verify with: LEADBAY_TOKEN=$(...) npx -y @leadbay/mcp@0.12 doctor
+Verify with: LEADBAY_TOKEN=$(...) npx -y @leadbay/mcp@0.13 doctor
 Restart your MCP client(s) to pick up the new server.
 If you ever leak the token, run \`leadbay-mcp login --email <you> --region <us|fr>\` to mint a fresh one (which invalidates the prior session).
 `