Deploy from your terminal — or let your AI coding agent do it.
Website · Quick start · CLI reference · MCP setup · Troubleshooting
CloudeIDE is a cloud development environment that runs in a browser tab — editor, AI agent, sandboxed execution and deployment, with nothing to install.
This repository is the public, developer-facing part: the cloudeide command-line tool, its MCP server, and the documentation for both. It is what you need if you want to drive CloudeIDE from your own terminal, or give an AI coding agent the ability to build and ship on your behalf.
The web IDE itself lives at cloudeide.com.
Two different problems, one binary:
- The CLI is for you.
cloudeide deploy .builds the current directory and puts it on a public URL, without opening a browser. - The MCP server is for your agent. Cursor, Claude Code and Codex can call the same operations directly — deploy, watch the build, read the log, roll back — instead of asking you to run commands and paste the output back.
The second one is the interesting half. An agent that can only write code has to hand the result to a human to ship. An agent with these tools closes the loop itself.
npm install -g cloudeidepnpm add -g cloudeide, yarn global add cloudeide and bun add -g cloudeide all work too. Node 20 or newer.
cloudeide login # paste an API token from Settings → API tokens
cloudeide deploy . # build the current directory and publish itThat's the whole flow. deploy prints a live URL when it finishes.
To let an editor drive it instead:
cloudeide install cursor # or: claude-code, codexThat writes the correct MCP config for that tool, in the right place, in its own format. It merges into whatever config is already there rather than overwriting it, and it never writes your token into the file — the config is safe to commit.
See the quick start for the longer version.
| Guide | What's in it |
|---|---|
| Quick start | First deploy, start to finish |
| Installation | Package managers, Node versions, upgrading, uninstalling |
| CLI reference | Every command, flag and exit code |
| MCP setup | Cursor, Claude Code and Codex — plus all 13 tools |
| Configuration | Config file, environment variables, precedence |
| Authentication | Tokens, scopes, rotation, what to do if one leaks |
| Examples | CI pipelines, preview deploys, scripting against --json |
| Troubleshooting | Errors by symptom, and what each actually means |
| FAQ | Questions that come up repeatedly |
| Editor | Config written | Scope |
|---|---|---|
| Cursor | .cursor/mcp.json |
Project, or ~/.cursor/mcp.json with --global |
| Claude Code | .mcp.json |
Project — commit it and your whole team gets the tools |
| Codex | .codex/config.toml |
Project, or ~/.codex/config.toml with --global |
Run cloudeide doctor afterwards. It checks each tool's configuration and tells you what's wrong rather than just failing.
Every command takes --json, which prints one JSON document on stdout and nothing else — no progress lines, no colour. Exit codes are specific (3 not authenticated, 7 out of credits, 9 server unreachable), so a script can branch on the failure rather than on a string match.
URL=$(cloudeide deploy . --env production --json | jq -r '.liveUrl')See examples.
- A bug, or something that behaves surprisingly — open an issue
- A security vulnerability — please do not open a public issue; see SECURITY.md
- Account, billing or deployment questions — the dashboard at cloudeide.com
Issues and pull requests are welcome. CONTRIBUTING.md covers how to report something usefully and what to expect from review.
MIT — see LICENSE.