[RESOLVED] Reports of issues authorizing MCP for sites within Client Workspaces

What to do

• Check whether you use Webflow MCP Server. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 41m it lasted.

  Anything that failed between 2026-09-17 09:30 UTC and 2026-09-17 10:12 UTC may need a replay.

• Subscribe to Webflow's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=webflow works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Webflow 4

1. investigatingSep 17, 2026, 9:30 AM UTC

   We’re investigating reports that some customers are unable to authorize MCP for sites within client Workspaces. Affected sites may appear greyed out and cannot be selected during the authorization process. Our team is actively investigating the issue and will share another update as soon as we have more information. Thank you for your patience.

   provider

2. identifiedSep 17, 2026, 9:44 AM UTC

   We have identified the cause of an issue affecting MCP authorization for some sites within Client Workspaces. Our team is actively working to implement a fix.

   provider

3. monitoringSep 17, 2026, 10:00 AM UTC

   A fix has been implemented and customers should now be able to authorize MCP for sites within client Workspaces as expected.

   provider

4. resolvedSep 17, 2026, 10:12 AM UTC

   This incident has been resolved. Thank you for your patience while we worked on this issue.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.