Base44
by Base44
Build and edit Base44 apps from your AI assistant, and query the data your app's users submitted. Anthropic lists 5 tools; Base44 documents 16, including a shell command and a file writer. Edits commit to the live branch immediately.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Base44 via MCP
https://app.base44.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Base44 Tools & Capabilities (5)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The directory tool list covers under a third of the documented surface. Five names against sixteen, and the eleven absent ones include the shell command and the file writer. Read Base44's tool table, not the listing.
- We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no safety annotations were readable. Every read/write classification here is Base44's.
- Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, and the gated endpoint blocked our own
prompts/list, so we cannot say whether the server serves any. edit_base44_appis a natural-language dispatcher. Its effective surface is whatever the Base44 builder can do, and the documentation does not bound that. The sandbox tools are the reviewable alternative.- There is no merge step and no lock. Base44 states that if an agent and the app editor change the same file at the same time, the last write wins and the earlier change is gone.
- PII handling for
query_entitiesis undocumented. Base44 documents row-level and field-level security for an app's own users, but neither the MCP page nor the security page says whether a builder-side query is subject to them. Silence, not a guarantee. - A Builder plan or higher is required. Base44 documents the plan gate for connecting an assistant at all, and sandbox calls without it fail with
PREMIUM_REQUIRED. - Workspace role still governs. Base44 states the assistant acts as you and inherits your role, so a viewer or guest cannot create projects and a read-only viewer cannot change a project they can open. Superagents do not support the sandbox commands.
- Rate limits are per app, per minute: 120 read requests, 60 change requests and 30 run commands, exceeded calls failing with
RATE_LIMITED. - Session scope cannot be widened. Base44 states a session's permissions are fixed at creation and renewal does not add
sandbox:write— you must reconnect. - SSO workspaces cut the connection immediately. Base44 re-checks membership on every request and token refresh; removal ends the connection at once, and rotating the SSO configuration ends it until you reconnect.
- Data is in the US by default. Base44 states all its servers are US-located, with EU or UK residency limited to Elite and Enterprise plans and to apps created after 16 April 2026.
Frequently asked questions
How many tools does the Base44 MCP server actually have?
Base44 documents sixteen; Anthropic's directory snapshot lists five. The five in the directory are real and still documented, but the docs add seven sandbox tools, two internal build-polling tools, and two connector tools. The gap matters because the eleven unlisted tools include a shell command, a file writer and a file editor — the highest-privilege part of the surface.
Does an edit through the Base44 MCP server go live to my users immediately?
No, not to the public site. Base44 documents that a sandbox write commits to the app's active branch as part of the same request, so it appears in the app editor and its live preview straight away. Reaching the app's public site still takes the same separate publish step a change made in the editor would. Editing is not publishing.
Can I roll back a change an AI agent made to my Base44 app?
Yes, through checkpoints. Base44 documents `create_checkpoint` as saving a named restore point anchored to a specific commit, which you restore from the app editor if a later change goes wrong. Pending changes are flushed and committed first so the checkpoint captures the latest code. Base44 also states every sandbox change lands in git rather than in the compute process.
What data can query_entities read from my Base44 app?
Records from your app's entities — the tables holding whatever your app's end users submitted. Base44 documents entities as its MongoDB-compatible data model and names form submissions and survey answers among the records stored there. Base44's own deletion guidance treats those tables as a place personal data lives, and states the app owner is responsible for handling it lawfully.
Do Base44's row-level security rules limit what an agent can query?
Base44's documentation does not say. Its security page defines row-level and field-level rules governing what an app's users can access, but the MCP page describes the assistant's reach in terms of your own workspace role instead. Whether builder-side reads through `query_entities` are subject to those rules is not stated on either page. Treat the surface as unbounded until Base44 documents otherwise.
Do I need a paid Base44 plan to use the MCP server?
Yes. Base44's MCP documentation states a Builder plan or higher is required to connect an AI assistant through the server. The same requirement gates the sandbox tools from outside the app editor, where calls without it fail with `PREMIUM_REQUIRED`. Base44 also notes a workspace viewer or guest cannot create projects, whatever plan the workspace is on.
Which workspace does the Base44 MCP connection reach?
Exactly one, chosen at the OAuth consent step. Base44 documents that every action runs in the workspace you pick, that the connection cannot reach any other, and that the choice is fixed for the life of the connection. Targeting a different workspace means connecting again. Base44 re-checks your membership on every request and every token refresh.
Sources
- Base44 MCP server documentation — https://docs.base44.com/developers/backend/overview/mcp-server (fetched 2026-08-19 as Markdown via the
.mdsuffix; this is the URL Anthropic's directory publishes) · retrieved 2026-08-19 - Base44 "Bring your own agent" — https://docs.base44.com/developers/app-code/local-development/bring-your-own-agent (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 remote-development skill — https://docs.base44.com/developers/skills/base44-remote-dev (fetched 2026-08-19; source of the per-tool scope table and the connector tools) · retrieved 2026-08-19
- Base44 entities overview — https://docs.base44.com/developers/backend/resources/entities/overview (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 entity security rules — https://docs.base44.com/developers/backend/resources/entities/security (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 deleting user data — https://docs.base44.com/Community-and-support/Deleting-user-data (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 privacy and security — https://docs.base44.com/Community-and-support/Privacy-and-security (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 App MCP (a different server) — https://docs.base44.com/Integrations/app-mcp (fetched 2026-08-19) · retrieved 2026-08-19
- Base44 docs machine index — https://docs.base44.com/llms.txt (fetched 2026-08-19) and sitemap — https://docs.base44.com/sitemap.xml (fetched 2026-08-19; 2,281 URLs, adding no MCP pages beyond the index apart from translations) · retrieved 2026-08-19
docs.base44.com/robots.txtallows the docs paths and carriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis is expressly permitted on all three axes (fetched 2026-08-19).app.base44.com/robots.txtis a bareDisallow:with no path, which permits everything · retrieved 2026-08-19- Wix press room, acquisition announcement — https://www.wix.com/press-room/home/post/wix-further-expands-into-vibe-coding-with-acquisition-of-base44-a-hyper-growth-startup-that-simplif (18 June 2025; fetched 2026-08-19) · retrieved 2026-08-19
- Live RFC 9728 protected-resource descriptor — https://app.base44.com/.well-known/oauth-protected-resource/mcp and https://app.base44.com/mcp/.well-known/oauth-protected-resource (both fetched 2026-08-19, byte-identical; the root form returns 404) · retrieved 2026-08-19
- Live RFC 8414 authorization-server metadata — https://app.base44.com/.well-known/oauth-authorization-server (fetched 2026-08-19) · retrieved 2026-08-19
- Live anonymous probe — 2026-08-19:
POSTto the endpoint returns HTTP 307 to/mcp/, which returns HTTP 401 withwww-authenticate: Bearer error="invalid_token", resource_metadata="https://app.base44.com/.well-known/oauth-protected-resource/mcp"· retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/16ebc92d-b1db-473a-82ef-015426940c4c (snapshot 2026-08-16) · retrieved 2026-08-16
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Developer Tools
- Developer
- Base44
- Tools
- 5
- Domain
- app.base44.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.