MCP Redis Cloud logo

MCP Redis Cloud

by redis

Manage Redis Cloud accounts, subscriptions, databases, plans, regions, and tasks through MCP tools.

Install MCP Redis Cloud

Run the project’s own setup commands, in order.

Setup steps from the project

redis/mcp-redis-cloud installs with its own commands rather than a config we can generate, so these are copied as-is. Run them in order in a terminal. Source: github.com

  1. 1. Run
    npm run build
    
  2. 2. Install
    npm install
    
  3. 3. Install
    docker build -t mcp/redis-cloud .
    
  4. 4. Start the server
    docker run -i --rm \
      -e API_KEY=<your_redis_cloud_api_key> \
      -e SECRET_KEY=<your_redis_cloud_api_secret_key> \
      mcp/redis-cloud
    

Overview

redis/mcp-redis-cloud MCP server exposes Redis Cloud API operations to MCP clients such as Claude Desktop and Cursor. It uses Redis Cloud API credentials to let agents inspect accounts, subscriptions, plans, regions, modules, and task status, as well as create or delete supported subscriptions. Long-running operations return task IDs that can be queried for progress, while paginated endpoints may require multiple calls. Reach for it when an agent needs to administer Redis Cloud resources or answer questions about available deployment options.

Use cases

  • Inspect Redis Cloud account and payment details
  • Create Redis Cloud Pro or Essential subscriptions
  • Compare cloud regions and available subscription plans
  • Monitor deployment and subscription-change tasks

Key features

  • Account and payment method lookup
  • Pro and Essential subscription management
  • Cloud region and plan discovery
  • Database module and capability lookup
  • Task status monitoring
  • Pagination support for list operations

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

9/10 checks healthy over the last 95d

Supply-chain signal

2 high-severity advisories on record for this package. Most advisories affect transitive dependencies and may not be exploitable in this server's actual usage — this is a directional signal, not a security audit.

Critical 1High 1Medium 0Low 0

Scanned 8/27/2026 via OSV.dev

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars43Stargazers on the source repository.
Last commit1y agoMost recent push to the default branch.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Redis Cloud works

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. Long-running changes must be monitored through returned task IDs, and paginated responses are not necessarily complete after one request.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Redis Cloud

Clone the repository, install its npm dependencies, and run `npm run build`. Configure the built `dist/index.js` entry point in an MCP client with `API_KEY` and `SECRET_KEY`.

Yes.

Yes. The README provides Cursor MCP configuration steps using the same built Node entry point and credentials.

It requires a Redis Cloud API key and secret key, provided as `API_KEY` and `SECRET_KEY`.

Yes. Long-running operations return task IDs, and the documented task tools can list tasks or retrieve details for a specific task.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Redis Cloud AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/redis-mcp-redis-cloud?style=directory)](https://allmcps.com/mcp/redis-mcp-redis-cloud)
HTML Embed
<a href="https://allmcps.com/mcp/redis-mcp-redis-cloud"><img src="https://allmcps.com/api/badge/redis-mcp-redis-cloud?style=directory" alt="MCP Redis Cloud on AllMCPs" /></a>