DADA Cloud MCP server: run your cloud from Claude
Connect the platform to Claude Code, Claude Desktop, Cursor or any MCP client and ask in plain language: spin up a server, deploy this repo, show me why the app is down. The agent gets 41 console tools, signs in as you through the browser, and works with exactly the permissions your account has. Server URL: https://console.dada-tuda.ru/mcp.
Connection details
Copy these into your client — nothing else to configure.
Claude Code
/plugin marketplace add DadaDevelopment/dada-cloud-console/plugin install dada-cloud@dada-cloudClaude Desktop · Cursor · any MCP client
https://console.dada-tuda.ru/mcpOAuth Client ID: dada-mcpConnect in two minutes
The fastest path is the Claude Code plugin — no tokens, no keys to paste.
Add the marketplace
In Claude Code run /plugin marketplace add DadaDevelopment/dada-cloud-console once.
Install the plugin
/plugin install dada-cloud@dada-cloud. On Claude Desktop add a custom connector pointing at https://console.dada-tuda.ru/mcp with OAuth Client ID dada-mcp instead.
Log in through the browser
On first use your browser opens the DADA ID login. Approve it — the client obtains and refreshes the token itself, nothing goes into a config file.
Ask in plain language
"Deploy this repo into a new project", "show the last hour of logs", "set this environment variable". The agent calls the matching actions and reports the operation result.
What the agent can do over MCP
41 platform tools
Projects, apps, builds, databases, domains, environment variables, servers, logs and throwaway sandbox boxes — the same API the web console runs on, cut down to a set an agent does not get lost in.
Exactly your permissions
The agent only sees projects your account has a role on, and every write goes through the same permission check as a click in the console. MCP is not a side door.
No tokens in config files
Sign-in is standard browser OAuth. Keys never sit in settings files or shell history, and the short-lived token is refreshed by the client.
Logs for diagnosis
The agent reads app and VM logs, build status and operation state — enough for it to find why an app is failing and propose the fix itself. It cannot delete apps or databases: that stayed in the console.
Ready-made playbooks
The server ships three guided prompts: deploy-app, configure-env and diagnose-app. Clients pick them up with no extra setup.
Any MCP client
Claude Code, Claude Desktop, Cursor and anything else that speaks Model Context Protocol. Clients without browser login can send an Authorization: Bearer header with a DADA ID token.
MCP FAQ
Model Context Protocol is the standard by which an AI client connects to an external service and receives the list of actions it may call. DADA Cloud publishes its API as such a toolset, so the agent operates the cloud itself instead of suggesting commands for you to type.
Get your backend live from GitHub today
Connecting a repo takes a minute. You only pay for what you actually use.
Create account