Gatebase

Turn your Bubble workflows
into world-class APIs
and MCP tools.

Connect your backend workflows to apps and AI agents.
Manage access, versions, and every request in one place.

Start building Explore the product

Your workflows. Your data. A new way to connect.

YOUR API, AT A GLANCE.EXAMPLE WORKSPACE
Acme / Routesacme.gatebase.dev Test Live
API v1 Active All changes saved New route Publish
Get customer Test

Public route

Name
Get customer
Method
GET
Path
…/version-test/v1/customers/{uniqueId}

Bubble backend

Workflow
POSTget_customer
Parameters 2
ParameterSource
tenantId*stringGateway
uniqueId*stringPath
Gateway injection Optional

Expose as MCP tool

Tool name
get_customer
Description
Find a customer by their unique ID.
ONE CONNECTED STACK REST APIs MCP tools Consumer access Test & Live

01 / BUILT FOR THE CONNECTION

You build the logic.
We make it accessible.

The missing layer between your Bubble app and everything you want to connect it to.

One workflow. More ways in.

Give your workflows clean API routes. Expose them as MCP tools so AI clients can use them, too.

GET/v1/customers
POST/v1/orders
create_order

The right access. Every time.

Create consumers, issue API keys, and inject tenant IDs. Stay in control of who can call your workflows.

AAcme apptenantId · acmeEnabled
gb_••••••••••••••••API key

Know what’s happening.

Follow requests from your API to your workflow and back. Find errors with the context you need to fix them.

200/v1/customersREST
200create_orderMCP
422/v1/ordersREST

02 / FROM WORKFLOW TO ENDPOINT

Connected in three steps.

01

Connect your Bubble app

Add your app and API credentials. Gatebase discovers the backend workflows you’ve exposed.

02

Make it your API

Choose a workflow, define its public route, and enable MCP if you need it. Test as you build.

03

Publish with confidence

Deploy a version to Live, share access with your consumers, and follow every request.

03 / GOOD QUESTIONS

A few things
worth knowing.

Do I need to rebuild my Bubble workflows?

No. Gatebase connects to backend workflows exposed through Bubble’s Workflow API. You keep your business logic in Bubble and configure the public routes in Gatebase.

What can I connect with MCP?

MCP lets compatible AI clients discover and call the workflows you choose to expose as tools. Access is tied to a consumer, just like your REST API.

How do Test and Live work?

Build and try your routes in Test. When you’re ready, publish a version to Live. Changes in Test do not change your published Live routes until you deploy them.

Does Gatebase handle my app’s permissions?

Gatebase controls API access and can inject a consumer’s tenant ID. Your Bubble workflows still need to check that tenant and enforce access to the right data.

YOUR NEXT CHAPTER

Built in Bubble.
Ready for the world.

Your first endpoint is closer than you think.

Connect your Bubble app