Redis Cloud API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Redis Cloud API key | |
| SECRET_KEY | Yes | Redis Cloud API secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-current-accountB | Get the current Cloud Redis account |
| get-current-payment-methodsB | Get the current payment methods for the current Cloud Redis account |
| 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. |
| get-pro-plans-regionsB | Lookup list of regions for cloud provider. These regions include the providers too. |
| 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. |
| get-pro-subscriptionsB | Get the pro subscriptions for the current Cloud Redis account |
| get-pro-subscriptionC | Get pro subscription by ID. The payload must match the input schema. |
| 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. |
| get-essential-subscription-by-idB | Get an essential subscription by ID for the current Cloud Redis account |
| create-essential-subscriptionB | Create a new essential subscription. Returns a TASK ID that can be used to track the status of the subscription creation |
| delete-essential-subscriptionC | Delete an essential subscription by ID |
| 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. |
| get-tasksB | Get the current tasks for the current Cloud Redis account |
| get-task-by-idB | Get a task by ID for the current Cloud Redis account |
| get-pro-databasesC | Get the pro databases for the provided subscription Id |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
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.
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.
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.
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.