# Supabase: MCP connection error to branch environments

- Impact (vendor’s label): none
- Status: resolved
- Started: 2026-08-11 14:37 UTC · Resolved: 2026-08-11 18:30 UTC · Duration: 3.9 h
- Updates: 6
- [Vendor status page: https://status.supabase.com/incidents/01KZRM42MQH6EP4BPYRRGNR006](https://status.supabase.com/incidents/01KZRM42MQH6EP4BPYRRGNR006)
- [Company: Supabase](https://rewindex.com/company/supabase.md)

## Timeline of updates

- **investigating** 2026-08-11 14:37 UTC: We're currently investigating an issue that is impacting MCP connections to branch environments.
- **identified** 2026-08-11 15:09 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** 2026-08-11 15:52 UTC: We're still working on implementing a fix for the identified root cause.
- **monitoring** 2026-08-11 16:33 UTC: UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.
- **monitoring** 2026-08-11 17:48 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** 2026-08-11 18:30 UTC: Customers should now be able to connect to branch environments via MCP normally.


---
Canonical: https://rewindex.com/company/supabase/incidents/01KZRM42MQH6EP4BPYRRGNR006 · Markdown: https://rewindex.com/company/supabase/incidents/01KZRM42MQH6EP4BPYRRGNR006.md · JSON: https://rewindex.com/api/v1/companies/supabase/incidents/01KZRM42MQH6EP4BPYRRGNR006 · Generated 2026-10-18T09:46:32.148Z