Redis MCP

This is the Redis Cloud management server, and the distinction matters: it is a control plane connector, not a way to read or write keys inside a database. It wraps the Redis Cloud REST API so an agent can inspect and provision managed Redis infrastructure conversationally, while data access belongs to the separate Redis MCP server that talks to an instance directly. What it exposes maps to the Redis Cloud account model. An agent can read the account it is authenticated against and the payment methods on file, list Pro and Essential subscriptions along with the databases inside them, create a subscription with its cloud provider, region, and capability configuration, create databases within a subscription, and delete Essential subscriptions. Reference lookups fill in the rest: available modules and capabilities, the cloud provider regions on offer, and the Essential plan options to choose from. Because provisioning is asynchronous, write calls return a task identifier and a companion tool reports on that task until the resource is ready. It authenticates with Redis Cloud API keys, so whatever those credentials can do, the agent can do, including creating billable resources and deleting subscriptions. Scope the key deliberately and keep deletions behind human confirmation. The natural users are platform and backend engineers who want to spin up a cache or a vector database from inside an editor session, and teams auditing what already exists across a Redis Cloud account.