Resolved after 3 hours 52 minutes, on August 11, 2026.
Customers should now be able to connect to branch environments via MCP normally.
Update timeline
- investigating Aug 11, 2026, 02:37 PM UTC
We're currently investigating an issue that is impacting MCP connections to branch environments.
- identified Aug 11, 2026, 03:09 PM UTC
We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.
- identified Aug 11, 2026, 03:52 PM UTC
We're still working on implementing a fix for the identified root cause.
- monitoring Aug 11, 2026, 04:33 PM UTC
We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
- monitoring Aug 11, 2026, 05:48 PM UTC
We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.
- resolved Aug 11, 2026, 06:30 PM UTC
Customers should now be able to connect to branch environments via MCP normally.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services