What you need before you start
Base44 exposes your account to any MCP-compatible assistant through one address, https://app.base44.com/mcp. Once the assistant is connected, you describe an app in plain language and it creates or updates the project in your workspace.
The first thing to check is the plan, because this is where the connection usually stops. Base44 documents that a Builder plan or higher is required to connect an AI assistant through its MCP server. On the grid read on November 5, 2026, Starter is $20 a month and Builder is $50, so the real price of this connection is $50, not the $20 entry price. Starter buyers who try the URL get a refusal, not an upgrade prompt.
The second thing is the authentication method. Base44 uses OAuth, not an API key: you sign in to Base44 during the connection, and you pick the workspace inside that flow. There is no token to generate and no key to paste.
Have these ready:
- A Base44 account on a Builder plan or higher.
- An MCP client that supports remote HTTP servers, Claude Desktop, Claude Code or any other client in that family.
- A decision on which workspace the assistant should work in, since that choice is locked once made.
How the job is done with Base44
The configuration is one block. In the MCP settings of your client, add a server with the HTTP transport and this URL:
{"base44": {"type": "http", "url": "https://app.base44.com/mcp"}}
Then restart the client if it does not pick up new servers on its own, which several do not.
On the first call, Base44 opens its standard OAuth sign-in. You authorize the app, and the consent screen asks which workspace the connection targets. That choice matters more than it looks: every action the assistant takes, creating a project, listing projects, editing a project, runs inside the workspace you pick, and the connection cannot reach any other workspace afterwards. The workspace is fixed for the life of the connection. To point an assistant at a different workspace, you remove the connection and authorize again.
What the server exposes is the project surface: creating, listing and editing projects, plus the app scaffolding that Base44 already performs in its own chat. It is the same build engine, driven from another client.
On this page
What to check in the result
Ask for something read-only first, such as the list of projects in the workspace. If that list is empty while your own dashboard shows projects, the authorization landed on another workspace, and the fix is to redo the connection rather than to debug the client.
Then make one small change on a project you can afford to touch, and confirm it in the Base44 interface rather than in the conversation. A write that reports success and changes nothing is the failure mode a chat window hides best.
Check the plan badge on the Base44 side. The refusal for a Starter account arrives at authorization time, and it reads like a permission error rather than a billing limit.
Where it usually goes wrong
A Starter account. The MCP server is documented for Builder and above, and nothing in the OAuth flow mentions the plan until it refuses.
The wrong workspace. The consent screen pre-selects one, and the connection keeps that choice for good. A team that shares projects across workspaces ends up with an assistant that answers about the personal one.
A client that needs a restart. The server is added, the client keeps its old list, and the connection looks broken.
Confusing the two Base44 MCP servers. There is a second one, https://docs.base44.com/mcp, which searches Base44’s documentation and nothing else. It is free of plan requirements and useful for questions about the SDK, but it cannot create or edit an app.
What the plan allows
The MCP server itself is not sold separately. What it gives you is the build engine, and the build engine is metered in message credits, which is why the plan decides how usable the connection is.
Builder at $50 a month carries 250 message credits and 10,000 integration credits, with AI model select and the GitHub integration. Starter at $20 carries 100 message credits and 2,000 integration credits, and cannot use the MCP at all. Yearly billing takes a fifth off: Builder drops to $40 a month, Starter to $16.
That puts the connection at $50 a month, or $40 with the year paid up front. Compared with a coding agent subscription in the same range, the difference is what you are renting: here it is app generation and hosting, not a code editor.
The full grid, tier by tier and with the date each price was read, is in the Base44 review. ## What we did not do
Nobody on this site has connected Base44 to Claude. We did not create an account, authorize a workspace, run a prompt through the MCP server or watch the consent screen. Everything above comes from Base44’s documentation and pricing page, read on November 16, 2026, and listed in Sources.
The steps are therefore documented rather than tested. We did not measure the time an authorization takes, we did not verify what the assistant returns when a build fails, and we did not test the behaviour of a connection whose workspace was deleted after authorization.
One point is worth flagging. The documentation gives the plan requirement as Builder or higher, without saying what happens at the boundary, so the refusal a Starter account receives is described here in general terms rather than quoted.
Sources
Read on November 16, 2026.
Base44 MCP server, https://docs.base44.com/developers/backend/overview/mcp-server.
Managing MCP connections, https://docs.base44.com/documentation/account-and-billing/setting-up-a-custom-mcp.
Base44 Docs MCP, https://docs.base44.com/developers/backend/overview/base44-docs-mcp.
Pricing, https://base44.com/pricing, read November 5, 2026.
Update log
November 16, 2026: first version, built from Base44’s documentation and pricing page. No hands-on test has been done.
Start with Base44
This is an link to the publisher. A commission may be paid if you subscribe, and the price stays the same for you.