Redis Cloud Management Protocol (MCP) Gateway

This implementation provides a Model Context Protocol (MCP) Gateway specifically engineered to interface with the Redis Cloud API ecosystem. MCP establishes a standardized communication layer between sophisticated Language Models (LLMs) and external operational systems. This server component enables users to leverage natural language capabilities through clients like Claude Desktop or any compliant MCP interface to automate complex Redis Cloud account operations.

Examples of attainable natural language actions:

• "Provision a fresh Redis data store within the Azure cloud environment."
• "Enumerate my active service subscriptions and associated billing details."
• "Recommend an optimal Redis tier configuration for handling high-volume transactional data in e-commerce workloads."

Core Functional Modules

Identity and Account Services

• get_current_account: Retrieve detailed metadata pertaining to the currently authenticated Redis Cloud account.
• get_current_payment_methods: Catalog all registered payment instruments linked to the account.

Entitlement and Plan Management

Premium Service Tiers

• get_pro_subscriptions: Obtain a listing of all provisioned Premium service entitlements.
• create_pro_subscription: Initiate the creation of a new Premium entitlement featuring advanced customization parameters:
• Support for heterogeneous, multi-cloud deployment topologies.
• Granular control over memory allocation, data persistence policies, and extension modules.
• Setup and configuration of Active-Active redundancy paradigms.
• Specification of custom virtual private cloud networking parameters.

Standard Service Tiers

• get_essential_subscriptions: Fetch a paginated list of all Essential service entitlements.
• get_essential_subscription_by_id: Secure detailed specifications for a singular Essential entitlement via its identifier.
• create_essential_subscription: Provision a new Standard tier service instance.
• delete_essential_subscription: Terminate and decommission an existing Essential service instance.

Feature and Capability Discovery

• get_database_modules: List all foundational database modules (capabilities) accessible within the current account scope:
• Official Redis extension modules.
• Core database operational features.
• Supported performance optimization settings.

Geographical and Infrastructure Mapping

• get_pro_plans_regions: Ascertain the catalogue of available deployment regions across supported hyperscalers:
• Amazon Web Services (AWS) regions.
• Google Cloud Platform (GCP) regions.
• Supported networking adjacency options.
• Availability Zone groupings.

Tiers and Costing Structure

• get_essentials_plans: Display the catalogue of available Standard subscription plans (supports pagination):
• Coverage for AWS, GCP, and Microsoft Azure platforms.
• Information regarding 'Redis Flex' pricing models.
• Details on fixed-term subscription packages.

Asynchronous Operation Tracking

• get_tasks: Present a comprehensive ledger of all pending or completed operations within the tenant environment.
• get_task_by_id: Retrieve granular status updates for a specific asynchronous task:
• Tracking the deployment realization pipeline status.
• Monitoring progress of subscription modifications.
• Viewing overall task execution progression metrics.

Operational Deployment Guide

Prerequisites

• Possession of valid Redis Cloud API authentication materials (API Key and Secret Key).
• Understanding that substantial provisioning operations yield Task IDs for subsequent status polling.
• Recognition that retrieval of complete datasets often necessitates iterating through paginated API responses.

Integration with Claude Desktop

To deploy and initialize the MCP gateway agent within the Claude Desktop environment:

1. Compile the project artifacts: bash npm run build

2. Configure the server connection within Claude Desktop:

   • Access Claude Desktop configuration settings.
   • Navigate to the 'Developer' panel (ensure 'Developer Mode' is toggled on).
   • Select 'Edit config' to access the configuration manifest.
   • Append the subsequent configuration structure to the claude_desktop_config.json file, substituting placeholder values:

{ "mcpServers": { "mcp-redis-cloud": { "command": "node", "args": ["--experimental-fetch", "/dist/index.js"], "env": { "API_KEY": "", "SECRET_KEY": "" } } } }

1. Terminate Claude Desktop and relaunch the application to register the new MCP resource.

Integration with Cursor IDE

Steps to establish the MCP gateway connectivity within the Cursor IDE environment:

1. Build the distributable files: bash npm run build

2. Register the server component within Cursor:

   • Open Cursor IDE preferences/settings.
   • Navigate to the dedicated MCP configuration section.
   • Choose the option to 'Add new global MCP Server'.
   • Modify the auto-generated mcp.json file to incorporate the following directive block:

{ "mcpServers": { "mcp-redis-cloud": { "command": "node", "args": ["--experimental-fetch", "/dist/index.js"], "env": { "API_KEY": "", "SECRET_KEY": "" } } } }

1. Restart Cursor to finalize the server initialization.

Development Cycle

Local Environment Requirements

1. Node Version Manager (nvm) must be installed.
2. Target Node.js Runtime: Version 22.14.0.
3. Target npm Utility: Version 10.9.2.

Initialization Procedure

1. Secure dependencies installation: bash nvm use v22.14.0 npm install

2. Compile the source code for execution: bash npm run build

3. Validation via the MCP Inspector tool: bash npx @modelcontextprotocol/inspector node dist/index.js --api-key= --secret-key=

Source Code Organization

src/ ├── index.ts # Primary application bootstrap file ├── clients/ # Module housing external API integration logic │ └── generated # Artifacts generated from the Redis Cloud API schema definitions └── tools/ # Implementation logic for each exposed MCP tool └── accounts/ # Tools related to account identity management └── subscriptions/ # Tools managing service entitlements └── tasks/ # Tools for monitoring asynchronous workflows

Crucial Reminder: Any modification to the source code necessitates a rebuild and subsequent restart of the integrating client (Claude Desktop / Cursor): bash npm run build

Containerized Operations (Docker)

Image Construction

Execute the following command to build the distributable Docker image:

bash docker build -t mcp/redis-cloud .

Container Execution

To launch the service within a container instance:

bash docker run -i --rm \ -e API_KEY= \ -e SECRET_KEY= \ mcp/redis-cloud

Docker Integration with Claude Desktop

To integrate the containerized gateway with Claude Desktop:

1. Ensure the Docker image is built (if not already completed). bash docker build -t mcp/redis-cloud .

2. Update the Claude Desktop server configuration:

3. Open Claude Desktop settings and navigate to the Developer section (Developer Mode required).
4. Select 'Edit config' and modify the claude_desktop_config.json file.
5. Embed the following Docker execution configuration:

{ "mcpServers": { "redis-cloud": { "command": "docker", "args": [ "run", "-i", "--rm", "-e", "API_KEY=", "-e", "SECRET_KEY=", "mcp/redis-cloud" ] } } }

1. Substitute the API credential placeholders with your active credentials.

2. Persist the changes and relaunch Claude Desktop to establish the connection.

Operational Notes

• Validation is required to confirm that the requisite environment parameters (API_KEY, SECRET_KEY) are correctly populated and accessible to the process.