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

**URL:** <https://forum.bubble.io/t/bubble-mcp-this-server-is-not-authorized-to-call-bubble-on-app-scoped-calls-dedicated-plan/401601>\
**Category:** Need help\
**Created:** [October 13, 2026, 3:29pm UTC](https://forum.bubble.io/t/bubble-mcp-this-server-is-not-authorized-to-call-bubble-on-app-scoped-calls-dedicated-plan/401601 "2026-10-13T15:29:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ricardo5](https://avatars.discourse-cdn.com/v4/letter/r/898d66/32.png) [@ricardo5](https://forum.bubble.io/u/ricardo5)\
**Post date:** [October 13, 2026, 3:29pm UTC](https://forum.bubble.io/t/bubble-mcp-this-server-is-not-authorized-to-call-bubble-on-app-scoped-calls-dedicated-plan/401601/1 "2026-10-13T15:29:32Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![fede.bubble](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/fede.bubble/32/215574_2.png) [@fede.bubble](https://forum.bubble.io/u/fede.bubble)\
**Post date:** [October 13, 2026, 6:03pm UTC](https://forum.bubble.io/t/bubble-mcp-this-server-is-not-authorized-to-call-bubble-on-app-scoped-calls-dedicated-plan/401601/2 "2026-10-13T18:03:15Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![cha\_james](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/cha_james/32/199800_2.png) [@cha\_james](https://forum.bubble.io/u/cha_james)\
**Post date:** [October 15, 2026, 1:33pm UTC](https://forum.bubble.io/t/bubble-mcp-this-server-is-not-authorized-to-call-bubble-on-app-scoped-calls-dedicated-plan/401601/4 "2026-10-15T13:33:08Z")

</div>

> [@cha\_james](#):
>
> we have the same issue, what is meant by upgrading tour dedicated manager? We are on the latest version of Bubble

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