Redis Cloud API Orchestration MCP Endpoint

The Model Context Protocol (MCP) establishes a standardized mechanism for interfacing Large Language Models (LLMs) with external operational systems. This repository furnishes an MCP Server specifically engineered for the Redis Cloud API, empowering users to govern their cloud resources using conversational language.

This integration allows clients like Claude Desktop, or any compliant MCP Client, to execute administrative tasks against your Redis Cloud tenancy through plain English, such as:

• "Provision a fresh Redis data store within the AWS environment"
• "Enumerate my present service agreements?"
• "Advise on the optimal Redis instance profile for handling e-commerce transaction volumes"

Core Capabilities

Account Administration

• get_current_account: Retrieve comprehensive details pertaining to the active Redis Cloud account profile.
• get_current_payment_methods: List all registered financial instruments linked to the organization's account.

Service Tier Oversight

Professional Tiers

• get_pro_subscriptions: Fetch a roster of all Professional service contracts under management.
• create_pro_subscription: Initiate a new Professional service contract incorporating granular configuration parameters:
• Support for heterogenous cloud deployments (multi-cloud).
• Parameters for data capacity, durability settings, and feature modules.
• Configuration for Active-Active distributed architectures.
• Customization of virtual network topology.

Essential Tiers

• get_essential_subscriptions: Retrieve a paginated inventory of Essential service contracts.
• get_essential_subscription_by_id: Obtain granular metadata for a designated Essential service contract.
• create_essential_subscription: Initiate the establishment of a new Essential service contract.
• delete_essential_subscription: Terminate an existing Essential service contract.

Data Store Feature Inventory

• get_database_modules: List all available Redis extensions (capabilities) provisionable within the account scope:
• Official Redis module extensions.
• Core database feature sets.
• Performance enhancement options.

Cloud Provider Mapping

• get_pro_plans_regions: Determine the geographically available deployment zones across supported cloud vendors:
• AWS geographical points of presence.
• GCP geographical points of presence.
• Associated network routing configurations.
• Availability zone specifics.

Plan Structures and Costing

• get_essentials_plans: Present the catalogue of available Essential service plans (requires pagination for full list):
• Coverage for AWS, GCP, and Microsoft Azure platforms.
• Options pertaining to Redis Flex structures.
• Predefined, fixed-configuration plans.

Operational Task Tracking

• get_tasks: List all in-flight and historical operational activities recorded for the account.
• get_task_by_id: Retrieve the status report for a specific operational activity:
• Monitoring deployment progression.
• Tracking service tier modifications.
• Viewing overall task completion progress metrics.

Deployment and Execution

Prerequisites for Operation

• Valid API authentication credentials for Redis Cloud (API Token and Secret Token).
• Long-running operations yield Task IDs necessary for subsequent status polling.
• Comprehensive data retrieval may necessitate multiple sequential requests due to response pagination.

Utilizing with Claude Desktop

To deploy and register the MCP server instance within Claude Desktop, execute the subsequent steps:

1. Compile the application assets: bash npm run build

2. Integrate the server endpoint configuration into Claude Desktop:

   • Access Claude Desktop application settings.
   • Navigate to the 'Developer' interface (ensure Developer Mode is active).
   • Select the 'Edit config' option.
   • Modify the claude_desktop_config.json file, incorporating the following structure:

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

1. Terminate and subsequently relaunch the Claude Desktop application for the new server to become active in the MCP Servers registry.

Utilizing with Cursor IDE

To configure the MCP server integration within the Cursor IDE environment, follow this procedure:

1. Compile the application assets: bash npm run build

2. Register the server endpoint within Cursor:

   • Open Cursor Settings interface.
   • Navigate to the dedicated MCP configuration tab.
   • Choose the option to 'Add new global MCP Server'.
   • Overwrite the default content of the generated mcp.json file with this payload:

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

1. Restart Cursor. The newly configured endpoint will appear in the MCP Servers listing.

Development Workflow

Foundational Requirements

1. Node Version Manager (nvm) utility.
2. Specific Node runtime version: v22.14.0.
3. Specific npm package manager version: 10.9.2.

Initial Setup Steps

1. Activate the required Node version: bash nvm use v22.14.0 npm install

2. Generate production build artifacts: bash npm run build

3. Verify functionality using the MCP Inspector utility: bash npx @modelcontextprotocol/inspector node dist/index.js --api-key= --secret-key=

Codebase Organization

src/ ├── index.ts # Primary entry point script ├── clients/ # Modules for external service communication │ └── generated # Auto-generated Redis Cloud API interface files └── tools/ # Implementation logic for exposed MCP functions └── accounts/ # Logic related to account endpoints └── subscriptions/ # Logic pertaining to service tier management └── tasks/ # Logic for tracking asynchronous operations

Crucial Reminder: Any modifications to source code necessitate a rebuild before restarting Claude Desktop or Cursor: bash npm run build

Containerization (Docker)

Building the Docker Image

Execute the following command to construct the server image:

bash docker build -t mcp/redis-cloud-orchestrator .

Running the Containerized Instance

Launch the service using environment variables for credentials:

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

Docker Integration with Claude Desktop

To connect the containerized server instance to Claude Desktop, perform these setup actions:

1. Ensure the Docker image is built (refer to the previous step). bash docker build -t mcp/redis-cloud-orchestrator .

2. Update the Claude Desktop configuration file (claude_desktop_config.json):

3. Open Claude Desktop settings -> Developer tab (Developer Mode required).
4. Select 'Edit config'.
5. Inject the following JSON structure:

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

1. Substitute the bracketed placeholders with your actual access credentials.

2. Save the configuration and perform a restart of Claude Desktop to activate the Dockerized endpoint.

Operational Notes

• Verification is mandatory to confirm that the necessary runtime environment variables (API_KEY, SECRET_KEY) are populated with valid credentials.