Integration

Clever Cloud integration

Clever Cloud is a European platform as a service: it runs applications (Node.js, Java, Python, PHP, Go, Docker and more) and managed add-ons (PostgreSQL, MySQL, Redis, MongoDB, object storage and more). With this API you can list organisations, applications and add-ons, create, scale, configure, redeploy and stop applications, set environment variables, manage domains, TCP and UDP redirections, service dependencies and tags, create, link and delete add-ons, follow deployments and instances, and manage organisation members. Not exposed: reading environment variables and add-on credentials (they hold secrets), billing (credits, invoices, payment methods and purchases, whose v2 routes are deprecated), OAuth consumers, service and API tokens, the add-on vendor API, account, password, MFA and SSH key management, and login flows. Authentication is a Clever Cloud API token (created in the Console or with clever tokens create, valid up to one year) sent as a Bearer token to the API bridge.

Connect Clever Cloud How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Clever Cloud.Built from the 59 Clever Cloud tools below, on the connection you add once.

What you can do with Clever Cloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Addon, 8 operations

create_addonCreate addonPOSTCreates (provisions) an add-on such as a PostgreSQL, MySQL, Redis or MongoDB database from a provider id and a plan id (from list_addon_providers) in a region. Paid plans are billed to the owner.
delete_addonDelete addonDELETEDeletes an add-on. This cannot be undone.
get_addonGet addonGETReturns one add-on: name, real id, region, provider, plan with its features, creation date and the names of the configuration variables it exposes.
link_addonLink addonPOSTLinks an existing add-on to an application, so the add-on's configuration variables become part of the application's environment; redeploy the application (redeploy_application) to use them.
list_addonsList addonsGETLists the add-ons (databases and other managed services) of an organisation or of the personal space: id, name, real id, region, provider, plan with its features, creation date and configuration variable names.
list_application_addonsList application addonsGETLists the add-ons linked to an application (their configuration is injected into its environment): id, name, provider, plan, region and the names of the configuration variables they expose.
rename_addonRename addonPUTRenames an add-on and returns it with its provider, plan and region.
unlink_addonUnlink addonDELETEUnlinks an add-on from an application, removing its configuration variables from the application's environment (redeploy to apply). The add-on itself is kept.

Instance, 7 operations

cancel_deploymentCancel deploymentDELETECancels an ongoing deployment of an application (one whose state is WIP in list_deployments).
get_instance_typeGet instance typeGETReturns one runtime by type and version from list_instance_types: variant, allowed, default and build flavors, deployment methods. Where variants share a type and version (java, magic), only one comes back: take variant ids from list_instance_types.
list_addon_instancesList addon instancesGETLists the instances running an add-on: id, IP and port, state, flavor, deployment number and id, and creation date.
list_application_instancesList application instancesGETLists the instances of an application: id, IP and port, state, flavor, commit, deployment number and id, instance number and creation date.
list_instance_typesList instance typesGETLists the runtimes an application can be created with (Node.js, Java, Python, PHP, Ruby, Go, Rust, .NET, Docker, static and more): type, version, variant id and slug, flavors, default and build flavors. Needs no token.
redeploy_applicationRedeploy applicationPOSTStarts a new deployment of an application (restarts it), on its last pushed commit or on a given commit, optionally without the build cache. Returns the deployment id.
stop_applicationStop applicationDELETEStops an application: all its instances are undeployed. redeploy_application starts it again.

Application, 6 operations

create_applicationCreate applicationPOSTCreates an application from an instance type (type, version and variant id from list_instance_types) in a zone, with flavors and instance counts. Returns it with its id and the Git URL to push code to.
delete_applicationDelete applicationDELETEDeletes an application. This cannot be undone.
get_applicationGet applicationGETReturns one application: name, description, zone, instance type and scaling (flavors, min and max instances), domains, deployment branch, last commit, Git deploy URL, build flavor, settings and state.
list_addon_applicationsList addon applicationsGETLists the applications an add-on is linked to.
list_applicationsList applicationsGETLists the applications of an organisation or of the personal space: id, name, zone, instance type and scaling, domains, deployment branch, last commit, Git deploy URL, state and creation date.
update_applicationUpdate applicationPUTChanges an application's settings: name, description, scaling (flavors and min and max instances), zero-downtime, sticky sessions, cancel on push, force HTTPS, separate build, task mode. Only the fields sent change.

Member, 4 operations

add_memberAdd memberPOSTInvites a person to an organisation by email, with a role (ADMIN, MANAGER, DEVELOPER or ACCOUNTING) and an optional job title. Only admins and managers can add members.
list_membersList membersGETLists the members of an organisation: each user's id, email and name, their role (ADMIN, MANAGER, DEVELOPER or ACCOUNTING) and job title.
remove_memberRemove memberDELETERemoves a member from an organisation, identified by the user id from list_members. Only admins and managers can remove members.
update_memberUpdate memberPUTChanges the role (ADMIN, MANAGER, DEVELOPER or ACCOUNTING) or the job title of an organisation member, identified by the user id from list_members.

Tag, 4 operations

add_addon_tagAdd addon tagPUTAdds a tag to an add-on and returns the add-on's tags.
add_application_tagAdd application tagPUTAdds a tag to an application and returns the application's tags.
remove_addon_tagRemove addon tagDELETERemoves a tag from an add-on and returns the remaining tags.
remove_application_tagRemove application tagDELETERemoves a tag from an application and returns the remaining tags.

Dependency, 3 operations

add_dependencyAdd dependencyPUTMakes an application depend on another application, so the other application's exposed configuration is injected into its environment.
list_dependenciesList dependenciesGETLists the applications this application depends on (service dependencies): their exposed configuration is injected into this application's environment.
remove_dependencyRemove dependencyDELETERemoves a service dependency between two applications.

Favourite, 3 operations

get_favourite_domainGet favourite domainGETReturns the primary (favourite) domain name of an application, the one Clever Cloud links to by default. Answers a not-found error when none is set; list_domains lists the attached domains.
set_favourite_domainSet favourite domainPUTSets the primary (favourite) domain name of an application, the one Clever Cloud links to by default (see list_domains for the attached ones).
unset_favourite_domainUnset favourite domainDELETEClears the primary (favourite) domain name of an application.

Tcp redir, 3 operations

create_tcp_redirectionCreate tcp redirectionPOSTCreates a TCP redirection to an application's port 4040 in a namespace (default, cleverapps or a dedicated one) and returns the public port Clever Cloud assigned (above 5000). Free while in beta.
delete_tcp_redirectionDelete tcp redirectionDELETEDeletes a TCP redirection of an application, identified by its public port and namespace.
list_tcp_redirectionsList tcp redirectionsGETLists the TCP redirections of an application: for each namespace, the public port Clever Cloud assigned to reach the application's port 4040 over raw TCP.

Udp redir, 3 operations

create_udp_redirectionCreate udp redirectionPOSTCreates a UDP redirection for an application in a namespace and returns the public port Clever Cloud assigned.
delete_udp_redirectionDelete udp redirectionDELETEDeletes a UDP redirection of an application, identified by its public port and namespace.
list_udp_redirectionsList udp redirectionsGETLists the UDP redirections of an application: for each namespace, the public port Clever Cloud assigned to it.

Vhost, 3 operations

add_domainAdd domainPUTAttaches a domain name to an application: a custom domain (point its DNS to Clever Cloud) or a unique subdomain of cleverapps.io.
list_domainsList domainsGETLists the domain names (FQDNs) attached to an application, custom domains and cleverapps.io subdomains alike.
remove_domainRemove domainDELETEDetaches a domain name from an application.

Addonprovider, 2 operations

get_addon_providerGet addon providerGETReturns one add-on provider by id (for example postgresql-addon): description, regions, plans (id, name, slug, zones, features) and the features they describe.
list_addon_providersList addon providersGETLists the add-on providers (PostgreSQL, MySQL, Redis, MongoDB, Elasticsearch, Cellar object storage, Keycloak and more) with their regions and plans (plan id, name, slug and features). Needs no token.

Env, 2 operations

delete_environment_variableDelete environment variableDELETERemoves one environment variable from an application. The change applies at the next deployment (redeploy_application). Returns the application.
set_environment_variableSet environment variablePUTCreates or replaces one environment variable of an application. The change applies at the next deployment (redeploy_application). Returns the application.

Organisation, 2 operations

get_organisationGet organisationGETReturns one organisation by id: name, description, billing email, company, address, country, VAT number and VAT state.
list_organisationsList organisationsGETLists the organisations you belong to, each with its id (orga_...), name, description, billing email, company, address, country and VAT details.

Branch, 1 operation

set_deployment_branchSet deployment branchPUTSets the Git branch an application deploys from.

Buildflavor, 1 operation

set_build_flavorSet build flavorPUTSets the flavor of the dedicated build instance of an application (pico to 3XL, see list_flavors).

Dependent, 1 operation

list_dependentsList dependentsGETLists the applications that depend on this application (they receive its exposed configuration and are redeployed when it changes).

Deployment, 1 operation

list_deploymentsList deploymentsGETLists the deployments of an application, most recent first: id, uuid, date, state (WIP, OK, FAIL, CANCELLED or TASK_RUNNING), action, commit, cause, number of instances and author.

Flavor, 1 operation

list_flavorsList flavorsGETLists the instance flavors (sizes) from pico to 3XL with their CPU count, GPU count, memory and availability. Needs no token.

Namespace, 1 operation

list_namespacesList namespacesGETLists the reverse-proxy namespaces available to an owner for TCP and UDP redirections (default, cleverapps, or dedicated ones).

Self, 1 operation

get_current_userGet current userGETReturns the profile of the user who owns the API token: id (user_..., also the owner id of the personal space), email, name, language, creation date, whether the email is validated and the preferred MFA kind.

Summary, 1 operation

get_summaryGet summaryGETReturns an overview of everything the API token can reach: the user (id, name, email, personal applications and add-ons) and each organisation with your role, its applications (id, name, type, state, tags) and add-ons. Start here to find ids.

Zone, 1 operation

list_zonesList zonesGETLists the zones (regions) where applications and add-ons can run, for example par (Paris), rbx, ldn, mtl, sgp, syd and the HDS zones for health data (parhds, grahds, rbxhds). Needs no token.

Use Clever Cloud from Claude Code, Cursor or Codex

Connect Clever Cloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Clever Cloud operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Clever Cloud

Create your workspace
Sign up free. Nothing to install.
Connect Clever Cloud once
Add your Clever Cloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.