@ateam-ai/mcp 0.4.60 → 0.4.62

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ateam-ai/mcp",
-  "version": "0.4.60",
+  "version": "0.4.62",
   "mcpName": "io.github.ariekogan/ateam-mcp",
   "description": "A-Team MCP Server — build, validate, and deploy multi-agent solutions from any AI environment",
   "type": "module",

package/src/tools.js

@@ -3167,13 +3167,30 @@ const handlers = {
       const base = getBaseUrl(sessionId) || "";
       const wellFormedKey = parseApiKey(api_key).isValid;
       const triedProd = /(?:^|\/\/)api\.ateam-ai\.com/.test(base);
-      const hint = wellFormedKey && triedProd
-        ? ` This is a well-formed tenant key ("adas_${resolvedTenant}_…") but ${base} rejected it — if it's a DEV key, retry: ateam_auth(api_key, url:"https://dev-api.ateam-ai.com").`
-        : ` (tried ${base || "the default base"})`;
+      // THE HEADLINE MUST NOT CONTRADICT THE HINT. The upstream message is
+      // "Invalid or unconfigured API key" — which for a well-formed key tried
+      // against the WRONG ENVIRONMENT is false: the key is fine, the target is
+      // wrong. Leading with it sent the reader to get a replacement key they
+      // did not need. The hint below already said the right thing and rescued a
+      // session on 2026-08-21, but only because someone read past the first
+      // line. Lead with the likely cause; keep the upstream text as detail.
+      if (wellFormedKey && triedProd) {
+        return {
+          ok: false,
+          tenant: resolvedTenant,
+          env_mismatch_suspected: true,
+          message:
+            `WRONG ENVIRONMENT, most likely — not a bad key. "adas_${resolvedTenant}_…" is a well-formed tenant key, ` +
+            `and it was tried against PROD (${base}), which is the default. A DEV tenant's key is rejected there. ` +
+            `Retry as: ateam_auth(api_key, url:"https://dev-api.ateam-ai.com"). ` +
+            `Only if that also fails is the key itself the problem (get one at https://mcp.ateam-ai.com/get-api-key). ` +
+            `Upstream said: ${err.message}`,
+        };
+      }
       return {
         ok: false,
         tenant: resolvedTenant,
-        message: `Authentication failed: ${err.message}.${hint} The user can get a valid API key at https://mcp.ateam-ai.com/get-api-key`,
+        message: `Authentication failed: ${err.message} (tried ${base || "the default base"}). The user can get a valid API key at https://mcp.ateam-ai.com/get-api-key`,
       };
     }
   },
@@ -5527,7 +5544,20 @@ export async function handleToolCall(name, args, sessionId) {
           "",
           hasEnvVars
             ? "Environment variables (ADAS_API_KEY) were detected, but they are not sufficient for tenant-aware operations. You must call ateam_auth explicitly to confirm which tenant you intend to use."
-            : "No authentication found.",
+            // "No authentication found." was TRUE and pointed at the WRONG CAUSE.
+            // Auth is held in this process's memory and does NOT survive a
+            // restart, so a container rebuild silently logs out every connected
+            // session — and the message read like a first-time setup problem,
+            // sending the reader to go get an API key they already had.
+            // 2026-08-21: a Builder deploy logged out a live session mid-work
+            // and cost a human round-trip to diagnose. State both causes; the
+            // second is the likelier one for a session that was working a
+            // moment ago.
+            : "No authentication found in this process. TWO CAUSES, and the second is easy to miss:\n" +
+              "  (a) this session never authenticated, or\n" +
+              "  (b) THE MCP SERVER RESTARTED. Auth lives in memory and does not survive a restart, so a\n" +
+              "      container rebuild or redeploy logs out every connected session with no warning.\n" +
+              "If your tools were working minutes ago, it is (b) — nothing is misconfigured, just re-run ateam_auth.",
           "",
           "Please ask the user to:",
           "1. Get their API key at: https://mcp.ateam-ai.com/get-api-key",