Get connected

Your assistant, connected to your cloud

Copy the setup prompt into your AI assistant, sign in through your browser, and start working with your Codara Cloud apps.

Connect with one prompt

Use an assistant that can run commands on your computer, such as Claude Code, Cursor or Codex. Paste this into its conversation. The assistant detects your setup, installs both tools and guides you through sign-in.

Paste into your AI assistant

Connect to Codara Cloud:1. Install the CLI and local MCP using https://codaracloud.com/docs/mcp.2. Run codaracloud login and let me sign in through the browser.3. Add codara-cloud to your MCP configuration, then verify my account and list my workspaces. Tell me if a restart is needed.

Complete sign-in at console.codaracloud.com when the browser opens. Choose the account and access you want the assistant to use.

One login, shared by both tools

MCP runs locally and uses your saved CLI login. You do not need to copy an API key into a chat or have access to Codara's source code.

Check the connection

Restart your assistant if requested, then paste this to verify the actual connection:

Read-only connection check

Use codara_search to find auth_status, then codara_call to check my connected account and access. List my accessible workspaces and projects. Do not create or change anything, and do not display credentials.

A successful check identifies your account and lists the workspaces you can access. An empty workspace is valid; an installed server alone does not confirm a working login.

Prefer manual setup?

Open Developer tools in the console for instructions tailored to your computer and assistant, including desktop configuration.

macOS and Linux

Terminal

curl -fsSL https://console.codaracloud.com/v1/cli/install.sh | shcurl -fsSL https://console.codaracloud.com/v1/mcp/install.sh | shcodaracloud --api https://console.codaracloud.com logincodaracloud whoami

Windows

PowerShell

irm https://console.codaracloud.com/v1/cli/install.ps1 | iexirm https://console.codaracloud.com/v1/mcp/install.ps1 | iexcodaracloud --api https://console.codaracloud.com logincodaracloud whoami

The adapter needs Node.js 20 or newer. The installers download published releases and verify their checksums. For desktop apps, use the absolute Node, adapter and CLI paths shown by the guided setup; their PATH may differ from your terminal.

Setting	Use
Transport	Local STDIO
Server name	codara-cloud
CODARA_API_BASE	https://console.codaracloud.com
CODARA_CLI_BIN	Full path to the codaracloud executable used for login.

What your assistant can do

The MCP exposes two discovery tools. codara_search finds operations and their input schema; codara_call runs a discovered operation. Your assistant can search by task, so there is no fixed tool list to memorize.

Deploy: publish a folder, ZIP or HTML file, connect GitHub, and inspect build results.
Operate: read logs, diagnose an environment, manage domains, and pause or resume services.
Manage data: create and connect databases, volumes and buckets, and inspect backups.
Give feedback: search for feedback_submit to report a problem or suggest an improvement. feedback_list shows your submissions and responses.

Example request

Check which Codara Cloud account is connected, then show my apps and their current status. Use codara_search to find the operations. Do not change anything.

Choose the right access

The CLI and MCP use the permissions of the selected credential. Ordinary access stays within its organization or workspace. Administrator access is a separate, explicit browser approval flow; it is not part of normal setup.

For unattended development, create a Development only token in the console and store it directly in the local configuration. Keep credentials out of conversations. Use environments_prepare_development for development work; publishing to production is a separate release step.

Permissions enforce the boundary

Operations retain their preview and confirmation requirements. Those checks do not replace credential permissions: a prompt cannot grant access to another customer's resources.

Updates and troubleshooting

Installed adapters check for updates daily. Verified updates load after restarting the assistant; a failed update leaves the last verified adapter in place.
Server missing: check the absolute Node, adapter and CLI paths, then restart the assistant.
Unauthorized: run codaracloud login again and check codaracloud whoami.
Forbidden: check the credential's workspace and permissions. A Development only token cannot operate production.

For deployment notifications, see Logs and metrics.

Last updated 14 September 2026