MCP Server

redu.cloud provides a Model Context Protocol (MCP)  server at mcp.redu.cloud. Connect it to Claude Code, Claude.ai, or ChatGPT to manage your cloud infrastructure in natural language.

Create a large Ubuntu instance called web-prod with my default keypair

What instances am I running? Stop the staging one.

Deploy a reduOS instance and give me the SSH command when it's ready.

Connect your agent

Recommended (OAuth), pick your client:

claude mcp add --transport http redu https://mcp.redu.cloud/mcp --client-id redu-mcp

codex mcp add redu --url https://mcp.redu.cloud/mcp --oauth-client-id redu-mcp

The server is available as soon as you are signed in. It works with any MCP client; Claude Code and Codex are shown above.

Alternative, connect with an API key (for CI, headless, or a committable team config).

Generate a key at Account → API Keys, then add it inline:

claude mcp add --transport http redu-cloud https://mcp.redu.cloud/mcp --header "x-api-key: YOUR_KEY"

Or use a .mcp.json file in your project root, which keeps the key out of the command:

{
  "mcpServers": {
    "redu-cloud": {
      "type": "http",
      "url": "https://mcp.redu.cloud/mcp",
      "headers": { "Authorization": "Bearer ${REDU_API_KEY}" }
    }
  }
}

Set your key as an environment variable so it never lives in the file:

export REDU_API_KEY=your_api_key_here

The .mcp.json file is safe to commit, the ${REDU_API_KEY} placeholder expands at load time.

Connect from Claude.ai

Claude.ai supports MCP servers (rolling out 2025–2026).

1. Open Claude.ai → Settings → Integrations → Add MCP server
2. Enter: https://mcp.redu.cloud/mcp
3. Authenticate with your redu.cloud account (OAuth via Keycloak)

Connect from ChatGPT

redu.cloud works as a ChatGPT Custom GPT Action.

1. Create a Custom GPT → Configure → Actions
2. Set the schema URL to: https://mcp.redu.cloud/.well-known/oauth-protected-resource
3. Authentication: OAuth 2.0, use your redu.cloud Keycloak credentials

Available tools

Example: create an instance

On a fresh account, set up an SSH keypair first (import your own key, or ask your agent to generate one):

“Import my SSH key, here it is: ssh-ed25519 AAAA…”

your agent will call import_keypair and confirm the name. Then:

“Create a medium Ubuntu instance called api-server with my default keypair. Use the first available network.”

your agent will call plan_instance to gather the options, then create_instance with the right IDs. You don’t need to know image IDs or flavor IDs.

Example: deploy an app from a Git repo

“Deploy https://github.com/me/my-app  to redu.”

your agent calls plan_deploy first to scan the repo, size the VM, estimate cost, and check quota, then shows you the plan before provisioning. On approval it calls deploy_app, which builds the container on a VM and serves it at https://my-app.redu.cloud.

Need a database? Just say so, deploy_app accepts database: "managed" (a dedicated managed-Postgres server, auto-provisioned and wired) or database: "single_vm" (Postgres on the app VM). Either way the connection env (DATABASE_URL + DATABASE_HOST/PORT/USER/PASSWORD/NAME, plus the legacy PG*/MYSQL_*) is injected automatically, frameworks like Rails, Django, and Prisma pick it up without manual mapping. You can request Postgres extensions (db_extensions: ["pgvector", "postgis"]) and a superuser DB role (db_superuser: true).

Multi-container apps, if the repo ships a docker-compose.yml / compose.yaml, plan_deploy flags it and your agent uses deploy_compose instead. It runs the whole stack on one VM via podman-compose up -d --build and exposes one service (you pass its host port) at https://<name>.redu.cloud. By default the compose file’s own db service is used; pass database: "single_vm" or "managed" to add a Postgres outside the compose file, its connection env is appended to the project’s .env (redu never rewrites your compose file).

Example: deploy reduOS

“Deploy a reduOS full-stack instance on a large flavor.”

your agent will call create_instance with cloud_init_template: "reduos", which automatically:

• Picks port 3006 for the dashboard DNS entry
• Injects the full reduOS setup cloud-init
• Starts setup in the background (takes 15–25 min)

After creation, ask:

“Check if the reduOS instance is ready and give me the SSH command.”

API key vs OAuth

Generate an API key at console.redu.cloud/category/user/api-keys .