CloudeIDE MCP server

Read from the package source without running it. The installed server may list more.

• cloudeide_cancel_deploymentwrite action

  Stop a deployment that is still running. Nothing is published. Use it when a deploy was started by mistake, or the user asked to stop. Credits already spent on build time are not refunded.

• cloudeide_create_projectwrite action

  Create a new project. A project is a deploy target with its own URL, environment variables and history. If no name is given the server generates a readable one. Only create a project when the user has asked for a new one \u2014 deploying to an existing project does not need this.

• cloudeide_deploywrite action

  Build and publish a directory, and return immediately with a deployment id. This SPENDS CREDITS and counts against the account's daily deploy limit, so do not call it speculatively or to test whether something works. It does NOT wait for the build: poll cloudeide_deployment_status with the id it returns. Only one deploy per account can run at a time; a second call while one is running is refused.

• cloudeide_deployment_logs

  Read a deployment's full build log. Use it when a deploy failed and you need to see why \u2014 the status tool gives a one-line summary and the last few lines, this gives everything. Changes nothing.

• cloudeide_deployment_status

  Check whether a deployment is still running, and what happened if it is not. Returns inFlight, status, the live URL on success, and the reason and phase on failure. Poll this after cloudeide_deploy rather than calling deploy again. Changes nothing and costs nothing.

• cloudeide_list_deployments

  List recent deployments for a project, newest first, with their status and duration. Use it to find the id of a previous deploy \u2014 for instance to roll back to the last one that worked. Changes nothing.

• cloudeide_list_domains

  List custom domains attached to a project, with their verification and SSL status. Changes nothing.

• cloudeide_list_env_vars

  List the environment variable NAMES set for a project, and which environments each applies to. Values are never returned, including for non-secret variables \u2014 read them from your own source if you need them. Changes nothing.

• cloudeide_list_projects

  List the deployable projects on this account, with their ids and slugs. Use it to resolve a project name the user gave you into an id before deploying. Changes nothing.

• cloudeide_rollback

  Republish an earlier deployment's files, making it live again. This CHANGES THE LIVE SITE immediately. It does not rebuild, so it is fast and cannot fail the way a deploy can. Use it to recover from a bad deploy. Confirm with the user before rolling back production.

• cloudeide_set_env_var

  Set an environment variable for a project. It takes effect on the NEXT deploy, not immediately. Mark it secret when the value is a credential: a secret's value is hidden in build logs. Do not set a variable to a value the user has not given you.

• cloudeide_usage

  Show how much of the account's daily deploy limit, storage and credits have been used. Check this before a deploy if you are unsure whether one will be allowed. Changes nothing.

• cloudeide_whoami

  Identify the account this connection is using and what it is allowed to do. Call this first: it confirms the credential works and returns the scopes, so you can tell in advance whether deploying will be permitted rather than finding out from a failed deploy. Costs nothing and changes nothing.

• Code scan2 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 37 days ago12/15
• Maintainer identityregistry namespace matches repository owner; website matches verified namespace9/10

Safety score

72/100

higher than 33% of 1,119 Developer tools servers

Tools

13

the typical Developer tools server has 7

Tools that change things

23%

typical: 5%. Fewer write tools means less an agent can break

Downloads a week

31

more than 15% of 442 Developer tools servers with a package

CloudeIDE: common questions

Is CloudeIDE MCP server safe?

Mostly: it is graded B (72/100). Read the CloudeIDE safety report

How do I install CloudeIDE?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does CloudeIDE need an API key?

Yes. The registry entry asks for CLOUDEIDE_TOKEN.

Is CloudeIDE maintained?

The last commit was 44 days ago (2026-09-22). The latest release is v0.1.2.

What can I use instead of CloudeIDE?

Servers from other publishers that do the same job: walkerOS Flow MCP server, Omnara MCP server and Repowise MCP server.

How does CloudeIDE compare with other Developer tools MCP servers?

safety score 72/100 (higher than 33% of 1,119 Developer tools servers); tools 13 (the typical Developer tools server has 7); tools that change things 23% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.