How do I review TypeScript MCP OAuth callback and storage ownership?
SDK OAuth helpers support an application flow but do not decide its callback environment, private storage or user association automatically. Review those responsibilities before presenting a TypeScript remote client as ready for Montage, and fail closed when approved auth cannot complete. Callback ownership and token storage must fit the actual runtime and requesting user. SDK helpers cannot automatically decide those trust boundaries, and a successful local flow cannot establish that another deployment’s callback or private-state isolation works.
Help me review TypeScript MCP OAuth callback and storage ownership. Determine whether the existing client runs in an application backend, browser environment or another supported host. State which runtime and generation produced the real read, or name the incomplete auth boundary. No writes.Identify the runtime boundary
Determine whether the existing client runs in an application backend, browser environment or another supported host. Token storage and callback handling must fit that architecture rather than being copied from an unrelated sample with different trust assumptions.
Match helper generation
Use OAuth facilities documented for the installed v1 or v2 client line. Do not mix callback or storage interfaces between generations merely because both examples target an HTTPS MCP server.
Trace private account association
Review where approved auth state is linked to the requesting user and how it stays outside model messages and inappropriate bundles. Helpers are not proof that a shared store or callback automatically selects the correct Montage account.
Run a direct authorized check
After the supported application flow completes, execute signals_status through the actual configured client without a model. Preserve the returned workspace or authorization error rather than claiming completion from a callback page alone.
Conclude with specific evidence
State which runtime and generation produced the real read, or name the incomplete auth boundary. A locally successful OAuth flow does not certify another deployment’s callbacks, storage isolation or permission for future workspace mutations.
Keep the boundaries clear.
- Helpers are not proof that a shared store or callback automatically selects the correct Montage account.
- A locally successful OAuth flow does not certify another deployment’s callbacks, storage isolation or permission for future workspace mutations.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.