@leadbay/mcp 0.23.8 → 0.23.9

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog — @leadbay/mcp
 
+## 0.23.9 — 2026-06-27
+
+MCP data plane now targets backend **/1.6** (was /1.5).
+
+- **`client`** — every request path is built from a single `API_VERSION = "1.6"` constant (exported as `API_PREFIX`). `LeadbayClient` (request / requestVoid / requestRawBinary + mock-mode paths) and `bin.ts`'s login probe all reference it, so future backend version bumps are a one-line change. Verified live on `api-us` before shipping: `/1.6` mirrors `/1.5` across the full route surface probed (monitor, lenses, auth/login, kpi, geo) — identical status on every call. Tool-description prose and route-doc comments updated to /1.6 to match.
+
 ## 0.23.8 — 2026-06-26
 
 Installer no longer hangs in Claude Cowork / headless terminals (product#3805).

package/dist/bin.js

@@ -68,7 +68,7 @@ async function resolveRegion(email, password, startWith = "us") {
     const baseUrl = REGIONS[region];
     const body = JSON.stringify({ email, password });
     try {
-      const res = await httpsRequest("POST", `${baseUrl}/1.5/auth/login`, { "Content-Type": "application/json" }, body);
+      const res = await httpsRequest("POST", `${baseUrl}${API_PREFIX}/auth/login`, { "Content-Type": "application/json" }, body);
       if (res.status === 200) {
         const parsed = JSON.parse(res.body);
         if (parsed?.token) {
@@ -159,7 +159,7 @@ function parseRetryAfter(value) {
   }
   return null;
 }
-var LENS_CACHE_TTL_MS, TASTE_CACHE_TTL_MS, ME_CACHE_TTL_MS, MAX_CONCURRENT, REGIONS, _mockFixtures, _mockJournal, LeadbayClient;
+var LENS_CACHE_TTL_MS, TASTE_CACHE_TTL_MS, ME_CACHE_TTL_MS, MAX_CONCURRENT, REGIONS, API_VERSION, API_PREFIX, _mockFixtures, _mockJournal, LeadbayClient;
 var init_client = __esm({
   "../core/dist/client.js"() {
     "use strict";
@@ -171,6 +171,8 @@ var init_client = __esm({
       us: "https://api-us.leadbay.app",
       fr: "https://api-fr.leadbay.app"
     };
+    API_VERSION = "1.6";
+    API_PREFIX = `/${API_VERSION}`;
     _mockFixtures = null;
     _mockJournal = [];
     LeadbayClient = class {
@@ -313,7 +315,7 @@ var init_client = __esm({
         const retryOn401 = opts?.retryOn401 !== false;
         await this.acquireSemaphore();
         try {
-          const url = `${this._baseUrl}/1.5${path}`;
+          const url = `${this._baseUrl}${API_PREFIX}${path}`;
           const headers = {
             Authorization: `Bearer ${this.token}`
           };
@@ -348,7 +350,7 @@ var init_client = __esm({
         }
         await this.acquireSemaphore();
         try {
-          const url = `${this._baseUrl}/1.5${path}`;
+          const url = `${this._baseUrl}${API_PREFIX}${path}`;
           const headers = {
             Authorization: `Bearer ${this.token}`
           };
@@ -373,7 +375,7 @@ var init_client = __esm({
       // serialized body (string for text payloads such as CSV; Buffer for binary
       // uploads). Auth, semaphore, error mapping, _lastMeta, and mock-mode all
       // mirror request() exactly. Used by leadbay_import_leads to upload CSVs to
-      // the wizard at POST /1.5/imports.
+      // the wizard at POST /1.6/imports.
       async requestRawBinary(method, path, contentType, body) {
         if (process.env.LEADBAY_MOCK === "1") {
           return this.mockRequestBinary(method, path, contentType, body);
@@ -383,7 +385,7 @@ var init_client = __esm({
         }
         await this.acquireSemaphore();
         try {
-          const url = `${this._baseUrl}/1.5${path}`;
+          const url = `${this._baseUrl}${API_PREFIX}${path}`;
           const headers = {
             Authorization: `Bearer ${this.token}`,
             "Content-Type": contentType
@@ -407,7 +409,7 @@ var init_client = __esm({
         }
       }
       mockRequest(method, path, body) {
-        const fullPath = `/1.5${path}`;
+        const fullPath = `${API_PREFIX}${path}`;
         this._lastMeta = {
           region: this._region,
           endpoint: `${method} ${path}`,
@@ -430,7 +432,7 @@ var init_client = __esm({
         };
       }
       mockRequestBinary(method, path, contentType, body) {
-        const fullPath = `/1.5${path}`;
+        const fullPath = `${API_PREFIX}${path}`;
         this._lastMeta = {
           region: this._region,
           endpoint: `${method} ${path}`,
@@ -5695,7 +5697,7 @@ WHEN TO USE: at the start of a session to know what the agent can/can't do, afte
 
 WHEN NOT TO USE: as a pre-flight gate before bulk ops \u2014 operations themselves return 429; this tool is for context, not gating. And: a recent quota snapshot showing "exhausted" is NOT a reason to refuse a write call when the user has just topped up \u2014 re-call this tool first, then proceed.
 `;
-    leadbay_acknowledge_notification = `Acknowledge a Leadbay notification \u2014 i.e. tell the MCP and the backend "I've seen this and acted on it." Wraps \`POST /1.5/notifications/{id}/seen\` (default) or \`/archive\` (when \`archive:true\`) and drops the entry from the local inbox so subsequent \`_meta.notifications\` payloads stop carrying it.
+    leadbay_acknowledge_notification = `Acknowledge a Leadbay notification \u2014 i.e. tell the MCP and the backend "I've seen this and acted on it." Wraps \`POST /1.6/notifications/{id}/seen\` (default) or \`/archive\` (when \`archive:true\`) and drops the entry from the local inbox so subsequent \`_meta.notifications\` payloads stop carrying it.
 
 **When to call.** After you read an entry from \`_meta.notifications\` or \`account_status.notifications\` and have revised whatever prior output the just-finished background work might have made stale (outreach drafts, lead lists, "available leads" claims, followup plans). Mark-seen tells the human team's pipeline you handled this and prevents the notification from re-surfacing on every subsequent tool response.
 
@@ -6305,7 +6307,7 @@ WHEN NOT TO USE: from agent flow \u2014 leadbay_adjust_audience handles the draf
 
 This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible for confirming intent before invocation; the MCP server does not soft-prompt for confirmation. See \`annotations.destructiveHint\`.
 `;
-    leadbay_create_topup_link = `Generate a one-shot Stripe checkout session for an AI-credits top-up. Wraps \`POST /1.5/stripe/topup_checkout\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL (~1 hour TTL); creating one does NOT charge the user \u2014 payment happens only after the user opens the URL and completes checkout in their browser.
+    leadbay_create_topup_link = `Generate a one-shot Stripe checkout session for an AI-credits top-up. Wraps \`POST /1.6/stripe/topup_checkout\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL (~1 hour TTL); creating one does NOT charge the user \u2014 payment happens only after the user opens the URL and completes checkout in their browser.
 
 **When a quota window is hit, offer top-up as the FIRST option.** A top-up clears the throttle immediately (no need to wait for the daily/weekly/monthly window reset). The flow:
 
@@ -7489,7 +7491,7 @@ follow-ups. On \`ambiguous_sectors\`, the only move is to pick a sector and re-c
 If nothing fits, default to "switch to the new lens and pull leads" \u2014 never
 invent a tool that doesn't exist.
 `;
-    leadbay_open_billing_portal = `Generate a one-shot Stripe customer-portal URL. Wraps \`GET /1.5/stripe/portal\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL the user can open to manage their existing Leadbay subscription: change plan tier, swap payment method, view invoices. The agent does NOT make subscription changes itself \u2014 it surfaces the URL and lets the user act.
+    leadbay_open_billing_portal = `Generate a one-shot Stripe customer-portal URL. Wraps \`GET /1.6/stripe/portal\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL the user can open to manage their existing Leadbay subscription: change plan tier, swap payment method, view invoices. The agent does NOT make subscription changes itself \u2014 it surfaces the URL and lets the user act.
 
 Sibling of \`leadbay_create_topup_link\`. Use cases differ:
 
@@ -7767,7 +7769,7 @@ table. Detail + status priority below.
 
 Pull KNOWN leads from the user's Monitor view \u2014 the re-engagement entry point. Use when the user asks "what should I follow up on", "leads I haven't contacted", "leads in [city]", "before my trip", or any phrasing implying pre-existing pipeline context. For NEW leads from Discover, use \`leadbay_pull_leads\`.
 
-Backend: wraps \`GET /1.5/monitor?personal=&liked=&filtered=&count=&page=\` plus, when \`set_filter\` is supplied, a preceding \`POST /1.5/monitor/filter\`. The Monitor filter is a single \`FilterItem\` per user \u2014 refreshing restores it.
+Backend: wraps \`GET /1.6/monitor?personal=&liked=&filtered=&count=&page=\` plus, when \`set_filter\` is supplied, a preceding \`POST /1.6/monitor/filter\`. The Monitor filter is a single \`FilterItem\` per user \u2014 refreshing restores it.
 
 **Filter mechanism \u2014 store-then-apply.** Pass \`set_filter: { criteria: FilterCriterion[] }\` to overwrite the server-stored filter, then the composite re-fetches with \`filtered:true\`. \`FilterCriterion\` is the backend's \`anyOf\` over 10 typed criteria: \`size\`, \`keywords\`, \`sector_ids\`, \`location_ids\`, \`custom_field\`(\`_comparison\`), \`yc\`, \`liked\`, \`last_action\` (MonitorActionType enum), \`last_action_date\` (with \`last_days\`).
 
@@ -22669,6 +22671,8 @@ var init_artifact_kit = __esm({
 // ../core/dist/index.js
 var dist_exports = {};
 __export(dist_exports, {
+  API_PREFIX: () => API_PREFIX,
+  API_VERSION: () => API_VERSION,
   AgentMemoryCaptureInputSchema: () => AgentMemoryCaptureInputSchema,
   AgentMemoryEntrySchema: () => AgentMemoryEntrySchema,
   AgentMemoryInjectionError: () => AgentMemoryInjectionError,
@@ -27717,7 +27721,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.23.8";
+var VERSION = "0.23.9";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 
@@ -28518,7 +28522,7 @@ async function loginAt(baseUrl, email, password) {
   const https2 = await import("https");
   return await new Promise((resolve, reject) => {
     const body = JSON.stringify({ email, password });
-    const u = new URL(baseUrl + "/1.5/auth/login");
+    const u = new URL(baseUrl + `${API_PREFIX}/auth/login`);
     const r = https2.request(
       {
         hostname: u.hostname,

package/dist/http-server.js

@@ -1592,6 +1592,8 @@ var REGIONS = {
   us: "https://api-us.leadbay.app",
   fr: "https://api-fr.leadbay.app"
 };
+var API_VERSION = "1.6";
+var API_PREFIX = `/${API_VERSION}`;
 function httpsRequest(method, url, headers, body) {
   return new Promise((resolve, reject) => {
     const start = Date.now();
@@ -1647,7 +1649,7 @@ async function resolveRegion(email, password, startWith = "us") {
     const baseUrl = REGIONS[region];
     const body = JSON.stringify({ email, password });
     try {
-      const res = await httpsRequest("POST", `${baseUrl}/1.5/auth/login`, { "Content-Type": "application/json" }, body);
+      const res = await httpsRequest("POST", `${baseUrl}${API_PREFIX}/auth/login`, { "Content-Type": "application/json" }, body);
       if (res.status === 200) {
         const parsed = JSON.parse(res.body);
         if (parsed?.token) {
@@ -1861,7 +1863,7 @@ var LeadbayClient = class {
     const retryOn401 = opts?.retryOn401 !== false;
     await this.acquireSemaphore();
     try {
-      const url = `${this._baseUrl}/1.5${path}`;
+      const url = `${this._baseUrl}${API_PREFIX}${path}`;
       const headers = {
         Authorization: `Bearer ${this.token}`
       };
@@ -1896,7 +1898,7 @@ var LeadbayClient = class {
     }
     await this.acquireSemaphore();
     try {
-      const url = `${this._baseUrl}/1.5${path}`;
+      const url = `${this._baseUrl}${API_PREFIX}${path}`;
       const headers = {
         Authorization: `Bearer ${this.token}`
       };
@@ -1921,7 +1923,7 @@ var LeadbayClient = class {
   // serialized body (string for text payloads such as CSV; Buffer for binary
   // uploads). Auth, semaphore, error mapping, _lastMeta, and mock-mode all
   // mirror request() exactly. Used by leadbay_import_leads to upload CSVs to
-  // the wizard at POST /1.5/imports.
+  // the wizard at POST /1.6/imports.
   async requestRawBinary(method, path, contentType, body) {
     if (process.env.LEADBAY_MOCK === "1") {
       return this.mockRequestBinary(method, path, contentType, body);
@@ -1931,7 +1933,7 @@ var LeadbayClient = class {
     }
     await this.acquireSemaphore();
     try {
-      const url = `${this._baseUrl}/1.5${path}`;
+      const url = `${this._baseUrl}${API_PREFIX}${path}`;
       const headers = {
         Authorization: `Bearer ${this.token}`,
         "Content-Type": contentType
@@ -1955,7 +1957,7 @@ var LeadbayClient = class {
     }
   }
   mockRequest(method, path, body) {
-    const fullPath = `/1.5${path}`;
+    const fullPath = `${API_PREFIX}${path}`;
     this._lastMeta = {
       region: this._region,
       endpoint: `${method} ${path}`,
@@ -1978,7 +1980,7 @@ var LeadbayClient = class {
     };
   }
   mockRequestBinary(method, path, contentType, body) {
-    const fullPath = `/1.5${path}`;
+    const fullPath = `${API_PREFIX}${path}`;
     this._lastMeta = {
       region: this._region,
       endpoint: `${method} ${path}`,
@@ -6824,7 +6826,7 @@ WHEN TO USE: at the start of a session to know what the agent can/can't do, afte
 
 WHEN NOT TO USE: as a pre-flight gate before bulk ops \u2014 operations themselves return 429; this tool is for context, not gating. And: a recent quota snapshot showing "exhausted" is NOT a reason to refuse a write call when the user has just topped up \u2014 re-call this tool first, then proceed.
 `;
-var leadbay_acknowledge_notification = `Acknowledge a Leadbay notification \u2014 i.e. tell the MCP and the backend "I've seen this and acted on it." Wraps \`POST /1.5/notifications/{id}/seen\` (default) or \`/archive\` (when \`archive:true\`) and drops the entry from the local inbox so subsequent \`_meta.notifications\` payloads stop carrying it.
+var leadbay_acknowledge_notification = `Acknowledge a Leadbay notification \u2014 i.e. tell the MCP and the backend "I've seen this and acted on it." Wraps \`POST /1.6/notifications/{id}/seen\` (default) or \`/archive\` (when \`archive:true\`) and drops the entry from the local inbox so subsequent \`_meta.notifications\` payloads stop carrying it.
 
 **When to call.** After you read an entry from \`_meta.notifications\` or \`account_status.notifications\` and have revised whatever prior output the just-finished background work might have made stale (outreach drafts, lead lists, "available leads" claims, followup plans). Mark-seen tells the human team's pipeline you handled this and prevents the notification from re-surfacing on every subsequent tool response.
 
@@ -7434,7 +7436,7 @@ WHEN NOT TO USE: from agent flow \u2014 leadbay_adjust_audience handles the draf
 
 This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible for confirming intent before invocation; the MCP server does not soft-prompt for confirmation. See \`annotations.destructiveHint\`.
 `;
-var leadbay_create_topup_link = `Generate a one-shot Stripe checkout session for an AI-credits top-up. Wraps \`POST /1.5/stripe/topup_checkout\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL (~1 hour TTL); creating one does NOT charge the user \u2014 payment happens only after the user opens the URL and completes checkout in their browser.
+var leadbay_create_topup_link = `Generate a one-shot Stripe checkout session for an AI-credits top-up. Wraps \`POST /1.6/stripe/topup_checkout\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL (~1 hour TTL); creating one does NOT charge the user \u2014 payment happens only after the user opens the URL and completes checkout in their browser.
 
 **When a quota window is hit, offer top-up as the FIRST option.** A top-up clears the throttle immediately (no need to wait for the daily/weekly/monthly window reset). The flow:
 
@@ -8618,7 +8620,7 @@ follow-ups. On \`ambiguous_sectors\`, the only move is to pick a sector and re-c
 If nothing fits, default to "switch to the new lens and pull leads" \u2014 never
 invent a tool that doesn't exist.
 `;
-var leadbay_open_billing_portal = `Generate a one-shot Stripe customer-portal URL. Wraps \`GET /1.5/stripe/portal\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL the user can open to manage their existing Leadbay subscription: change plan tier, swap payment method, view invoices. The agent does NOT make subscription changes itself \u2014 it surfaces the URL and lets the user act.
+var leadbay_open_billing_portal = `Generate a one-shot Stripe customer-portal URL. Wraps \`GET /1.6/stripe/portal\` \u2192 \`{url}\`. Returns a fresh Stripe-hosted URL the user can open to manage their existing Leadbay subscription: change plan tier, swap payment method, view invoices. The agent does NOT make subscription changes itself \u2014 it surfaces the URL and lets the user act.
 
 Sibling of \`leadbay_create_topup_link\`. Use cases differ:
 
@@ -8896,7 +8898,7 @@ table. Detail + status priority below.
 
 Pull KNOWN leads from the user's Monitor view \u2014 the re-engagement entry point. Use when the user asks "what should I follow up on", "leads I haven't contacted", "leads in [city]", "before my trip", or any phrasing implying pre-existing pipeline context. For NEW leads from Discover, use \`leadbay_pull_leads\`.
 
-Backend: wraps \`GET /1.5/monitor?personal=&liked=&filtered=&count=&page=\` plus, when \`set_filter\` is supplied, a preceding \`POST /1.5/monitor/filter\`. The Monitor filter is a single \`FilterItem\` per user \u2014 refreshing restores it.
+Backend: wraps \`GET /1.6/monitor?personal=&liked=&filtered=&count=&page=\` plus, when \`set_filter\` is supplied, a preceding \`POST /1.6/monitor/filter\`. The Monitor filter is a single \`FilterItem\` per user \u2014 refreshing restores it.
 
 **Filter mechanism \u2014 store-then-apply.** Pass \`set_filter: { criteria: FilterCriterion[] }\` to overwrite the server-stored filter, then the composite re-fetches with \`filtered:true\`. \`FilterCriterion\` is the backend's \`anyOf\` over 10 typed criteria: \`size\`, \`keywords\`, \`sector_ids\`, \`location_ids\`, \`custom_field\`(\`_comparison\`), \`yc\`, \`liked\`, \`last_action\` (MonitorActionType enum), \`last_action_date\` (with \`last_days\`).
 
@@ -24014,7 +24016,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.23.8" : "0.0.0-dev";
+var VERSION = true ? "0.23.9" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var sseSessions = /* @__PURE__ */ new Map();

package/dist/installer-electron.js

@@ -1764,7 +1764,7 @@ var init_installer_gui = __esm({
     init_install_dxt();
     init_install_shared();
     init_oauth();
-    VERSION = true ? "0.23.8" : "0.0.0-dev";
+    VERSION = true ? "0.23.9" : "0.0.0-dev";
     MESSAGES = {
       en: {
         installer: {

package/dist/installer-gui.js

@@ -1027,7 +1027,7 @@ async function oauthLogin(opts) {
 }
 
 // installer/installer-gui.ts
-var VERSION = true ? "0.23.8" : "0.0.0-dev";
+var VERSION = true ? "0.23.9" : "0.0.0-dev";
 var MESSAGES = {
   en: {
     installer: {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leadbay/mcp",
-  "version": "0.23.8",
+  "version": "0.23.9",
   "mcpName": "io.github.leadbay/leadbay-mcp",
   "description": "Model Context Protocol (MCP) server for Leadbay — AI lead discovery, qualification, and enrichment for Claude Desktop, Cursor, and Claude Code.",
   "type": "module",