Skip to main content
Glama
Redis Cloud API MCP Server

Redis Cloud API MCP Server

Official
by redis

Redis Cloud API MCP Server

Model Context Protocol (MCP) is a standardized protocol for managing context between large language models (LLMs) and external systems. This repository provides an MCP Server for Redis Cloud's API, allowing you to manage your Redis Cloud resources using natural language.

This lets you use Claude Desktop, or any MCP Client, to use natural language to accomplish things on your Redis Cloud account, e.g.:

  • "Create a new Redis database in AWS"

  • "What are my current subscriptions?"

  • "Help me choose the right Redis database for my e-commerce application"

Features

Account Management

  • get_current_account: Get details about your current Redis Cloud account

  • get_current_payment_methods: List all payment methods configured for your account

Subscription Management

Pro Subscriptions

  • get_pro_subscriptions: List all Pro subscriptions in your account

  • create_pro_subscription: Create a new Pro subscription with advanced configuration options

    • Supports multi-cloud deployment

    • Configure memory, persistence, and modules

    • Set up Active-Active deployments

    • Custom networking configuration

Essential Subscriptions

  • get_essential_subscriptions: List all Essential subscriptions (paginated)

  • get_essential_subscription_by_id: Get detailed information about a specific Essential subscription

  • create_essential_subscription: Create a new Essential subscription

  • delete_essential_subscription: Delete an Essential subscription

Database Capabilities

  • get_database_modules: List all available database modules (capabilities) supported in your account

    • Redis modules

    • Database features

    • Performance options

Cloud Provider Management

  • get_pro_plans_regions: Get available regions across cloud providers

    • AWS regions

    • GCP regions

    • Networking options

    • Availability zones

Plans and Pricing

  • get_essentials_plans: List available Essential subscription plans (paginated)

    • Supports AWS, GCP, and Azure

    • Redis Flex options

    • Fixed plans

Task Management

  • get_tasks: List all current tasks in your account

  • get_task_by_id: Get detailed information about a specific task

    • Track deployment status

    • Monitor subscription changes

    • View task progress

Related MCP server: Redis MCP Server

Usage

Prerequisites

  • Valid Redis Cloud API credentials (API Key and Secret Key)

  • Task IDs are returned for long-running operations and can be monitored

  • Paginated responses require multiple calls to retrieve all data

Claude Desktop

To run the MCP server with Claude Desktop, follow these steps:

  1. Build the package:

    npm run build
  2. Add the server to Claude Desktop:

    • Open Claude Desktop settings

    • Navigate to the Developer tab (make sure you have enabled Developer Mode)

    • Click on "Edit config"

    • Open the claude_desktop_config.json file in your text editor and add the following configuration:

    {
      "mcpServers": {
        "mcp-redis-cloud": {
          "command": "node",
          "args": ["--experimental-fetch", "<absolute_path_to_project_root>/dist/index.js"],
          "env": {
            "API_KEY": "<redis_cloud_api_key>",
            "SECRET_KEY": "<redis_cloud_api_secret_key>"
          }
        }
      }
    }
  3. Close Claude Desktop and restart it. The server should now be available in the MCP Servers section.

Cursor IDE

To run the MCP server with Cursor IDE, follow these steps:

  1. Build the package:

    npm run build
  2. Add the server to Cursor:

    • Open Cursor Settings

    • Navigate to the MCP tab

    • Click on "Add new global MCP Server"

    • Update the automatically opened mcp.json file with the following configuration:

    {
      "mcpServers": {
        "mcp-redis-cloud": {
          "command": "node",
          "args": ["--experimental-fetch", "<absolute_path_to_project_root>/dist/index.js"],
          "env": {
            "API_KEY": "<redis_cloud_api_key>",
            "SECRET_KEY": "<redis_cloud_api_secret_key>"
          }
        }
      }
    }
  3. Restart Cursor. The server should now be available in the MCP Servers section.

Development

Prerequisites

  1. nvm (Node Version Manager)

  2. Node v22.14.0

  3. npm 10.9.2

Getting Started

  1. Install dependencies:

    nvm use v22.14.0
    npm install
  2. Build the project:

    npm run build
  3. Test it by using the MCP Inspector:

    npx @modelcontextprotocol/inspector node dist/index.js --api-key=<api_key> --secret-key=<secret_key>

Project Structure

src/
├── index.ts              # Entry point
├── clients/              # API Clients for external services
│   └── generated         # Generated Redis Cloud API client
└── tools/                # Tool implementations
    └── accounts/         # Account tools
    └── subscriptions/    # Subscription tools
    └── tasks/            # Task tools

Note: If you make changes to your code, remember to rebuild and restart Claude Desktop / Cursor:

npm run build

Docker Usage

Building the Docker Image

To build the Docker image for the MCP server, run the following command:

docker build -t mcp/redis-cloud .

Running the Docker Container

To run the container, use the following command:

docker run -i --rm \
  -e API_KEY=<your_redis_cloud_api_key> \
  -e SECRET_KEY=<your_redis_cloud_api_secret_key> \
  mcp/redis-cloud

Docker Integration with Claude Desktop

To integrate the Dockerized MCP server with Claude Desktop, follow these steps:

  1. Build the Docker image (if you haven't already):

    docker build -t mcp/redis-cloud .
  2. Add the server to Claude Desktop:

    • Open Claude Desktop settings

    • Navigate to the Developer tab (ensure Developer Mode is enabled)

    • Click on "Edit config"

    • Open the claude_desktop_config.json file in your text editor

    • Add the following configuration:

    {
      "mcpServers": {
        "redis-cloud": {
          "command": "docker",
          "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "API_KEY=<your_redis_cloud_api_key>",
            "-e",
            "SECRET_KEY=<your_redis_cloud_api_secret_key>",
            "mcp/redis-cloud"
          ]
        }
      }
    }
  3. Replace the placeholder values with your actual API credentials.

  4. Save the configuration file and restart Claude Desktop.

Notes

  • Ensure that the required environment variables (API_KEY, SECRET_KEY) are set correctly.

Available Tools

16 tools
create-essential-subscriptionB

Create a new essential subscription. Returns a TASK ID that can be used to track the status of the subscription creation

Inputs: name (required), planId (required), paymentMethod, paymentMethodId.

create-pro-databaseA

Create a new database inside the specified subscription ID. Returns a TASK ID that can be used to track the status of the database creationPrerequisites: 1) For database modules, validate against get-database-modules list. 2) Validate regions using get-pro-plans-regions. The payload must match the input schema.

Inputs: name (required), subscriptionId (required), averageItemSizeInBytes, dataEvictionPolicy, +17 more.

create-pro-subscriptionA

Create a new pro subscription. Returns a TASK ID that can be used to track the status of the subscription creation. Prerequisites: 1) Verify payment method by checking get-current-payment-methods. 2) For database modules, validate against get-database-modules list. 3) Validate regions using get-pro-plans-regions. The payload must match the input schema.

Inputs: cloudProviders (required), databases (required), deploymentType, dryRun, +5 more.

delete-essential-subscriptionC

Delete an essential subscription by ID

Inputs: subscriptionId (required).

get-current-accountB

Get the current Cloud Redis account

Inputs: no named parameters.

get-current-payment-methodsB

Get the current payment methods for the current Cloud Redis account

Inputs: no named parameters.

get-database-modulesB

Lookup list of database modules supported in current account (support may differ based on subscription and database settings). These modules are also called capabilities.

Inputs: no named parameters.

get-essentials-plansB

Get the available plans for essential subscriptions. Always ask for which provider the plans are want to be retrieved. A paginated response is returned, and to get all the plans, the page and size parameters must be used until all the plans are retrieved.

Inputs: provider (required), page, redisFlex, size.

get-essential-subscription-by-idB

Get an essential subscription by ID for the current Cloud Redis account

Inputs: subscriptionId (required).

get-essential-subscriptionsA

Get the essential subscriptions for the current Cloud Redis account. A paginated response is returned, and to get all the essential subscriptions, the page and size parameters must be used until all the essential subscriptions are retrieved.

Inputs: page, size.

get-pro-databasesC

Get the pro databases for the provided subscription Id

Inputs: subscriptionId (required), limit, offset.

get-pro-plans-regionsB

Lookup list of regions for cloud provider. These regions include the providers too.

Inputs: no named parameters.

get-pro-subscriptionC

Get pro subscription by ID. The payload must match the input schema.

Inputs: subscriptionId (required).

get-pro-subscriptionsB

Get the pro subscriptions for the current Cloud Redis account

Inputs: no named parameters.

get-task-by-idB

Get a task by ID for the current Cloud Redis account

Inputs: taskId (required).

get-tasksB

Get the current tasks for the current Cloud Redis account

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources (subscriptions, databases, tasks, etc.), but there's some potential confusion between get-essential-subscription-by-id and get-essential-subscriptions, and between get-pro-subscription and get-pro-subscriptions, as the singular/plural versions could be misselected for the wrong granularity. Overall, the resource-action combinations are mostly clear.

    Naming Consistency5/5

    Tool names follow a highly consistent verb-noun pattern with hyphens (e.g., create-essential-subscription, get-pro-databases). All tools use lowercase with hyphens, and verbs like 'create', 'get', and 'delete' are applied consistently across resources, making the naming predictable and readable.

    Tool Count4/5

    With 16 tools, the count is slightly high but reasonable for managing Redis Cloud subscriptions, databases, and related tasks. It covers essential and pro tiers comprehensively, though it might feel a bit heavy for a single domain. The tools are well-scoped without obvious bloat.

    Completeness4/5

    The toolset provides good coverage for managing Redis Cloud resources, including CRUD operations for subscriptions and databases, plus supporting tools for tasks, payment methods, and plans. Minor gaps exist, such as no update or delete tools for pro databases or payment methods, but agents can likely work around these with the available creation and retrieval tools.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      B
      maintenance
      The official Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis.
      53
      3,039 PyPI
      642
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server for the Spot.io API that enables management of AWS and Azure Ocean clusters across multiple accounts. It provides tools for cluster inventory, node management, cost analysis, and scaling operations through natural language.
      39
      1
      MIT