Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Give your AI agent a git repo, cloud sandbox, database and hosting so its code runs.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Macaly Cloud MCP server gives Claude, ChatGPT and any MCP-compatible agent the infrastructure to run the code it writes. It exposes 16 tools covering a git repository, a cloud sandbox, build and dev-server logs, a shareable preview and production hosting on macaly.app. Your agent writes every line; Macaly stores, builds, runs and serves it. Sign-in is OAuth.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
x-ratelimit-* headers. Absent documentation is not the same as absent limits.FORBIDDEN means either the workspace has Macaly Cloud disabled or the action needs a plan feature you lack, and names custom-domain publishing as the example.CHAT_CLAIMED_BY_AGENT or CHAT_CLAIMED_BY_EDITOR.upload_file — documented but absent from Anthropic's listing — imports from a publicly reachable URL, up to 1 GB.Whatever your agent asks it to. Macaly documents the tool as running installs, CLIs, skill scripts and its own typecheck, and the directory listing adds type checks, package installs and database setup. Macaly's security page calls it a secure, isolated sandbox with real development tools, but publishes no command allowlist, no network egress policy and no CPU, memory or timeout figures.
No. Macaly's documentation says publishing happens only when you explicitly ask to go live, and that the agent then calls publish_app and polls get_deployment until the status is READY. The listing repeats it: publishing and domain changes are separate, explicit actions that are never taken on their own. Connecting a custom domain needs a Pro or Hosting plan.
Yes, through Macaly's version history rather than through the connector. Macaly states that each write_file and delete_file call is one atomic git commit with its own entry in the app history, and that a Restore this version button under any chat response reverts the project code to that point. No MCP tool in this connector performs the restore.
The Macaly Cloud page documents no plan gate for the connector itself, unlike Macaly's separate MCP server, which requires Pro. Two gates still apply. Builds consume credits from the workspace they run in, and Macaly gives the Free plan 3 million credits a month. Connecting a custom domain requires a Pro or Hosting plan.
It reads a platform capability guide before your agent writes code against that capability. Macaly describes it as returning a guide with ready-to-run commands and the code patterns to apply, covering the Convex database, authentication, payments, media generation and search. The intended sequence is read the guide with skill_info, then run its commands in the sandbox.
Someone else holds the app. Macaly's troubleshooting says the error means its own agent is mid-turn or another external editor wrote recently, and the advice is to wait and retry because the lock frees itself a few minutes after the last activity. Macaly designs this deliberately: only one agent works on an app at a time.
No. Macaly's listing states the connector reaches only the Macaly workspaces your account can reach, never your local machine and never another user's projects. The documentation adds that no tool accepts raw file bytes: a local file has to be added to the app's media library in Macaly first, then given to the agent as a public URL.
Both, and OAuth is the documented default. Macaly says your client opens a browser window where you sign in and approve access, with no keys to copy. An API key passed as a bearer token is offered as the headless alternative, scoped to a single workspace. Our own anonymous request confirmed the gate: HTTP 401 with an OAuth challenge.
.md suffix; the HTML route returns a 383 KB single-page-app shell, the Markdown 10.7 KB of clean text) · retrieved 2026-09-08/docs/_llms/, so the /en/ path in the directory's documentation URL is the primary one, not a localised variant of it. · retrieved 2026-09-08initialize against https://www.macaly.com/api/cloud/claude/mcp — HTTP 401 with WWW-Authenticate: Bearer error="invalid_token" and an RFC 9728 descriptor pointer (2026-09-08). The descriptor at /.well-known/oauth-protected-resource/api/cloud/claude/mcp names Clerk (https://clerk.macaly.com) as the authorization server with scopes openid, profile, email. No tool was called and no credential was supplied. · retrieved 2026-09-08robots.txt (fetched 2026-09-08). It disallows /api and two redirector paths; the /docs tree we read is not disallowed, and no Content-Signal line is published. · retrieved 2026-09-08Connect Macaly Cloud once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.