MCP connection error to branch environments
Aug 11, 14:37 UTCAug 11, 18:30 UTC
Duration
3h 53m
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
Customers should now be able to connect to branch environments via MCP normally.
Timeline
- Resolved · Aug 11, 18:30 UTC
Customers should now be able to connect to branch environments via MCP normally.
- Monitoring · Aug 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.
- Monitoring · Aug 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.
- Identified · Aug 11, 15:52 UTC
We're still working on implementing a fix for the identified root cause.
- Identified · Aug 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.
- Investigating · Aug 11, 14:37 UTC
We're currently investigating an issue that is impacting MCP connections to branch environments.
More from Supabase
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2321:58 UTC | Supabase CLI CI workflow failures | minor | 1h 42m |
| Sep 2309:31 UTC | Storage search failing for restored projects | minor | Ongoing |
| Sep 2309:21 UTC | Increased error rate in project creation and project restore | major | 1h 28m |
| Sep 2210:49 UTC | Supavisor connection disruptions in EU West 1 (Ireland) | minor | 1h 31m |
| Sep 2208:33 UTC | Project creations are degraded in multiple regions | minor | 31m |
| Sep 1920:12 UTC | Project Lifecycle Activity Degradation | major | 2h |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.