@leadbay/mcp 0.37.0 → 0.38.0

package/CHANGELOG.md

@@ -1,5 +1,20 @@
 # Changelog — @leadbay/mcp
 
+## 0.38.0 — 2026-09-10
+
+`leadbay_account_status` now returns `mcp_version`, the version of the server
+answering the call, on every call and on both the stdio and hosted servers.
+
+Before this, an agent asked "what version of Leadbay are you running" had no
+answer. The version reached the host only in `initialize`'s `serverInfo`, which
+hosts keep out of the model's context, and in
+`update_available.current_version`, which exists only while an update is
+pending and never on hosted (`http-server.ts` wires no update store).
+
+The server wrapper sets the field next to `update_available`; the composite's
+`outputSchema` declares it, and the description gains a routing trigger and one
+sentence telling the agent to answer version questions with it.
+
 ## 0.37.0 — 2026-09-08
 
 Expose the backend MCP-first delivery endpoints (`POST /1.6/mcp/search`,

package/dist/bin.js

@@ -1599,7 +1599,7 @@ account resurfaced:
 `;
     leadbay_account_status = `## WHEN TO USE
 
-Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
+Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits", "what version of Leadbay am I running".
 
 Do NOT use for: "show me leads" \u2192 \`leadbay_pull_leads\`.
 
@@ -1608,6 +1608,7 @@ Prefer when: meta question about account, quota, active lens, or top-up recovery
 Examples that SHOULD invoke this tool:
 - "What's my account status?"
 - "How much quota do I have left this week?"
+- "Which version of the Leadbay connector is this?"
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "Show me today's leads."
@@ -1633,6 +1634,8 @@ Show the user's account state \u2014 admin rights, language, last-active lens, q
 
 **After a user tops up, do NOT keep refusing \u2014 RETRY.** If the user signals they topped up / bought credits / added credits, the previous QUOTA_EXCEEDED is invalidated the moment the Stripe webhook lands. RE-CALL \`leadbay_account_status\` to pick up the new state AND retry the originally failed call. The retry itself does not require a successful account_status check first \u2014 a topped-up user has cleared the throttle whether or not your cached snapshot reflects it yet. If the retry hits the wall again, only then re-offer top-up / wait. **A stale quota snapshot is never a reason to gate-keep a topped-up user.**
 
+**\`mcp_version\`** is the version of the Leadbay MCP server answering the call. When the user asks which Leadbay version they are running, answer with it.
+
 **\`notifications\` block.** The response now includes a top-level \`notifications\` array listing background work the user (or agent) initiated that has since completed (\`bulk_enrich\`, \`bulk_qualify\`, \`import\`). These are signals to revise prior agent outputs the just-finished work might have made stale \u2014 they're NOT a pending-task list for the user. After revising (or confirming nothing is affected), call \`leadbay_acknowledge_notification(notification_id)\`. Full handling protocol below.
 
 ## GATE \u2014 INSPECT \`_meta.notifications\` ON EVERY RESPONSE
@@ -6946,7 +6949,7 @@ This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible
     NO_COMMERCE_TOOL_DESCRIPTIONS = {
       leadbay_account_status: `## WHEN TO USE
 
-Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
+Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits", "what version of Leadbay am I running".
 
 Do NOT use for: "show me leads" \u2192 \`leadbay_pull_leads\`.
 
@@ -6955,6 +6958,7 @@ Prefer when: meta question about account, quota, active lens, or top-up recovery
 Examples that SHOULD invoke this tool:
 - "What's my account status?"
 - "How much quota do I have left this week?"
+- "Which version of the Leadbay connector is this?"
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "Show me today's leads."
@@ -6976,6 +6980,8 @@ Show the user's account state \u2014 admin rights, language, last-active lens, q
 
 **After a user tops up, do NOT keep refusing \u2014 RETRY.** If the user signals they topped up / bought credits / added credits, the previous QUOTA_EXCEEDED is invalidated the moment the Stripe webhook lands. RE-CALL \`leadbay_account_status\` to pick up the new state AND retry the originally failed call. The retry itself does not require a successful account_status check first \u2014 a topped-up user has cleared the throttle whether or not your cached snapshot reflects it yet. **A stale quota snapshot is never a reason to gate-keep a topped-up user.**
 
+**\`mcp_version\`** is the version of the Leadbay MCP server answering the call. When the user asks which Leadbay version they are running, answer with it.
+
 **\`notifications\` block.** The response now includes a top-level \`notifications\` array listing background work the user (or agent) initiated that has since completed (\`bulk_enrich\`, \`bulk_qualify\`, \`import\`). These are signals to revise prior agent outputs the just-finished work might have made stale \u2014 they're NOT a pending-task list for the user. After revising (or confirming nothing is affected), call \`leadbay_acknowledge_notification(notification_id)\`. Full handling protocol below.
 
 ## GATE \u2014 INSPECT \`_meta.notifications\` ON EVERY RESPONSE
@@ -17796,6 +17802,11 @@ var init_account_status = __esm({
               agent_memory: { type: "object" }
             }
           },
+          // Set by the MCP server wrapper (NOT this composite) on every call.
+          mcp_version: {
+            type: "string",
+            description: "Version of the Leadbay MCP server answering this call. Answer 'what version of Leadbay are you running' with this value."
+          },
           // Auto-update block. Populated by the MCP server wrapper (NOT this
           // composite) when a newer release is published on GitHub AND the
           // user hasn't suppressed it. When present, the agent should prompt
@@ -29136,6 +29147,9 @@ ${url}
         }) === true
       }));
       await maybeAttachUpdate(name, result);
+      if (name === "leadbay_account_status" && result !== null && typeof result === "object" && !Array.isArray(result) && result.error !== true) {
+        result.mcp_version = serverVersion;
+      }
       maybeAttachNotifications(result);
       if (result && typeof result === "object" && result.error === true) {
         const envText = formatErrorForLLM(result);
@@ -30787,7 +30801,7 @@ var OAUTH_BASE_URLS = {
     fr: "https://staging.api.leadbay.app"
   }
 };
-var VERSION = "0.37.0";
+var VERSION = "0.38.0";
 var HELP = `
 leadbay-mcp ${VERSION} \u2014 Leadbay Model Context Protocol server
 

package/dist/http-server.js

@@ -4545,7 +4545,7 @@ account resurfaced:
 `;
 var leadbay_account_status = `## WHEN TO USE
 
-Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
+Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits", "what version of Leadbay am I running".
 
 Do NOT use for: "show me leads" \u2192 \`leadbay_pull_leads\`.
 
@@ -4554,6 +4554,7 @@ Prefer when: meta question about account, quota, active lens, or top-up recovery
 Examples that SHOULD invoke this tool:
 - "What's my account status?"
 - "How much quota do I have left this week?"
+- "Which version of the Leadbay connector is this?"
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "Show me today's leads."
@@ -4579,6 +4580,8 @@ Show the user's account state \u2014 admin rights, language, last-active lens, q
 
 **After a user tops up, do NOT keep refusing \u2014 RETRY.** If the user signals they topped up / bought credits / added credits, the previous QUOTA_EXCEEDED is invalidated the moment the Stripe webhook lands. RE-CALL \`leadbay_account_status\` to pick up the new state AND retry the originally failed call. The retry itself does not require a successful account_status check first \u2014 a topped-up user has cleared the throttle whether or not your cached snapshot reflects it yet. If the retry hits the wall again, only then re-offer top-up / wait. **A stale quota snapshot is never a reason to gate-keep a topped-up user.**
 
+**\`mcp_version\`** is the version of the Leadbay MCP server answering the call. When the user asks which Leadbay version they are running, answer with it.
+
 **\`notifications\` block.** The response now includes a top-level \`notifications\` array listing background work the user (or agent) initiated that has since completed (\`bulk_enrich\`, \`bulk_qualify\`, \`import\`). These are signals to revise prior agent outputs the just-finished work might have made stale \u2014 they're NOT a pending-task list for the user. After revising (or confirming nothing is affected), call \`leadbay_acknowledge_notification(notification_id)\`. Full handling protocol below.
 
 ## GATE \u2014 INSPECT \`_meta.notifications\` ON EVERY RESPONSE
@@ -9892,7 +9895,7 @@ This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible
 var NO_COMMERCE_TOOL_DESCRIPTIONS = {
   leadbay_account_status: `## WHEN TO USE
 
-Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits".
+Trigger phrases: "what's my account status", "how much quota do I have", "what lens am I on", "I topped up / I bought credits / I added credits", "what version of Leadbay am I running".
 
 Do NOT use for: "show me leads" \u2192 \`leadbay_pull_leads\`.
 
@@ -9901,6 +9904,7 @@ Prefer when: meta question about account, quota, active lens, or top-up recovery
 Examples that SHOULD invoke this tool:
 - "What's my account status?"
 - "How much quota do I have left this week?"
+- "Which version of the Leadbay connector is this?"
 
 Examples that should NOT invoke this tool (sound similar, route elsewhere):
 - "Show me today's leads."
@@ -9922,6 +9926,8 @@ Show the user's account state \u2014 admin rights, language, last-active lens, q
 
 **After a user tops up, do NOT keep refusing \u2014 RETRY.** If the user signals they topped up / bought credits / added credits, the previous QUOTA_EXCEEDED is invalidated the moment the Stripe webhook lands. RE-CALL \`leadbay_account_status\` to pick up the new state AND retry the originally failed call. The retry itself does not require a successful account_status check first \u2014 a topped-up user has cleared the throttle whether or not your cached snapshot reflects it yet. **A stale quota snapshot is never a reason to gate-keep a topped-up user.**
 
+**\`mcp_version\`** is the version of the Leadbay MCP server answering the call. When the user asks which Leadbay version they are running, answer with it.
+
 **\`notifications\` block.** The response now includes a top-level \`notifications\` array listing background work the user (or agent) initiated that has since completed (\`bulk_enrich\`, \`bulk_qualify\`, \`import\`). These are signals to revise prior agent outputs the just-finished work might have made stale \u2014 they're NOT a pending-task list for the user. After revising (or confirming nothing is affected), call \`leadbay_acknowledge_notification(notification_id)\`. Full handling protocol below.
 
 ## GATE \u2014 INSPECT \`_meta.notifications\` ON EVERY RESPONSE
@@ -20075,6 +20081,11 @@ var accountStatus = {
           agent_memory: { type: "object" }
         }
       },
+      // Set by the MCP server wrapper (NOT this composite) on every call.
+      mcp_version: {
+        type: "string",
+        description: "Version of the Leadbay MCP server answering this call. Answer 'what version of Leadbay are you running' with this value."
+      },
       // Auto-update block. Populated by the MCP server wrapper (NOT this
       // composite) when a newer release is published on GitHub AND the
       // user hasn't suppressed it. When present, the agent should prompt
@@ -27716,6 +27727,9 @@ ${url}
         }) === true
       }));
       await maybeAttachUpdate(name, result);
+      if (name === "leadbay_account_status" && result !== null && typeof result === "object" && !Array.isArray(result) && result.error !== true) {
+        result.mcp_version = serverVersion;
+      }
       maybeAttachNotifications(result);
       if (result && typeof result === "object" && result.error === true) {
         const envText = formatErrorForLLM(result);
@@ -28112,7 +28126,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.37.0" : "0.0.0-dev";
+var VERSION = true ? "0.38.0" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var logger = {

package/dist/installer-electron.js

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

package/dist/installer-gui.js

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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leadbay/mcp",
-  "version": "0.37.0",
+  "version": "0.38.0",
   "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",