Claude Macaly Cloud connectorWhat Claude can do in your Macaly Cloud account.
The Claude Macaly Cloud connector exposes 16 tools: 9 read, 6 write, 1 undocumented. Claude writes the code of a web app, and Macaly stores it, builds it, previews it and hosts it. Here is what Claude can change, what stays read-only, and where Macaly's own docs disagree with the sheet.
Verified Trustpilot reviews · AI, automation & growth agency
Why connect Macaly Cloud to Claude
Asking Claude for an app usually ends with code in a chat window and no place to run it. With Macaly Cloud connected, the code goes straight into a project in your Macaly workspace: every file write becomes a commit, Macaly builds it and gives you a shareable preview, and when you explicitly ask, the app goes live on a macaly.app address you can share.
From idea to a link you can share. You ask for a pre-order page. Claude calls create_app, writes the pages with write_file, then hands back the shareable address from preview_app.
Fix a build that fails. When the preview stays blank, Claude reads the real error with get_logs instead of guessing, edits the faulty file and checks again.
Go live on your own domain. Once you explicitly ask, publish_app puts the app in production and connect_domain attaches your address; Macaly says these steps are never taken on their own.
What it will not do: Claude reaches only the Macaly workspaces your account can reach, never your own computer and never another user's projects. No tool accepts a file straight from your disk, either: it has to sit in Macaly's media library first. And nothing runs on a timer; Claude acts only while it answers you. For recurring jobs between apps, the Integrations hub lists the automation platforms we cover.
Five words before you connect
The Claude vocabulary around this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself; the directory sheet lists all of them.
- Authorization
- Macaly's own sign-in window, where you approve the access Claude will use afterwards. Granted once, per person, revocable.
- Approval
- The confirmation Claude waits for before changing something in your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Macaly.
Set up the Claude Macaly Cloud connector in three steps
- 01
Find Macaly Cloud in Claude
Open Claude's settings, go to Customize, then Connectors, and look for Macaly Cloud. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Macaly in the window Macaly opens itself. Macaly adds that you approve access in that same window, and that the connector works in claude.ai, the desktop app and on mobile.
- 03
Check the authorization screen
Read Macaly's approval screen before you accept. It belongs to the service, not to Claude, and it sets what the access covers. Macaly says the connection uses OAuth, or a team-scoped API key.
The 16 tools, sorted by what they do
Macaly Cloud gives Claude 16 tools: 9 that read your account, 6 that change something in it, and 1 no official source describes.
Nine tools read, six change your projects, and one is described by no source. Names stay exactly as Claude shows them.
- 9 read
- 6 write
- 1 not documented
What Claude reads (9)
9 toolsNine tools that look at workspaces, projects, files, logs and deployments without changing anything.
get_deployment
Reports where a publication stands, the live address and any domains already attached. Claude polls it after a release until the deployment reads as ready.
get_logs
Fetches the build, dev-server or deployment logs of an app, so Claude sees the real error message rather than guessing what went wrong in the last step.
get_project
Gives a status picture of one app: the preview build state, its preview and live addresses, the project briefing and who is working on it right now.
list_files
Returns the source files that make up an app, the map Claude consults before deciding which one to open next.
list_projects
Shows the apps of a workspace, the most recently updated first, with a search box and paging for long lists.
list_teams
Lists the Macaly workspaces your account can build in. Claude starts here when it has to pick where a new app should go.
preview_app
Returns the live preview address of an app, ready to share with someone who should see the app before it goes public.
read_file
Opens one source file by its path so Claude can look at the current code before deciding what to propose.
skill_info
Reads Macaly's guide for a platform capability, such as a database, payments, authentication, media or search, with ready-made commands and the code patterns to follow.
What Claude changes (6)
6 toolsSix tools that create, edit, delete or publish. No source describes Claude's confirmation for them: the general rule below applies.
connect_domain
Approval: see the ruleAttaches a custom domain to an app, or renames its Macaly subdomain. Macaly lists domain changes among the explicit actions that never happen by themselves.
create_app
Approval: see the ruleStarts a new, empty app on Macaly's default stack and returns its briefing. Macaly's own agent builds nothing at this stage.
delete_file
Approval: see the ruleRemoves one source file and records the deletion at once as its own commit in the app's history, so it can still be traced.
duplicate_app
Approval: see the ruleForks an existing app, history included, into a fresh copy you can change without touching the original.
publish_app
Approval: see the rulePuts the app into production at its macaly.app address. Macaly says the agent calls it only when you explicitly ask to go live.
write_file
Approval: see the ruleWrites one source file in full and commits it immediately. Macaly says each call is one atomic git commit with its own entry in the app's history.
Not documented (1)
1 toolListed on the directory sheet, but no official source explains it under this name. Nothing here is a capability.
run_project_command
No official source describes a tool by this name. The directory sheet publishes the name only, and Macaly's documentation lists a different command tool instead, so nobody can say what this one does. Claude's general approval rule, explained below, is the only reference.
What Claude asks before acting
By default, Claude stops and asks before any action it takes on an account on your behalf. No source describes a prompt specific to Macaly's tools.
On Team and Enterprise workspaces, owners decide whether members may let certain actions through without a fresh prompt, and they can restrict what a connector may do for the whole organisation, keeping reads open and closing writes for instance. Claude also works with your rights and nothing more. Macaly adds two commitments of its own: publishing and domain changes are separate, explicit actions, and every file change is a commit you can trace and roll back.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, the answer is published nowhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organisation before members connect. For this one's current status, check its sheet in the official Claude directory. Macaly alone documents this connector; no Claude help page covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing rebuilds or publishes on its own when you are not in the conversation.
The directory's partner badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools or guarantee they behave as described. Macaly's apps also follow one recipe: TanStack Start, Vite and Tailwind, with Convex behind them. An app built this way stays an ordinary Macaly app: Macaly says you can open it in its editor, browse the version history, roll back or continue with its own agent. Other apps and their connectors are listed on the Integrations hub.
Which tools does Macaly Cloud really give Claude?
- Claude directory sheet ↗2026-10-01Lists 16 tools by name, run_project_command among them, and none called bash.
- Macaly Cloud documentation (publisher) ↗undated, read 2026-10-01Describes a tool set that includes bash and two more tools absent from the sheet, and does not mention run_project_command.
What this page followsThe sheet is the more recent reading for the Claude connector; Macaly's page covers several AI clients and carries no date. Neither settles it for your account: once connected, the tool list Claude shows you is the reference.
Need help connecting Macaly Cloud to Claude?
A person reads every message.
