mcp is a remote MCP server that gives an AI agent 81 tools, among them architecture_diagram, attach_volume, check_agent_prerequisites. It answers at https://mcp.redu.cloud/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
architecture_diagram | Read-only. Fetches EVERY resource on your redu.cloud account (VMs, volumes, private networks, managed databases: Postgres/MySQL/MariaDB/ClickHouse/Redis/Qdrant, load balancers, and DNS access points) and renders ONE Mermaid diagram of the w Inputs: include_volumes, include_load_balancers, include_managed |
attach_volume | Attaches an EXISTING block volume to a running instance as an extra disk. This is how you finish a RESTORE after a VM is gone: restore_backup (volumeName) rebuilds the data into a new volume, then attach_volume puts that volume on a replace Inputs: volume_id, instance_id |
check_agent_prerequisites | Checks if your account has everything needed to run autonomous coding agents. Returns a checklist: API key validity, private network, SSH keypair, and billing. Safe to call anytime — read-only. Call this first before create_controller. Inputs: github_pat |
check_deploy_prerequisites | The deploy ENTRY GATE — run this first when a user wants to deploy. Verifies the account is ready and AUTO-SELECTS the network_id + keypair_name to pass to deploy_app (so you never hunt for them): (1) account reachable + quota, (2) a privat Inputs: mode |
create_api_key | Mints a NEW least-privilege redu API key for a deployed app or automation to use (e.g. to add a backup feature). GUARDRAIL: the first call does NOT create anything. It returns a confirmation the user must approve, because a key is a long-li Inputs: name, scopes, expires_in_days, confirm |
create_backup | Creates a backup, by volumeId or by instanceId (the instance's volume is resolved for you). The backup is held independently of the instance, so it survives the VM. Poll list_backups until the new backup is available. Inputs: volumeId, instanceId, backupName |
create_clickhouse | Provisions a managed ClickHouse database (OLAP / columnar analytics engine, Apache-2.0) on a dedicated VM on your private network — its OWN resource, NOT a relational database. Requires a recent plan_managed_datastore. Use it for analytics Inputs: idempotency_key, name, flavor_id, network_id, keypair_name, db_name |
create_controller | Creates a self-configuring controller VM on redu.cloud. Auto-discovers your network, Ubuntu image, and flavor. Generates and uploads an SSH keypair if you don't have one. The VM bootstraps itself — no SSH or VPN needed. After ~7 minutes, au Inputs: github_pat, repo, worker_count |
create_database | Provisions a managed PostgreSQL database on a dedicated VM on your private network. Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' so plan_deploy includes and wires the DB automatically. Inputs: idempotency_key, name, flavor_id, network_id, keypair_name, db_name |
create_instance | Creates a raw compute instance for custom OS/cloud-init workflows. For app/source deployments, prefer check_deploy_prerequisites -> plan_deploy -> deploy_app/deploy_compose; do not use create_instance as a shortcut around the deployment pla Inputs: idempotency_key, name, image_id, flavor_id, keypair_name, network_id |
create_media_space | Creates a private Redu media space: a small NFS VM backed by a persistent volume, intended for WordPress/WooCommerce wp-content/uploads in autoscaling clusters. Prefer letting deploy_app/deploy_compose create this by passing create_media_sp Inputs: idempotency_key, name, size_gb, flavor_id, network_id, keypair_name |
create_redis | Provisions a managed Redis instance on a dedicated VM on your private network. Requires a recent plan_managed_datastore. It is PRIVATE — reachable only from another instance on the same private network, via its internal/private IP on port 6 Inputs: idempotency_key, name, flavor_id, network_id, keypair_name, version |
create_relational_database | Provisions a managed MySQL (or MariaDB) database on a dedicated VM on your private network — the relational-database resource (use this instead of create_database when the app needs MySQL/MariaDB, e.g. WordPress, NextCloud, Matomo, many PHP Inputs: idempotency_key, name, engine, flavor_id, network_id, keypair_name |
create_snapshot | Creates a snapshot of a running instance. Inputs: instanceId, snapshotName |
create_volume | Creates a block storage volume. Inputs: name, size |
delete_backup | Deletes a backup by ID. Inputs: id |
delete_clickhouse | Deletes a managed ClickHouse database and its underlying VM. Pass the numeric id from list_clickhouse_databases. This cannot be undone. Inputs: id |
delete_cluster | Deletes an autoscaling cluster — tears down the WHOLE cluster: every autoscaled EXTRA member VM, the load balancer, the pool, the cluster security group, and the cluster's *.redu.cloud proxy host. Your SOURCE (hero) VM is NOT part of the st Inputs: stack_name, stack_id |
delete_database | Deletes a managed Postgres database and its underlying VM. Pass the numeric database id from list_databases. This cannot be undone. Inputs: id |
delete_deployment | Deletes a deployment and its underlying app VM. Pass the numeric id from list_deployments. IMPORTANT: if the deployment used database:'managed', the managed Postgres VM is NOT deleted (data safety) — this tool returns its id so you can dele Inputs: id |
delete_instance | Permanently deletes an instance. This cannot be undone. Inputs: id |
delete_keypair | Removes an SSH keypair from your account by name. Inputs: name |
delete_redis | Deletes a managed Redis instance and its underlying VM. Pass the numeric id from list_redis. This cannot be undone. Inputs: id |
delete_relational_database | Deletes a managed MySQL/MariaDB database and its underlying VM. Pass the numeric id from list_relational_databases. This cannot be undone. Inputs: id |
delete_snapshot | Deletes a snapshot by ID. Inputs: id |
delete_volume | Permanently deletes a block storage volume and the data on it. This cannot be undone. The volume must be 'available' (detached) — detach_volume it first, and note you cannot detach a running instance's boot disk. A volume left behind after Inputs: id |
deploy_app | Deploys an app to a VM and exposes it at a public https://<name>-<id>.redu.cloud URL. The container is built ON the VM. PREREQS — run check_deploy_prerequisites first for network_id + keypair_name, then plan_deploy for cost approval. Source |
deploy_compose | Deploys a MULTI-CONTAINER app — a repo that ships docker-compose.yml / compose.yaml — onto ONE VM via podman-compose, and exposes one or more services at redu.cloud URLs. Use this instead of deploy_app when the repo is a compose stack. Same |
deploy_overview | Orientation for deploying an app on redu.cloud: the end-to-end flow, the two source modes (git vs upload), how to handle a missing Dockerfile or a database, when (and when NOT) to split a deploy across multiple VMs, verifying a deploy funct |
deploy_vpn | Stands up a redu VPN gateway (WireGuard tunnelled over wstunnel on WSS/443) on your PRIVATE network, so you (or your team) can reach the private IPs of the VMs you deployed on redu, over a single https endpoint — no UDP, no extra ports. Thi Inputs: keypair_name, name, network_id, flavor_id, client_cidr, confirm |
detach_volume | Detaches a block volume from an instance, leaving the volume (and its data) intact and 'available' to attach elsewhere. Unmount it INSIDE the guest first (`umount /mnt/...`) or you risk a dirty filesystem. You cannot detach an instance's RO Inputs: volume_id, instance_id |
get_agent_status | Returns the current status of your controller VM. On a freshly set-up VM also returns the trigger token needed to authorize the fleet and to call trigger_agent_batch. Call this after setup_agent_fleet to confirm the VM is ready. Inputs: controller_url, log_token |
get_container_logs | THE APPLICATION'S OWN LOGS - what `docker logs`/`podman logs` would show for each container in a deployment. This is the tool for 'it deployed fine but it does not work': a 500, a crash loop, a failed DB connection, a missing env var all an Inputs: deployment_id, service, tail, since |
get_containers | WHAT IS ACTUALLY RUNNING on a deployment's VM: every container's name, image, state, health, restart count, exit code and published ports - including the ones that have CRASHED, which are the ones you need. Use this the moment a deployment Inputs: deployment_id |
get_deployment | Fetches ONE deployment by its numeric id (from list_deployments). Returns its current status, the public access_point URL, the underlying VM id, AND the build_log - IN FULL when status is 'build_failed' or 'error', which is when it is the d Inputs: id, redu_md |
get_domain_verification | Returns the DNS TXT record to add for custom domain ownership verification. Add the record to your DNS provider, then call verify_domain. Inputs: domain |
get_env_keys | WHICH ENVIRONMENT VARIABLES the deployment was actually given, BY NAME - the keys in the env files on the VM (/opt/app-src/.env and friends), never the values. Most of the time the real question is 'did DATABASE_URL get wired, or is the app Inputs: deployment_id |
get_instance_logs | The VM's SERIAL CONSOLE: kernel messages and early-boot/cloud-init output. ⛔ THIS IS NOT YOUR APPLICATION'S LOGS. For a deployed app - a crash loop, a 500, a failed DB connection - use get_container_logs, which returns what the containers a Inputs: instance_id |
get_resource_usage | HOW MUCH ROOM IS LEFT on a deployment's VM: total/used/available memory, swap, disk free, load average, CPU count, and OOM kills in the last 24h - plus per-container memory and CPU. Use it to answer 'is this flavor big enough', to size the Inputs: deployment_id |
get_ssh_command | Returns the SSH command to connect to an instance via the redu.cloud TCP proxy. ACCEPTS an instance id, a deployment's id / name / instance_id, OR a MANAGED DATASTORE's id / name / instance_id (Postgres, MySQL/MariaDB, ClickHouse, Redis) - Inputs: instance_id, keypair_name |
import_keypair, instance_action, integrate_overview, list_backups, list_clickhouse_databases, list_clusters, list_databases, list_deployments, list_dns_entries, list_domains, list_flavors, list_images, list_instances, list_keypairs, list_media_spaces, list_private_networks, list_redis, list_regions, list_relational_databases, list_security_groups, list_snapshots, list_volumes, plan_deploy, plan_instance, plan_managed_datastore, prepare_upload, restore_backup, scaffold_local, select_surface, set_cluster_domain, set_managed_backups, setup_agent_fleet, setup_agent_session, trigger_agent_batch, update_cluster, upgrade_to_cluster, upgrade_to_ha, verify_deployment, verify_domain, wait_for_deployment, whoami
Every block below points at https://mcp.redu.cloud/mcp. Pick your client and copy.
claude mcp add --transport http mcp https://mcp.redu.cloud/mcp
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.redu.cloud/mcp"]
}
}
}{
"mcpServers": {
"mcp": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}{
"servers": {
"mcp": {
"type": "http",
"url": "https://mcp.redu.cloud/mcp"
}
}
}{
"context_servers": {
"mcp": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"serverUrl": "https://mcp.redu.cloud/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}name: mcp
version: 0.0.1
schema: v1
mcpServers:
- name: mcp
type: streamable-http
url: https://mcp.redu.cloud/mcp{
"mcpServers": {
"mcp": {
"httpUrl": "https://mcp.redu.cloud/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"type": "http",
"url": "https://mcp.redu.cloud/mcp"
}
}
}{
"mcpServers": {
"mcp": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.redu.cloud%2Fmcp&type=streamable_http&id=mcp&name=mcp
It answered our last check on 17 October 2026 in 96 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by redu.cloud and served from mcp.redu.cloud, the vendor's own domain: https://mcp.redu.cloud/mcp.
81, as returned by the server's own tools/list on 9 September 2026: architecture_diagram, attach_volume, check_agent_prerequisites, check_deploy_prerequisites, create_api_key, create_backup, create_clickhouse, create_controller, and 73 more.
It answered our last check on 17 October 2026 in 96 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.redu.cloud/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: cloud.redu. Endpoint host: mcp.redu.cloud. ARD identifier: urn:air:cloud.redu:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.