# Clever Cloud MCP

> Clever Cloud Developer PaaS API lets you manage your entire cloud infrastructure through natural conversation. Use your AI agent to list applications, provision databases, trigger deployments, and oversee multiple organizations without leaving your IDE or chat window. It puts full control of your PaaS resources directly into your workflow.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Tags:** paas, cloud-hosting, deployment-automation, infrastructure-as-code, clever-cloud

## Description

This MCP connects your Clever Cloud account to any compatible AI client, giving you direct command over your Platform as a Service (PaaS) environment. You manage everything—from initial setup to final deployment—by simply talking to your agent. Need to check which apps are running? Ask it. Want to spin up a new database add-on or see the logs for an old service? It handles that, too. The system lets you orchestrate complex processes like creating entire organizational units and then building applications within them. If you're used to juggling multiple dashboards and terminal commands just to check status, this changes that. By connecting through Vinkius, your AI agent becomes a central hub for all your infrastructure needs, letting you focus on the code while it keeps track of what’s deployed.

## Tools

### create_application
This tool creates a brand new application within your Clever Cloud account with provided settings.

### create_organization
Use this to establish and set up an entirely new organizational unit.

### delete_application
This tool removes a specific application from your cloud environment.

### get_addon
It fetches all the detailed specs for one particular provisioned add-on service.

### get_application_logs
It gathers and displays recent operational logs from any specific application.

### get_application
This tool pulls up all the metadata and configuration details for a single app.

### get_current_user
This confirms your identity and shows you the current access rights assigned to your account.

### list_addons
It lists every single add-on service that is currently running or provisioned in your account.

### list_applications
This command retrieves a complete list of all applications associated with your cloud setup.

### list_instances
It shows you a listing of every running instance across the platform.

### list_organization_applications
This lists all applications that belong specifically to one organization unit.

### list_organizations
It retrieves a list of every separate organizational container you have access to.

### provision_addon
Use this tool to create and set up a new, specified add-on service like a database instance.

### trigger_deployment
This immediately starts the build and deployment process for any selected application.

## Prompt Examples

**Prompt:** 
```
List all my Clever Cloud applications.
```

**Response:** 
```
I've retrieved your applications. You have 3 active apps: 'frontend-prod' (ID: app_123), 'api-gateway' (ID: app_456), and 'worker-service' (ID: app_789).
```

**Prompt:** 
```
Trigger a new deployment for application app_456.
```

**Response:** 
```
Deployment triggered successfully for 'api-gateway' (app_456). The platform is now building and deploying your latest changes.
```

**Prompt:** 
```
Show me the details of my provisioned add-ons.
```

**Response:** 
```
You have 2 active add-ons: a PostgreSQL database (ID: addon_abc) and a Redis instance (ID: addon_xyz). Both are currently in 'running' status.
```

## Capabilities

### Check User Status
It retrieves information about your current account settings and access levels.

### Manage Applications
You can create, delete, or get detailed metadata for any application running on the platform.

### Provision Services (Add-ons)
It lets you list existing services like databases and provision brand new ones instantly.

### Automate Deployments
You can trigger a full deployment cycle for any application directly from your conversation.

### Organize Structures
It manages multiple organizational units, allowing you to list them and see which apps belong where.

## Use Cases

### The daily deployment checkup
A DevOps engineer needs to confirm that 'frontend-prod' is running smoothly. Instead of navigating the web dashboard, they ask their agent via `get_application` for metadata and then use `get_application_logs` to see the last 50 entries—all in one prompt.

### Scaling up a new feature
A full-stack developer realizes the current app needs more processing power. They ask their agent, and it uses `list_addons` to check what's available before calling `provision_addon` to spin up a larger Redis instance.

### Onboarding a new business unit
A Technical Lead needs to manage apps for an entirely new subsidiary. They start by using `list_organizations` and then use `create_organization` before mapping the first application via `create_application`.

### Fixing a production bug
A developer spots an issue in a service. Instead of logging into the platform, they prompt their agent to 'trigger deployment' for that specific app, rolling out the fix instantly and verifying it with `list_instances`.

## Benefits

- You eliminate context switching. Instead of jumping between the console, an admin dashboard, and your code editor, you manage everything in one conversation window.
- Deployment becomes a single prompt. You don't have to manually initiate a deployment; just ask it to 'trigger deployment for app_xyz,' and it handles the rest.
- Resource management is instant. Need a new PostgreSQL database? Simply ask your agent to provision an add-on, pulling all the necessary details without leaving your current task.
- Organization oversight is simplified. You can list organizations and applications using `list_organizations` and `list_application_logs`, giving you a bird's-eye view of complex multi-tenant setups.
- Debugging gets faster. If an app fails, instead of digging through log files, you ask the agent to fetch application logs, getting immediate status updates right in your chat.

## How It Works

The bottom line is, you talk to your agent like talking to a coworker who already has credentials for every system in the company.

1. Subscribe to this MCP and input your Clever Cloud API credentials (Consumer Key, Secret, and Tokens).
2. Your AI client reads the configuration and validates access against your cloud account.
3. You ask it a question—'List all my applications,' or 'Provision a Redis instance.' It runs the command and reports the result.

## Frequently Asked Questions

**How do I check if my current user account has enough permissions? (get_current_user)**
You run `get_current_user`. This immediately pulls up your profile and settings, confirming exactly what access levels you have for the cloud environment.

**Can I list all apps in just one specific organization? (list_organization_applications)**
Yes. You use `list_organization_applications`. This narrows down the scope, letting you see only the applications that belong to a single defined organizational unit.

**What's the first step if I need to add a new database? (provision_addon)**
First, run `list_addons` to confirm what types of services are available. Then, use `provision_addon`, providing all the required configuration details in your prompt.

**How do I make sure my code changes go live? (trigger_deployment)**
You simply ask the agent to 'trigger deployment' for that application. It handles the sequence, starting the build and pushing out the latest changes immediately.

**What configuration details does the tool `create_application` need to successfully provision a new service?**
The tool requires essential setup parameters like the desired name and initial runtime environment. You must provide these config fields in the request body for the MCP to execute the creation.

**If an application is throwing runtime errors, how can I use `get_application_logs` to diagnose the issue?**
Running this tool fetches detailed historical logs for a specific app ID. This lets your agent pinpoint exactly when and why the failure occurred, speeding up debugging immensely.

**Before managing specific apps, how does `list_organizations` help me map out all the accounts I belong to?**
It returns a complete list of every organization ID and name you have access to. This gives your agent the necessary scope before listing resources in any single unit.

**What's the process for safely removing an entire service using `delete_application`?**
The tool deletes the specified application ID completely. Since this action is irreversible, always confirm dependencies with your agent before triggering it through the MCP.

**Can I trigger a new deployment for a specific application using this server?**
Yes! Use the `trigger_deployment` tool by providing the `appId`. You can optionally specify deployment options like a commit ID in the request body.

**How do I see all the databases and services (add-ons) I have active?**
Simply use the `list_addons` tool. It will return a list of all provisioned add-ons, including databases and other managed services across your account.

**Is it possible to manage applications within a specific organization?**
Yes. You can use `list_organizations` to find the `orgId`, and then use `list_organization_applications` to see only the apps belonging to that specific organization.