MCP Server · Claude Integration

Manage your cloud by talking to Claude.

redu.cloud has a native Model Context Protocol server. Add it to Claude Code in one command and start managing infrastructure through conversation — no console, no docs lookup.

Install in Claude Code
claude mcp add --transport http redu-cloud https://mcp.redu.cloud/mcp

Requires Claude Code CLI and a redu.cloud API key (generate one in Account → API Keys).

Get started freeView API docs
How it works

Three steps to cloud infrastructure via Claude.

01

Sign up and get an API key

Create your redu.cloud account and generate an API key from Account → API Keys. You get £200 credits to start.

02

Add the MCP server

Run the command above in your terminal. Claude Code will prompt you to set your API key.

03

Talk to Claude

Open Claude Code and start asking. "Deploy a new instance", "show me the logs for my staging server", "take a snapshot before I deploy".

See it in action

A real conversation with Claude.

Open Claude Code, connect the MCP server, and start talking.

Claude Code
You
Deploy a new Ubuntu instance with 4GB RAM in my private network.
Claude
Creating instance prod-app-01 (m1.medium, Ubuntu 22.04) on network private-eu-west-1...
✓ Instance launched · ID: a4f9c2d1
✓ Security groups: default, app-access
✓ SSH ready on port 22417

SSH command:
  ssh ubuntu@prod-app-01.redu.cloud -p 22417
You
Take a snapshot before I deploy.
Claude
✓ Snapshot snap-20260531-prod-app-01 created.

You're good to deploy.
Available tools

30+ tools across 4 categories.

Instances
  • list_instancesList all instances with status, IP, and uptime.
  • create_instanceLaunch a VM — size, image, keypair, DNS, and volume.
  • delete_instanceTerminate an instance and release its resources.
  • instance_actionStart, stop, reboot, or resize a running instance.
  • get_ssh_commandGet the SSH command with the forwarded TCP port.
Storage
  • list_snapshotsList instance snapshots with size and date.
  • create_snapshotSnapshot an instance before deploys or migrations.
  • delete_snapshotRemove a snapshot to free block storage.
  • list_volumesList block storage volumes with attachment status.
  • create_volumeCreate a new volume and attach to an instance.
  • list_backupsList volume backups.
Networking
  • list_security_groupsList security groups and their rules.
  • list_private_networksList private networks with CIDR and status.
  • list_dns_entriesList DNS proxy host entries.
  • list_domainsList verified custom domains on your account.
Infrastructure
  • list_clustersList autoscaling clusters with status.
  • list_flavorsList available instance sizes and pricing.
  • list_imagesList available OS images.
  • list_keypairsList SSH keypairs on your account.
  • import_keypairRegister your SSH public key — required before creating instances.
  • delete_keypairRemove an SSH keypair by name.
  • list_regionsList available deployment regions.
Example prompts

Things you can say to Claude.

“

Deploy a new Ubuntu instance with 4GB RAM in my private network.

“

Show me the logs from my production server — last 100 lines.

“

Take a snapshot of my database server before I run the migration.

“

What's the SSH command for my staging instance?

“

Deploy reduOS on an XLarge instance with my OpenAI key.

“

Stop all my non-production instances to save credits.

Autocoding agents

Or let a fleet of agents write the code.

The same connection can spin up a fleet of agents that read tasks from your repo, implement them, run your tests, and open pull requests — overnight, in parallel, using your own Claude subscription (no per-token API charges).

01

Set up the fleet

In Claude Code: "Set up autocoding agents for my repo with 3 workers." It provisions a controller plus worker VMs on your account and seeds a starter ROADMAP.

02

Add tasks to ROADMAP.md

List scoped tasks and mark each one (agent-ready). Each task becomes one focused pull request — best for endpoints, tests, bugfixes, and UI changes.

03

Wake up to merged PRs

Workers pick up tasks in parallel, write the code, run the tests, and open PRs on GitHub. Review and merge like any other PR. After each merge, the fleet learns.

Full setup guide →
Common issues

Setup troubleshooting.

claude mcp list shows nothing even though the server is configured

Some Claude Code builds silently ignore servers stored under projects[...].mcpServers in ~/.claude.json — which is where claude mcp add writes by default. No error is emitted; the tools just never load.

Fix: use a .mcp.json file in your project root instead. This path is read reliably by both the CLI and the desktop app:

{
  "mcpServers": {
    "redu-cloud": {
      "type": "http",
      "url": "https://mcp.redu.cloud/mcp",
      "headers": { "Authorization": "Bearer ${REDU_API_KEY}" }
    }
  }
}
Set REDU_API_KEY as an env var — the placeholder expands at load time so your key never lives in the file.

Alternatively, force user scope when adding: claude mcp add --transport http -s user redu-cloud https://mcp.redu.cloud/mcp

Should I commit .mcp.json to git?

Yes — if you use the ${REDU_API_KEY} placeholder. The file contains no secrets; every team member sets their own key as an env var and picks up the server automatically.

If you hard-code your token instead, add .mcp.json to .gitignore so you don't leak your key.

curl returns Bad Request: initialize first on Windows / PowerShell

PowerShell mangles inline JSON in -d '...'. Save your request body to a file and use curl.exe (not the PowerShell alias) with --data-binary:

curl.exe --data-binary "@body.json" https://mcp.redu.cloud/mcp ...

Start building with Claude today.

Sign up for redu.cloud, generate an API key, and add the MCP server. Your entire cloud — in one conversation.

Start for free · £200 credits included