Skip to content
OutageDeck

Incident detail

MCP connection error to branch environments

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Supabase breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Supabase alerts work

Timeline

Incident updates

Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.

  1. Investigating

    We're currently investigating an issue that is impacting MCP connections to branch environments.

  2. Identified

    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.

  3. Identified

    We're still working on implementing a fix for the identified root cause.

  4. Monitoring

    UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.

  5. Monitoring

    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.

  6. Resolved

    Customers should now be able to connect to branch environments via MCP normally.

Keep exploring

More from Supabase

Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.

← Older incident

Project Upgrade Delays

All Supabase incidentsSupabase live status