create-pro-subscription, create-essential-subscription, create-pro-database and create-essential-database all return a task ID that you then poll with get-task-by-id, so provisioning is inherently two-step. The tools state their own prerequisites in order: verify a payment method, validate modules against get-database-modules, validate regions against get-pro-plans-regions. Deletion is available on the essential tier through delete-essential-subscription, and create-essential-database warns that a free database needs get-essential-subscriptions checked first.
A control-plane server for a Redis Cloud account, covering subscriptions, databases and the asynchronous tasks that create them.
- Account state: the current account, its payment methods, the database modules it supports, and the regions available per cloud provider
- Pro subscriptions listed, fetched by subscriptionId, and created — creation returns a task ID rather than a finished subscription
- Essential subscriptions listed with page and size paging, fetched by ID, created, and deleted, alongside the essentials plans for a chosen provider
- Databases inside a subscription: pro and essential lists with limit and offset, and creation on both tiers with the full property set (persistence, eviction policy, TLS, replication, sharding)
- Task tracking through get-tasks and get-task-by-id, which is how every create call is followed to completion
- A dryRun flag on the pro subscription and pro database creates
A Redis Cloud account with API credentials, supplied as API_KEY and SECRET_KEY.
One command plus a key — npx -y mcp-redis-cloud, then supply credentials