@qaecy/cue-sdk 0.0.26 → 0.0.27

package/README.md

@@ -94,6 +94,37 @@ Sign in using a Cue API key. Intended for non-interactive/server-side use (e.g.
 const user = await cue.auth.signInWithApiKey('MY_CUE_API_KEY', 'my-project-id');
 ```
 
+### `cue.auth.signInWithCustomToken(token)`
+
+Sign in using a Firebase custom token. Intended for server-issued auth flows such as MCP tools or OAuth-protected backends where the server mints a token on behalf of the user.
+
+**Typical flow (e.g. MCP + Google OAuth):**
+
+1. The server receives a Google OAuth access token (e.g. via the MCP host's OAuth dance).
+2. The server looks up the Firebase UID for the Google `sub` claim and mints a custom token using Firebase Admin:
+   ```typescript
+   // Server side (Node.js / Firebase Admin)
+   import * as admin from 'firebase-admin';
+
+   async function mintCustomToken(googleAccessToken: string): Promise<string> {
+     const res = await fetch('https://www.googleapis.com/oauth2/v3/userinfo', {
+       headers: { Authorization: `Bearer ${googleAccessToken}` },
+     });
+     const { sub } = await res.json(); // Google UID
+
+     const user = await admin.auth().getUserByProviderUid('google.com', sub);
+     return admin.auth().createCustomToken(user.uid);
+   }
+   ```
+3. The custom token is passed to the browser/view (e.g. via `structuredContent`).
+4. The client signs in instantly — no popup, no redirect, no polling:
+   ```typescript
+   // Browser / view side
+   const cue = new Cue();
+   await cue.auth.signInWithCustomToken(customToken);
+   // cue is now fully authenticated
+   ```
+
 ### `cue.auth.signOut()`
 
 ```typescript