Claude Base44 connectorWhat Claude can do in your Base44 account.
The Claude Base44 connector exposes 5 tools. 3 read your projects and their data, 2 build or change an app. Below: what Claude can look up, what it can build for you, which workspace it lands in, and what Base44 asks of your account first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Base44 sits inside the conversation
Base44 is an app builder: you describe what you need and it generates the project, with its data models, backend and screens. With the connector, that brief goes to Claude in plain words. Claude hands it to Base44, and later reads the records your app stores, so you can check what your users entered without opening the editor.
A first version from a paragraph. You write two sentences about a job-application tracker with status, company and interview notes. create_base44_app sends that to Base44, the build runs in the background, and Base44 returns a link to its editor once the project is ready.
An existing app, adjusted in words. Your CRM project needs a follow-up date on contacts. Ask for it, and edit_base44_app passes the change to the project you name, which list_user_apps helps Claude find first.
Answers from your own data. list_entity_schemas shows how a project stores its records and query_entities pulls the rows you ask about, such as orders still marked pending.
What Claude will not do here. It stays inside the one workspace you picked when you signed in, and cannot reach another. It inherits your role: as a read-only Viewer, it changes nothing. Base44 documents more tools than the directory sheet lists, and Claude only sees the five on that sheet. Nothing runs on its own either: no tool wakes up when a record is added. Background jobs of that kind belong to an automation tool, a different job, collected on the Integrations hub.
Five words before you plug it in
The vocabulary you will meet while connecting Base44.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Base44.
Connecting Base44 to Claude in three steps
- 01
Find Base44 in Claude
In Claude's settings, open Customize, then Connectors, and look for Base44 in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Base44 in the window Base44 opens itself. That is where you choose the workspace the link will work in. If the link breaks later, Disconnect and connect again.
- 03
Read the authorization screen
Read Base44's screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from your Base44 account itself.
The 5 tools, sorted by what they do
Base44 gives Claude 5 tools: 3 that read your account, 2 that change something in it.
Two groups: what Claude reads in your projects, and what it builds or changes. Tool names stay as Claude shows them.
- 3 read
- 2 write
What Claude reads (3)
3 toolsThree tools that look at your projects and their records without touching them.
list_user_apps
Returns the projects in the workspace you connected, and can narrow them down by name. Claude usually starts here to know which app you mean before anything else.
list_entity_schemas
Shows how a given project structures its data: each entity and the fields it holds. You get the shape of the app's storage, not the records themselves.
query_entities
Pulls the records of one entity in a project, the ones your question is about. Claude then reads them back to you or summarises them in the conversation.
What Claude builds or changes (2)
2 toolsTwo tools that act on your Base44 workspace. No source describes a confirmation specific to them: the general rule below applies.
create_base44_app
Approval: see the ruleTurns a written description into a brand-new Base44 project. The build carries on in the background, and Base44 hands back a link to its editor once it is ready.
edit_base44_app
Approval: see the rulePasses a requested change to a project that already exists in your workspace. Like a new build, it runs in the background and ends with a link to the editor.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. On top of that, Claude only has your rights: Base44 says the assistant acts as you and inherits your role in the workspace you picked.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, the connector's sheet in the official directory is the place to check. Base44's own subscription requirement is a separate matter, covered in the limits.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a record lands, a user signs up or a build finishes.
Everything here comes from Base44's own developer documentation: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions that no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes it on every sheet: it does not choose the tools a publisher exposes, nor guarantee they behave as described. Connect what comes from a publisher you trust. Other connectors get the same treatment on pages like the Claude airtable connector.
Need help connecting Base44 to Claude?
A person reads every message.
