Bubble MCP: "This server is not authorized to call Bubble" on app-scoped calls (Dedicated plan)

Need help
1

Hi everyone,

We’re trying out the Bubble MCP (beta) from Claude and are stuck on an authorization error. Wondering if anyone else has hit this.

What works

  • OAuth connection completes successfully
  • whoami returns the session correctly
  • list_apps returns all our apps

What fails
Any app-scoped call (get_pages, get_issues, etc.) returns:

This server is not authorized to call Bubble.

It happens across all of our apps, so it doesn’t seem tied to a specific one.

Setup

  • Enterprise / Dedicated instance
  • We’ve seen the announcement that Agent 2 and the new AI features (including MCP) become available after upgrading the Dedicated Manager

Questions

  1. Does the MCP require the latest Dedicated Manager upgrade to access app data?
  2. Is there a setting to enable per app (or at the instance level) for MCP access?
  3. Does the connected account need a specific collaborator permission level?
  4. Is the MCP beta supported on Dedicated plans yet?

Has anyone on a Dedicated plan gotten it working? Any pointers appreciated. Thanks!

2

hey @ricardo5 the MCP should work for everyone so upgrading your dedicated manager is probably the issue here. Give it a go

4

we have the same issue, what is meant by upgrading your dedicated manager? We are on the latest version of Bubble