Connections & Capabilities
Connects To
Capabilities
Quickstart
Install
npx @modelcontextprotocol/inspectorConfig
{
"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>"
}
}
}
}Exposed MCP Tools (13)
get_current_accountRetrieves details about the current Redis Cloud account.
Read-only operation, no side effects.
get_current_payment_methodsLists all payment methods configured for the account.
Read-only operation, no side effects.
get_pro_subscriptionsLists all Pro subscriptions in the account.
Read-only operation, no side effects.
create_pro_subscriptionCreates a new Pro subscription with advanced configuration options.
Creates a new resource, but doesn't modify existing ones.
get_essential_subscriptionsLists all Essential subscriptions (paginated).
Read-only operation, no side effects.
get_essential_subscription_by_idGets detailed information about a specific Essential subscription.
Read-only operation, no side effects.
create_essential_subscriptionCreates a new Essential subscription.
Creates a new resource, but doesn't modify existing ones.
delete_essential_subscriptionDeletes an Essential subscription.
Deletes a resource, potentially causing data loss or service disruption.
get_database_modulesLists all available database modules supported in the account.
Read-only operation, no side effects.
get_pro_plans_regionsGets available regions across cloud providers.
Read-only operation, no side effects.
get_essentials_plansLists available Essential subscription plans (paginated).
Read-only operation, no side effects.
get_tasksLists all current tasks in the account.
Read-only operation, no side effects.
get_task_by_idGets detailed information about a specific task.
Read-only operation, no side effects.
Safety Assessment
This MCP server allows both read and write operations on Redis Cloud resources. While API key authentication is used, the lack of granular permissions and the potential for destructive actions (like deleting subscriptions) make it moderately risky. It's safer for read-only tasks and riskier when creating or deleting resources.
- API Key authentication adds a layer of security.
- Clear separation of read and write operations.
- Task management provides some level of monitoring and control.
- Docker containerization provides some isolation.
- API keys are passed as environment variables, posing a risk if not handled carefully.
- Write operations like creating and deleting subscriptions can have significant impact.
- Lack of explicit RBAC means the API key likely has broad permissions.
- No mention of input sanitization, increasing risk of injection attacks.
- Direct internet access required.
