@hubex/mcp 0.6.20260910 → 0.7.0

package/dist/auth.js

@@ -175,7 +175,12 @@ class RefreshingAuth {
     }
     /**
      * A service-token login never carries a refresh token, so ask for one.
-     * Best-effort: without it we simply re-authenticate when the access token expires.
+     * Best-effort for "service"/"login": credentials were already proven by the
+     * preceding login call, so a failure here just means retrying at expiry.
+     * Fatal for "token": the user-typed token is otherwise never round-tripped
+     * against the server, so this request is the only thing that can catch a
+     * token issued for the wrong environment (dev/stg/prod) — swallowing it
+     * would report success on a token that doesn't actually work.
      */
     async acquireRefreshToken() {
         try {
@@ -186,6 +191,8 @@ class RefreshingAuth {
             this.absorb(result);
         }
         catch (err) {
+            if (this.config.authMode === "token")
+                throw err;
             console.error("[hubex-mcp] could not obtain a refresh token; will re-authenticate on expiry: " +
                 `${err.message}`);
         }
@@ -201,7 +208,13 @@ class RefreshingAuth {
         const res = await fetch(url, init);
         if (!res.ok) {
             const body = await res.text().catch(() => "");
-            throw new Error(`${init.method ?? "GET"} ${url} failed (HTTP ${res.status}): ${body.slice(0, 500)}`);
+            let message = `${init.method ?? "GET"} ${url} failed (HTTP ${res.status}): ${body.slice(0, 500)}`;
+            if (res.status === 401 || res.status === 403) {
+                message +=
+                    ` Сейчас выбрано окружение HUBEX_ENV=${this.config.env}. Если токен получен в другом ` +
+                        `окружении (dev/stg/prod), авторизация не пройдёт — проверь, что токен именно из ${this.config.env}.`;
+            }
+            throw new Error(message);
         }
         return (await res.json());
     }