Integration · Automate and collaborate

Base44 and Meteor AI agents

Connect Base44 to a Met: query and create records in your app, review its entities and request project changes with the official Base44 MCP server.

Book a demo See every integration

How does Base44 connect to Meteor?

With the Base44 ready-made connector, your Met uses Base44's official MCP server with your account, authorized once with OAuth on the workspace you choose. It can list your projects, read an app's entities, query their records and create or update records, which is what it needs to save what arrives on WhatsApp. It also creates projects from a description, requests changes to an app, connects third party connectors and works on the sandbox files. Running commands in the sandbox and calling platform API operations, such as deploys or domains, start switched off until the admin turns them on. You need a Base44 Builder plan or higher.

What it automates

What a Meteor Met does with Base44

Save what arrives on WhatsApp in your app

A customer asks for an appointment or leaves a request. The Met reads the entity in your app where those are stored and creates the record with what the customer said.

Answer with what your app already has

When the customer asks about their request, the Met queries that entity's records and answers with the status it has in your app.

Request a change to an app without opening the editor

The owner asks by message "add a phone field to the form". The Met passes the change to the project and tells them what was done.

Check which connectors a project has

The Met lists the project's connectors and says which ones are already connected, before someone tries to use one that is missing.

24 tools

Everything your Met can ask Base44 for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`create_base44_app`	Creates a new project from a text description.
`edit_base44_app`	Makes changes to an existing project.
`list_user_apps`	Lists your projects, filtered by name if you need it.
`list_branches`	Lists a project's branches with their name, ID and status.
`list_entity_schemas`	Gets the entity schemas of a project.
`create_entity_schema`	Defines a new entity schema in a project.
`update_entity_schema`	Replaces an entity's fields; anything you do not send is removed.
`query_entities`	Queries records of an entity in a project.
`create_entities`	Creates records of an entity in a project.
`update_entities`	Updates records of an entity in a project.
`list_connectors`	Lists a project's connectors and which ones are already connected.
`initiate_connector_connection`	Connects a third party connector to a project.
`list_directory`	Lists files and folders in the app's sandbox.
`read_file`	Reads a file's content from the app's sandbox.
`grep`	Searches the sandbox files for a pattern.
`write_file`	Creates or overwrites a file in the sandbox; the change lands in the app right away.
`edit_file`	Replaces exact strings in a sandbox file.
`run_command`	Runs a shell command in the app's sandbox. Starts switched off.
`start_checkpoint`	Opens a restore point session before a change; not yet available in every account.
`create_checkpoint`	Saves a restore point in the app's version history, with an optional name.
`base44_readme`	Gives an overview of the available tools and how to use them together.
`list_api_catalog`	Lists the platform API operations that can be called, grouped by area.
`describe_api`	Gets the parameters, body and response of up to 10 platform API operations.
`execute_api`	Calls a platform API operation by its method and path. Starts switched off.

The limits

What the Base44 integration does NOT do

We would rather say it here than have you find out during rollout.

It does not work on plans below Builder: Base44 requires a Builder plan or higher to connect its MCP server.
It does not leave the workspace you chose when authorizing: to use another one you need to connect again and choose it.
It does not ask for confirmation in the chat before creating records, changing an app or writing in the sandbox. The admin decides in Connections which actions stay on; running commands and calling the platform API start switched off.
It does not keep sandbox changes in the version history unless it creates a restore point: Base44 says restoring discards whatever was written after the last one.
It does not go beyond your role: the Met acts as you and follows your permissions in that workspace. A viewer cannot change anything.

Before you start

What you need to connect Base44

1

A Base44 account on a Builder plan or higher

The Base44 account where your app lives, on a Builder plan or higher. Your role in the workspace decides what the Met can read or change.
2

Connect it in Met

In Met, open Connections → Base44 → Connect, sign in to Base44 and choose the workspace. Then you choose which actions stay on.

Frequently asked questions

Questions about Base44 and Meteor

Yes, if those actions stay on: it can request changes to the project or write files in the sandbox. For an app in use, it is better to leave only the record actions on.

No. The connection stays fixed on the workspace you chose when authorizing. For another one, you need to connect again.

Base44 warns that update_entity_schema replaces the fields: the ones not sent are removed. That is why it is worth reviewing before leaving it on.

You do, with your Base44 plan. Meteor does not resell Base44 and does not charge for the calls the Met makes to your account.

Step by step