What you can do with it
Share of each task's required capabilities it coversPrefer a ready-made agent?
An MCP server is a connector for your own assistant. These finished products do the job for you: query databases in plain language.Similar tools
Listed for the same task: query databases in plain languageReviews
No review yet. Used mcp? Be the first to help others choose.What it does
mcp is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
From the publisher's description, Electra Index matched it to one capability: sql querying. That makes it a candidate for tasks such as query databases in plain language or build data pipelines.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 10h ago (live check)Hosted endpoint
https://mcp.redu.cloud/mcpstreamable-http
In Claude Code: claude mcp add --transport http mcp-70 https://mcp.redu.cloud/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"mcp-70": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 10h agoONLINE mcp answered an MCP connection on 17 Nov 2026 and introduced itself as redu-cloud-mcp 2.0.0 (MCP protocol 2025-06-18).
119 tools offered to AI assistants
get_private_vps_pilot· Read your private VPS pilot approval and occupied website/database slots. This does not create a VM or change billing.create_private_vps· Approved pilot accounts only. Create one website VM (1 CPU, 2 GiB RAM, 10 GiB total disk) or one database VM (1 CPU, 1 GiB RAM, 2 GiB total disk). Both start with plain Ubuntu. Maximum one of each, including pending and stopped VMs. The paidelete_private_vps· 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-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 smallerget_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 genpublish_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 poget_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: reservcreate_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 ccreate_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 administratioget_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, envexec_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 d
Show 88 more
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 thepublish_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>.rget_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 afcreate_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 mupdate_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. Gadd_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 portsdelete_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 mset_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 orget_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 privatdeploy_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 functcreate_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-lilist_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 mintdelete_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 ointegrate_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-PRIVILEprepare_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 withscaffold_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-composplan_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 yoplan_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 deploymentsselect_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 RANKSplan_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 arelist_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_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_veriflist_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/upglist_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 6379list_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_spupgrade_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 VMupdate_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 rollinset_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 producdelete_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 stimport_keypair· Registers an existing SSH public key on your account. Use this to import your own public key so you can SSH into instances. The private key never leaves your machine.delete_keypair· Removes an SSH keypair from your account by name.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) -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 ainstance_action· Start, stop, reboot or resize an instance. action: START, STOP, REBOOT_SOFT, REBOOT_HARD, or RESIZE with flavorId (a flavor name or id). A resize restarts the machine on the new size and then waits for you: when list_instances shows it VERIcreate_instance· Creates a raw compute instance for custom OS/cloud-init workflows. A run's machines are empty VMs from send_signals (empty_vm: true), never from here (a run key cannot call create_instance). For app/source deployments, prefer check_deploy_pdelete_instance· Permanently deletes an instance. This cannot be undone.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.delete_database· Deletes a managed Postgres database and its underlying VM. Pass the numeric database id from list_databases. This cannot be undone.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 PHPdelete_relational_database· Deletes a managed MySQL/MariaDB database and its underlying VM. Pass the numeric id from list_relational_databases. This cannot be undone.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 analyticsdelete_clickhouse· Deletes a managed ClickHouse database and its underlying VM. Pass the numeric id from list_clickhouse_databases. This cannot be undone.upgrade_to_ha· Turns an EXISTING, running single-machine managed Postgres or ClickHouse into a THREE-machine highly available cluster, in place, keeping the data and the same username, password and database name. Use this when the user has a live databasecreate_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 6delete_redis· Deletes a managed Redis instance and its underlying VM. Pass the numeric id from list_redis. This cannot be undone.create_qdrant· Provisions a managed Qdrant vector database on a dedicated VM. Requires a recent plan_managed_datastore (engine 'qdrant'). Reachable from your private network at <private_ip>:6333 (REST) and :6334 (gRPC), and at a public https URL; every redelete_qdrant· Deletes a managed Qdrant and its underlying VM, with every collection in it. Pass the numeric id from list_qdrant. This cannot be undone.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. Sourcedeploy_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. Samedeploy_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. Thilist_deployments· Lists your app deployments. Each row carries status (provisioning/ready/build_failed/error), the current build phase while provisioning (installing/source/building/built/starting), the public access_point URL, port, repo, and build_log on fverify_deployment· Asks redu to re-probe a deployment's public URL and update its status from what it actually observes. USE THIS AFTER YOU HAVE FIXED A FAILED DEPLOY - a deployment that ended 'error' or 'build_failed' but is now serving becomes 'ready' againdelete_deployment· Deletes a deployment and its underlying app VM, with the data kept on that machine (its named volumes): the only way kept data is deleted, so ask the user first. Pass the numeric id from list_deployments. IMPORTANT: its managed datastores await_for_deployment· ⭐ CALL THIS INSTEAD OF POLLING. Waits up to 50 seconds per call (an MCP client cuts a call at about 60 s) for the deployment to reach a TERMINAL state (ready, build_failed, error or vm_missing) and returns, in ONE response, everything you wget_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 dget_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 deploymentget_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 anget_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 theget_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 apparchitecture_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 wcreate_snapshot· Creates a snapshot of a running instance.delete_snapshot· Deletes a snapshot by ID.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.restore_backup· Restores a backup into an existing volume (volumeId), an instance's volume (instanceId), or a new one (volumeName). Poll list_volumes for the restored volume. DISASTER RECOVERY (the original VM is gone, so its volume died with it): restoredelete_backup· Deletes a backup by ID.set_managed_backups· Turns nightly AUTOMATED (scheduled) backups ON or OFF for a MANAGED data service - the toggle that create_backup (a one-off volume snapshot) is NOT. Once enabled, redu's nightly job backs the service up on its own and prunes to the retentiocreate_volume· Creates a block storage volume.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 replacedetach_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
The first 100 are shown.
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.redu.cloud/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 0.1.1 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is mcp still online?
Free alerts · no account▲ 0Do you run mcp? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about mcp
How do I connect mcp?
Use the hosted endpoint https://mcp.redu.cloud/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does mcp offer?
When Electra Index connected on 17 Nov 2026, it listed 119 tools: get_private_vps_pilot, create_private_vps, delete_private_vps, exec_private_vps, get_private_vps_ssh, publish_private_vps, get_private_vps_action, get_free_resources and more. The full list is in "Live check" above.
Is mcp online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 10h ago.
What can I use mcp for?
Based on its description, it is most relevant to: query databases in plain language, build data pipelines.