Macaly Cloud
by Macaly Cloud
Give your AI agent a git repo, a cloud sandbox, a database and production hosting so the code it writes actually runs. 16 tools, OAuth sign-in, one that executes commands and two that publish to the internet.
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 Macaly Cloud via MCP
https://www.macaly.com/api/cloud/claude/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect Macaly Cloud once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioMacaly Cloud Tools & Capabilities (16)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The sandbox boundary is undocumented. Macaly describes an isolated sandbox with real development tools and nothing more. No command allowlist, no network egress policy, no CPU, memory or timeout figures appear on the connector page, the security overview or the usage page (all fetched 2026-09-08). This is the single largest gap on this connector, and it sits on its highest-consequence tool.
- No rate limit is published for this endpoint. Macaly documents 120 read and 20 write calls per minute for its *other* MCP server. The Cloud page states no equivalent, and our 401 responses carried no
x-ratelimit-*headers. Absent documentation is not the same as absent limits. - Builds cost credits. Macaly's pricing page says credits are consumed when you generate or edit text, design, images or code with AI, that the Free plan gets 3 million credits a month, and that unused credits expire at the end of each billing period. Some agent skills carry fixed prices — video generation runs 160,000 to 600,000 credits per use.
- Custom domains need a paid plan. Macaly's domains page states that connecting a custom domain requires a Pro or Hosting plan. Its troubleshooting adds that a tool returning
FORBIDDENmeans either the workspace has Macaly Cloud disabled or the action needs a plan feature you lack, and names custom-domain publishing as the example. - Database usage is metered. Macaly includes 1 GB per month on Free and 10 GB on Hosting, Pro and Agency, counted across the whole workspace. Each additional 10 GB in a calendar month costs 2 million credits, and each additional 100,000 backend API calls costs 200,000 credits.
- One agent at a time. Macaly locks the app chat while an external agent is working, so its own agent will not start a turn. The lock clears a few minutes after the last write or as soon as your agent shows the preview. A write against a locked app returns
CHAT_CLAIMED_BY_AGENTorCHAT_CLAIMED_BY_EDITOR. - The first write on a cold workspace is slow. Macaly says it takes roughly 20 to 30 seconds longer while the sandbox finishes booting.
- The stack is fixed. Apps are TanStack Start, Vite and Tailwind with Convex as the backend, per Anthropic's listing. This connector is not a general-purpose cloud sandbox.
- No tool accepts raw file bytes. A file that exists only on your computer has to be added to the app's media library in Macaly first;
upload_file— documented but absent from Anthropic's listing — imports from a publicly reachable URL, up to 1 GB. - We could not read the tool schemas or safety annotations. The endpoint is OAuth-gated, so the 16 names come from Anthropic's directory listing and the access labels from Macaly's documentation. We never authenticated and never called a tool.
Frequently asked questions
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.
Sources
- Macaly Cloud MCP documentation (fetched 2026-09-08, via the Markdown variant Macaly serves at the same path with a
.mdsuffix; the HTML route returns a 383 KB single-page-app shell, the Markdown 10.7 KB of clean text) · retrieved 2026-09-08 - Macaly MCP Server documentation, the separate second connector (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly security overview (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly plans and credits (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly domains and hosting (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly FAQ (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly workspace usage and limits (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly API authentication (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly documentation index (fetched 2026-09-08). English is the canonical top-level index; eight other languages are published as separate 83-page indexes under
/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-08 - Live anonymous
initializeagainsthttps://www.macaly.com/api/cloud/claude/mcp— HTTP 401 withWWW-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/mcpnames Clerk (https://clerk.macaly.com) as the authorization server with scopesopenid,profile,email. No tool was called and no credential was supplied. · retrieved 2026-09-08 - Macaly
robots.txt(fetched 2026-09-08). It disallows/apiand two redirector paths; the/docstree we read is not disallowed, and noContent-Signalline is published. · retrieved 2026-09-08 - Anthropic Connectors Directory entry (fetched 2026-09-08) · retrieved 2026-09-08
- Macaly support — <mailto:support@macaly.com> · Privacy
Server Info
- Category
- Developer Tools
- Developer
- Macaly Cloud
- Tools
- 16
- Domain
- www.macaly.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Developer Tools
Related Resources
Ready to connect Macaly Cloud?
Connect Macaly Cloud once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.