DADA Cloud

Documentation

Step-by-step guides for the console — from your first deploy to databases, domains, monitoring and driving the cloud from an AI agent. Plus the REST API and the MCP server for everything you want automated.

Browse the guidesMCP server

Guides

Each card is one whole job, from nothing to a working result.

Automation: REST API and MCP

The API works with the same objects as the console: project, app, database, domain, server. An app is a repository or an image plus environment variables; the platform assembles everything else, so a request never has to describe infrastructure.

Auth is a token in the Authorization header. The token carries your role in the project: whatever you cannot do by hand in the console, a request cannot do either. For deploys from someone else's CI there is a per-app deploy hook, so a pipeline never has to carry a full token.

State-changing calls are asynchronous: the request returns an operation id and the status is read separately. Logs come from the same API, so an on-call script or an AI agent sees exactly what the console shows.

REST API

Every console resource is available via /api/v1 with token auth.

curl -H "Authorization: Bearer $TOKEN" https://console.dada-tuda.ru/api/v1/projects

MCP server

61 tools for an AI agent: exactly your account's permissions, browser sign-in, no tokens in config files.

How to connect

Open console

Log in to the panel for your API access token and all project resources.

API and developer FAQ

Where are the DADA Cloud docs?

On this page: the Guides section is a set of step-by-step how-tos for the console, from your first deploy to billing, roles and connecting an AI agent over MCP.

Does DADA Cloud have a REST API?

Yes. Everything the console does — app deploys, servers, databases, domains and monitoring — is available over the /api/v1 REST API with token auth.

Where do I get an API token?

In the console: log in, open a project, and your access token and all resources are there.

What language are the docs in?

The step-by-step guides are currently in English; the marketing site itself is available in Russian and English.

How is the API different from a deploy hook?

A deploy hook is a single token-protected URL that triggers a rebuild of one app; it is handy to call from someone else's CI. The REST API is full control: create a project, provision a database, attach a domain, read logs.

Can an AI agent drive the cloud?

Yes. Besides REST there is an MCP server: the agent gets 61 tools and works with projects, apps, databases and logs under exactly the permissions your account has. The AI agents (MCP) section above has setup, the full tool reference and worked recipes.

Are there rate limits?

Metric and log reads are cached on the platform side, so polling every few seconds costs nothing. Mutating operations (deploys, resource creation) go through a task queue and return an operation id you can track.

Give your code a public address

Create an account and deploy your first app. The Free plan costs $0.

Create account