← redu.cloud
INDIVIDUAL MCP TOOL
list_relational_databases
Lists your managed MySQL/MariaDB databases (the relational-database resource).
Input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent endpoint
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.redu-cloud]
url = "https://mcp.redu.cloud/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"redu-cloud": {
"type": "http",
"url": "https://mcp.redu.cloud/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: redu-cloud
Remote MCP URL: https://mcp.redu.cloud/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"redu-cloud": {
"url": "https://mcp.redu.cloud/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"redu-cloud": {
"type": "http",
"url": "https://mcp.redu.cloud/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "redu-cloud",
"transport": "streamable-http",
"url": "https://mcp.redu.cloud/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
whoami— Verifies your redu.cloud credential with a REAL server round-trip and returns your identity + live quota.check_deploy_prerequisites— The deploy ENTRY GATE — run this first when a user wants to deploy.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.prepare_upload— Returns the LOCAL shell commands to package your working directory and upload it for an upload-mode deploy (no git, no PAT).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.plan_instance— Aggregates images/flavors/keypairs/networks/security groups into human-friendly choices.plan_managed_datastore— Plans a direct managed datastore create without provisioning anything.select_surface— For a repo with SEVERAL runnable parts, call this BEFORE plan_deploy.