ARTICLE

bubble mcp claude and mcp bubble io: MCP for Bubble developers (not MCPE)

I searched bubble mcp claude or mcp bubble io and kept hitting Minecraft noise. Here’s Bubble’s Model Context Protocol—not MCPE or MCPEDL—the official bubble mcp server, read-only Data API, and what still lives in the editor.

Why MCPE shows up in autocomplete

I typed MCP into search and got Minecraft hits. In developer search, MCP usually means Model Context Protocol: an open JSON-RPC standard so AI clients (including Claude) discover and invoke tools, resources, and prompts on a server. That has nothing to do with Minecraft Pocket Edition (MCPE) or download sites like MCPEDL (Bedrock add-ons and maps). Queries such as mcp bubble io or bubble mcp should point to Bubble’s docs and official endpoint—not game mods. Worth reading next: FLUX 3 Image and Vercel.

I put the full phrase Model Context Protocol in setup notes and stick to https://mcp.bubble.io/mcp (Bubble MCP | Bubble Docs).

Official path: Bubble MCP + Claude

Bubble runs a first-party bubble mcp server at https://mcp.bubble.io/mcp. Setup is documented for Claude (Connectors), Claude Code (claude mcp add --transport http --scope user bubble https://mcp.bubble.io/mcp), ChatGPT, Codex, and VS Code/Copilot—see the manual and bubble.io/mcp.

The server acts as the signed-in Bubble user: plan limits and collaborator permissions apply. It is not a read-only sandbox; MCP can change app design, workflows, and dev data where allowed.

What MCP can do (per docs):

  • app exploration: get_app_outline, get_node, list_types;
  • pages, elements, workflows, data types, privacy rules, option sets, styles, plugins;
  • issue checks, savepoints/undo;
  • API Connector: create_api_collection, create_api_call, etc.

Record tools (search_things, create_thing, …) work only on the development database and only for types an admin grants via grant_agent_data_access. Live production data is out of scope for the official server.

What stays in the Bubble editor (documented limits):

  • deploy and live promotion;
  • branch merge;
  • logs via MCP;
  • OAuth2 provider setup;
  • purchasing paid plugins before install;
  • initializing API Connector calls created through MCP in the editor—otherwise responses are not usable.

Changes made through MCP do not reach live until you deploy manually.

Claude + MCP safety (protocol level)

The MCP specification and Tools assume human-in-the-loop consent and visible tool use. Bubble’s official MCP is write-capable on design and dev data—I would not treat “MCP for Bubble” as a safe read-only assistant unless I picked a different server and token policy on purpose. A closer look: The ~500-row bulk-tools ceiling in.

What I actually do:

  • connect only to https://mcp.bubble.io/mcp, not random “bubble mcp” packages from autocomplete;
  • narrow grant_agent_data_access;
  • use savepoints and review batches before large edits.

Separate pattern: read-only Data API + custom MCP

Distinct from hosted bubble mcp, Bubble’s Data API (The Data API) supports integration-style access:

Schema introspection: Bubble documents Swagger at https://{app}.bubbleapps.io/api/1.1/meta/swagger.json when API/Swagger is enabled (The Bubble API). Community posts also reference .../api/1.1/meta; the manual emphasizes swagger.json as the stable discovery path.

Local third-party servers (e.g. nocoderoi/bubble_mcp) wrap the Data API; README claims such as read-only mode are author claims, not Bubble product facts. Read-only MCP experiments mean picking that architecture explicitly—not assuming every bubble mcp server is read-only.

MCP hosted on Bubble (different architecture)

A forum showcase describes API workflows plus HTTP as MCP tools, with stdio clients bridged via mcp-remote. That is not a substitute for mcp.bubble.io; it is your app acting as the MCP host.

Quick comparison

Goal Where to look
Edit a Bubble app from Claude https://mcp.bubble.io/mcp (official bubble mcp server)
Read-only data / schema for integrations Data API + privacy rules; optional custom MCP
MCPE / MCPEDL Minecraft—not Model Context Protocol

Takeaway

bubble mcp claude in a useful sense means Claude (or another MCP client) plus Model Context Protocol plus Bubble’s official server. mcp bubble io is the same lane—not MCPE. For safer read-only data access, I design Data API and privacy rules; I do not assume any bubble mcp install is read-only. Deploy, branches, and sensitive settings stay editor work.

Sources: Bubble MCP docs, What is MCP?, Claude Code MCP. Third-party repos and forum posts—verify yourself.

← All articles