# redis/mcp-redis-cloud [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/redis/mcp-redis-cloud  
**GitHub Stars:** 41  
**npm Downloads (last month):** 906795  
**Views:** 5  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/redis-mcp-redis-cloud

## Description
Manage your Redis Cloud resources effortlessly using natural language. Create databases, monitor subscriptions, and configure cloud deployments with simple commands.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp-redis-cloud": {
    "command": "npx",
    "args": ["-y","@modelcontextprotocol/inspector"],
    "env": {
      "API_KEY": "",
      "SECRET_KEY": ""
    }
  }
}
```

**Requires environment variables:** `API_KEY`, `SECRET_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What redis/mcp-redis-cloud MCP server does

redis/mcp-redis-cloud MCP server connects an MCP-compatible client to the Redis Cloud API. It gives an agent tools for inspecting account information, payment methods, subscriptions, database capabilities, cloud regions, plans, and account tasks. It also supports creating Pro and Essential subscriptions, deleting Essential subscriptions, and retrieving details for a specific Essential subscription.

The available operations cover both read and write workflows. An agent can use the server to review current Redis Cloud resources, compare available plans and regions, submit subscription changes, and check the progress of asynchronous work. The server does not provide a general Redis data-access interface; the documented scope is Redis Cloud account and deployment management.

## How it works

An MCP client invokes the exposed tools in response to a natural-language request. The server authenticates those API calls with a Redis Cloud API key and secret key supplied through environment variables. For example, a request to create a subscription can result in a task ID rather than an immediately completed deployment. The agent can then use the task tools to inspect status, progress, and subscription-change activity.

Some list operations are paginated. Retrieving a complete set of Essential subscriptions, plans, or other supported results may therefore require more than one tool call. The server includes a generated Redis Cloud API client in its source tree, with an entry point under the built `dist` directory.

## Setup and configuration

The repository is a Node project. Its documented development setup uses Node v22.14.0, npm 10.9.2, and nvm. Install the project dependencies with npm, then run the build script before starting the server. The resulting entry point is `dist/index.js`.

For Claude Desktop or Cursor, configure a local MCP server that runs Node with the `--experimental-fetch` option and points to the built entry point. Set these environment variables in the client configuration:

- `API_KEY`: Redis Cloud API key.
- `SECRET_KEY`: Redis Cloud API secret key.

Docker is also documented as an option. Build the image with the repository's Dockerfile and run it interactively with the same two environment variables. The container image name shown in the documentation is `mcp/redis-cloud`.

## Tools and capabilities

redis/mcp-redis-cloud MCP server documents tools for:

- Reading the current Redis Cloud account and configured payment methods.
- Listing Pro subscriptions and paginated Essential subscriptions.
- Inspecting an Essential subscription by ID.
- Creating Pro subscriptions with options for multi-cloud deployment, memory, persistence, modules, Active-Active deployment, and custom networking.
- Creating or deleting Essential subscriptions.
- Listing database modules, features, and performance options available to the account.
- Finding Pro regions across AWS and GCP, including networking and availability-zone information.
- Listing Essential plans across AWS, GCP, and Azure, including Redis Flex and fixed plans.
- Listing tasks and retrieving an individual task's deployment or change status.

## Limitations and notes

A valid Redis Cloud API key and secret key are required. The documented examples target Claude Desktop and Cursor, although the README describes the server as usable with any MCP client. Long-running changes must be monitored through returned task IDs, and paginated responses are not necessarily complete after one request. The provided material does not specify a license, Redis Cloud pricing details, or support for other MCP clients.

_Full upstream README: https://allmcps.com/mcp/redis-mcp-redis-cloud/readme_