HYPE OR FACT? · CHECKED 27 OCTOBER 2026
Supabase scoped access tokens: give your AI agent one project, not your whole account
OUR VERDICT
FactOur original verdict: “Fact vs hype: real and documented, but not brand new.”
THE CLAIM
“Supabase now lets you scope personal access tokens to the organisations, projects and permissions a job needs, so a CI pipeline or coding agent gets one project instead of your whole account.”
What’s actually true
- Tokens can be limited to specific organisations and projects, with per-area permissions and an expiry of up to a year. They work with the Supabase MCP server, the Management API and the CLI; with only database read access, the MCP server's SQL tool becomes read-only.
- It's been generally available since 28 September and is now the default, so the post is a reminder rather than a launch.
- Gotchas: the 'Read-only' preset still includes API-key secrets, so start from 'No access'; logging in to the CLI through the browser still creates a full-access token; a database password set in the environment bypasses token permissions.
Sources
Cost
Included on all plans.
USE IT IF
Anyone letting Claude Code, Cursor or an MCP server near a Supabase database: create a token for one project with database read access and a short expiry.
SKIP IT IF
Not a reason to skip other safeguards: environment database passwords and CLI browser logins still bypass the scoping.
Related AI tools
Related
How we knowChecked on 27 October 2026. Verdicts: Fact = the claim holds up; Partly fact = real, but with caveats or overstated parts; Hype = the headline claim isn't supported. Products change quickly, so check the maker's site before you buy. Our methods & sources ↗