kemal.earthandClaude Sonnet 5 124ff77ad0 feat(studio): warn that scoped tokens don't support the MCP server (#48849) ...

## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.

YES

## What kind of change does this PR introduce?

Scoped PATs are blocked from the Supabase MCP server until AI-1025 ships
FGA guard support, so surface that on the scoped review step (with a
link back into legacy mode) and on the view-token sheet, sharing one
warning module for easy removal.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Added a clear notice explaining that scoped access tokens aren’t
supported by the Supabase MCP server.
  * Added an option to create a legacy token when applicable.
* Displayed the MCP compatibility notice in token review and access
views.
* **UI Improvements**
  * Organization selectors now display their associated icons.
* Standardized MCP guidance across token-related screens for a more
consistent experience.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-07 17:41:45 +01:00

..

AccessTokens

feat(studio): warn that scoped tokens don't support the MCP server (#48849)

2026-08-07 17:41:45 +01:00

Preferences

Refactor all usage of form.watch to either useWatch or subscribe (#48436)

2026-07-30 11:45:40 +08:00

TOTPFactors

feat(account): require a user to name their TOTP authenticator (#48493)

2026-07-31 09:16:41 +02:00

AuditLogs.tsx

chore: cleanup duplicate exports studio (#47387)

2026-06-29 15:46:16 +02:00

AuditLogs.utils.ts

chore: remove format param from audit log query (#45466)

2026-05-04 16:24:44 -07:00