Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
接入你的智能体
發布者自己的 URL。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
https://mcp.redu.cloud/mcp上方的 Claude 按鈕會開啟 Claude,並填好名稱和 URL。你仍需在那裡確認。
claude mcp add --transport http cloud.redu-mcp https://mcp.redu.cloud/mcpRun in a terminal.
{ "mcpServers": { "cloud.redu-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://mcp.redu.cloud/mcp" ] } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
尚未爬取 README。 未登記儲存庫。
Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.
{ "mcpServers": { "cloud.redu-mcp": { "url": "https://mcp.redu.cloud/mcp", "headers": {} } }}60 個工具
常見問題
| Permanently delete one of your pilot VMs and its boot disk, including all stored data. Requires explicit user authorization. Use the occupied operation id from get_private_vps_pilot, not a paid VM id. After deletion is verified its one-per-account slot becomes available for a new create_private_vps |
| exec_private_vps | Run a user-requested shell script as ubuntu on an active pilot VM (sudo is available). Both pilots start as plain Ubuntu: install only the database or app the user requested. Either size can run commands without the other pilot. The smaller database pilot can clone from GitHub and download packages |
| get_private_vps_ssh | Install the user's SSH PUBLIC key on either pilot and return its SSH connection instructions through the restricted relay. The smaller database pilot works on its own; no website pilot is needed. Application ports stay private. Reuse or generate an Ed25519 key locally; send only its public key, neve |
| publish_private_vps | Publish a user-requested HTTP application from either pilot, including the smaller pilot on its own, at a generated public HTTPS URL. First install and start the application, enable its production authentication and verify its local HTTP port. This publishes the app only; it does not assign a public |
| get_private_vps_action | Read the status, bounded output and exit code of your pilot command, or the SSH access instructions. An unknown result must be inspected before submitting a new request. Does not repeat commands. |
| get_free_resources | Read the included website and private PostgreSQL slots for your account. These are separate from pilot VMs and paid VMs. All three plans include at most one of each. Free without a verified card lasts seven days. Capacity is limited: reserved requests with free_capacity_wait are queued in eligible r |
| create_free_website | Create the included Ubuntu website VM. Its fixed size is 1 CPU, 2 GiB RAM and 10 GiB total disk. No hosting credit is consumed. It is separate from the pilot. If capacity is full, keep the queued operation and original request key; do not create a paid replacement. Wait for an active slot in get_fre |
| create_free_postgres | Create the included private PostgreSQL VM, with PostgreSQL installed automatically. Its fixed size is 1 CPU, 1 GiB RAM and 2 GiB total disk including Ubuntu. Create the included website VM first: all database access, including administration, goes through that website. No direct public SQL, SSH or H |
| get_free_resource_telemetry | Read bounded memory, root-disk, load, OOM counters, container states and systemd service states from your active included VM. Uses the restricted read-only collector; PostgreSQL is reached only through its website VM. No commands, logs, environment values or credentials are collected. Inspect before |
| exec_free_resource | Run an authorized shell script on an included free VM. Database commands are relayed through the included website VM. PostgreSQL is installed automatically; inspect before modifying it. Use get_free_resource_telemetry before builds and to diagnose resource pressure or failed services. Never print pa |
| get_free_website_ssh | Install the user's Ed25519 public key on the included website VM and return verified SSH instructions through the restricted relay. Send only the public key. Read get_free_resource_action until complete, use the returned host keys, test the connection and give the user the returned command. This doe |
| publish_free_website | Publish the included website's working HTTP application at its generated HTTPS hostname or one exact custom hostname the owner has verified with verify_domain. Point the custom hostname at the generated free-<operation ID without hyphens>.redu.cloud name using CNAME (or the same public edge address |
| get_free_resource_action | Read your saved command, SSH or website publication result. This never repeats an action. If its outcome is unknown, preserve the existing VM and request key for review; do not claim success or resubmit a command. |
| delete_free_resource | Permanently delete one included free VM and its boot disk after explicit user authorization. Use its occupied operation ID from get_free_resources. Deleting the website interrupts access to the private database. The slot is released only after verified deletion. Monthly website usage is retained; no |
| create_security_group | Creates a security group (a firewall for the machines you attach it to) and returns its id and the rules it starts with: every outbound connection allowed, nothing inbound. Add inbound rules with add_security_group_rule, then attach it to machines with set_instance_security_groups. Names are unique |
| update_security_group | Renames a security group or changes its description. Its rules and the machines it is attached to stay as they are. Names stay unique in your account. Get the id from list_security_groups. |
| delete_security_group | Permanently deletes a security group and all its rules. Ask the user first. Refused for the default group, and for a group any machine still uses: the refusal names those machines, and set_instance_security_groups takes it off them first. Get the id from list_security_groups. |
| add_security_group_rule | Adds one rule to a security group and returns it as the platform made it (with its id). Machines with the group get it at once. Adding a rule that already exists changes nothing and returns the existing one. Zero trust: open only the ports a service needs, from the narrowest source that works: anoth |
| delete_security_group_rule | Permanently removes one rule from a security group; machines with the group lose it at once. Ask the user first. When a machine gets a public URL, the platform opens that port to any address in every security group the machine has at that moment, and closes it when the URL is removed. A group attach |
| set_instance_security_groups | Sets the COMPLETE list of security groups on one of your machines: groups you list are added, groups you leave out are removed, and the result is read back from the machine. Ask the user first when it removes a group. Give groups by name or id (list_security_groups). Keep at least one. When a machin |
| get_billing_account | Read your plan, credit expiry, budget and free-resource allowance. Card, budget and plan changes require the account owner in the console. |
| whoami | Verifies your redu.cloud credential with a REAL server round-trip and returns your identity + live quota. A green result means the key actually works - not merely that one is configured. Use this first if anything is 401ing. |
| 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 private network (picks your default - every account has one), (3) |
| 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 functionally, and how to debug a failed build. Call this first wh |
| 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-lived credential that acts on the account and ANY usage of it |
| list_api_keys | Lists the account's API keys: id, name, scopes, when each was created and last used, and when it expires. Never the secret (redu keeps only a hash). Use it to find a key to delete with delete_api_key, or to check what keys exist before minting another. |
| delete_api_key | Deletes one of the account's API keys, by id or by name. Anything that uses the key stops working at once, so the first call deletes nothing: it shows the key (name, scopes, last used) for the user to approve; call again with confirm:true only after their yes. Use it to clean up a key you created fo |
| integrate_overview | Orientation for wiring a redu.cloud capability (backups, DNS, extra storage, a managed DB, ...) INTO an app already deployed on redu, e.g. 'add a backup feature to the Supabase I deployed on redu'. Explains the pattern: mint a LEAST-PRIVILEGE scoped API key (with the user's approval via create_api_k |
| prepare_upload | Returns the LOCAL shell commands to package your working directory and upload it for an upload-mode deploy (no git, no PAT). Run them in the user's terminal, capture `source_token` from the upload's JSON response, then call deploy_app with that source_token (omit repo). The upload authenticates AUTO |
| scaffold_local | OPTIONAL preflight: returns a podman-compose.yml + .env so the user can run the app (and a throwaway local Postgres) on THEIR machine before deploying to redu - to see it run / sanity-check the container. Requires local podman/podman-compose. It's a suggestion, not a gate - skip it and go straight t |
| plan_instance | Aggregates images/flavors/keypairs/networks/security groups into human-friendly choices. Does not create anything. Happy path: import_keypair → plan_instance → create_instance → get_ssh_command. Call this second (after import_keypair, if you have no keypairs). |
| plan_managed_datastore | Plans a direct managed datastore create without provisioning anything. Use this before create_database, create_relational_database, create_redis, create_clickhouse or create_qdrant (engine 'qdrant', the vector database). For app deployments you need none of these: datastores are managed by default, |
| select_surface | For a repo with SEVERAL runnable parts, call this BEFORE plan_deploy. You enumerate the candidate surfaces (find every Dockerfile/Containerfile, OPEN each, classify by its EXPOSE + CMD - never by directory name) and pass them in; redu RANKS them with fixed rules (a standalone browser desktop/noVNC > |
| plan_deploy | Turns YOUR repo classification (you scan the repo and pass what you found) into a complete, approvable deploy plan WITHOUT creating anything. ⚡ REDU NEEDS THREE FILES IF THEY EXIST - redu.md, the compose file, the Dockerfile - and there are two ways to give them. ⭐ BEST, for an upload-mode deploy: r |
| list_instances | Lists your compute instances. |
| list_flavors | Lists available instance sizes. |
| list_images | Lists available OS images. |
| list_keypairs | Lists your SSH keypairs. If empty, call import_keypair first before creating instances. |
| list_security_groups | Lists your security groups, each with its rules (id, direction, protocol, ports, and the other side: an address range or another group). Use the ids with add_security_group_rule, delete_security_group_rule, update_security_group and delete_security_group; set_instance_security_groups attaches groups |
| list_private_networks | Lists your private networks. |
| list_volumes | Lists your block storage volumes. |
| list_snapshots | Lists your instance snapshots. |
| list_backups | Lists your volume backups. |
| list_clusters | Lists your autoscaling clusters. |
| list_dns_entries | Lists the public names (DNS entries) on this account: each entry's id, the names it serves (domain_names) and the address it forwards to. delete_dns_entry removes one by its id. |
| list_domains | Lists the custom domains on this account with their status: verified (it can be bound with dname on deploy_app/deploy_compose, dns_entries on create_instance, or set_cluster_domain) or pending (its TXT check has not passed: get_domain_verification gives the record, verify_domain checks it). The publ |
| list_regions | Lists available regions. |
| list_databases | Lists your managed PostgreSQL databases. Once a row's status is 'ready', it carries the private-network connection details (private_ip, port 5432, db_name, db_user). |
| list_relational_databases | Lists your managed MySQL/MariaDB databases (the relational-database resource). Each row carries its engine ('mysql'|'mariadb'); once status is 'ready' it has the private-network connection details (private_ip, port 3306, db_name, db_user). |
| list_media_spaces | Lists Redu media spaces: private NFS media VMs backed by persistent volumes. For WordPress/WooCommerce clusters, reuse one on the app's private network for wp-content/uploads, or pass create_media_space:true to deploy_app/deploy_compose/upgrade_to_cluster so Redu creates one. |
| list_clickhouse_databases | Lists your managed ClickHouse databases (OLAP / analytics - its own resource, not a relational DB). Once a row's status is 'ready' it carries the private-network connection details (private_ip, ClickHouse HTTP port 8123, db_name, db_user). |
| list_redis | Lists your managed Redis instances. Once a row's status is 'ready' it carries the private-network connection details (private_ip, port 6379) - connect from another instance on the same private network with redis-cli -h <private_ip> -p 6379 -a <password>. |
| list_qdrant | Lists your managed Qdrant vector databases (create_qdrant, or started for a deploy). Once a row's status is 'ready' it carries private_ip (REST port 6333, gRPC 6334); the API key is never listed. |
| 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_space:true after plan_deploy approval; use this tool when manu |
| upgrade_to_cluster | THE WAY TO MAKE AN EXISTING APP HIGHLY AVAILABLE. If the user asks for high availability, redundancy, no single point of failure, surviving a host or VM failure, or 'stay up if a machine dies', this is the tool: point it at their running VM and pass high_availability:true. It needs no rebuild and no |
| update_cluster | Updates a running autoscaling cluster to a new app version IN PLACE, with NO URL change: snapshots the 'hero' VM (the source/master VM you SSH into and change - it is also the always-on baseline member that serves traffic), then redu rolling-updates the autoscaled extra members to that snapshot ONE |
| set_cluster_domain | Changes the PUBLIC HOSTNAME a cluster serves on, so the user can put THEIR OWN production domain (shop.acme.com, app.theircompany.com) in front of it instead of the auto-generated redu.cloud URL. That is what this tool is for: a real product on a real brand. The cluster itself is untouched - same me |
| 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 stack and is NOT deleted - it was the always-on baseline membe |
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 http 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Redu 透過 HTTP 存取。
上次檢查時間:2026-11-17。 Agent-native cloud, EU-hosted. Provision VMs, networks & databases on redu.cloud via MCP.