Redis Cloud
mcpother officialio.docker.mcp/redis-cloud · v015aaa6bfeec
MCP Server for Redis Cloud's API, allowing you to manage your Redis Cloud resources using natural language.
run it
on your own machines, one way per deploy methodgenerated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
#!/usr/bin/env bash
# redis-cloud (io.docker.mcp/redis-cloud), recipe docker (generated).
# Generated by Hub for toolset "my-agent"; started by mcp-my-agent-redis-cloud.service.
set -euo pipefail
export HOST=127.0.0.1 PORT=8101
exec docker run --rm --name mcp-my-agent-redis-cloud -p 127.0.0.1:${PORT}:8000 --env-file /etc/mcp/my-agent.env mcp/redis-cloud
[Unit]
Description=MCP server redis-cloud (toolset my-agent), generated by Hub
After=network-online.target docker.service
Wants=network-online.target
[Service]
Type=simple
User=mcp
Group=mcp
SupplementaryGroups=docker
EnvironmentFile=/etc/mcp/my-agent.env
Environment=HOME=/var/lib/mcp/redis-cloud
WorkingDirectory=/var/lib/mcp/redis-cloud
ExecStart=/opt/mcp/my-agent/bin/redis-cloud.sh
Restart=on-failure
RestartSec=5
NoNewPrivileges=true
ProtectSystem=strict
ProtectHome=true
PrivateTmp=true
ReadWritePaths=/var/lib/mcp/redis-cloud
[Install]
WantedBy=multi-user.target
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
docker run --rm -p 127.0.0.1:8101:8000 -e SECRET_KEY mcp/redis-cloud
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T23:56:41+00:00).
# Each package server runs behind a stdio->HTTP bridge and listens on localhost only.
# cp .env.example .env # fill the ${VAR}s
# docker compose up -d && bash smoke.sh
# Remote servers are not here: clients reach them directly (see clients/).
name: mcp-my-agent
services:
redis-cloud:
image: mcp/redis-cloud
ports:
- 127.0.0.1:8101:8000
restart: unless-stopped
x-note: 'CHANGE_ME: check the image''s README for its transport and port; this assumes streamable
HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command
instead.'
environment:
SECRET_KEY: ${SECRET_KEY}
volumes:
npm-cache: {}
uv-cache: {}
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T23:56:41+00:00).
# kubectl create namespace mcp
# kubectl -n mcp create secret generic mcp-credentials --from-env-file=.env
# kubectl apply -f kubernetes.yaml
# Services are cluster-internal: <name>.mcp.svc.cluster.local:8000/mcp. Put an ingress
# with auth in front before exposing any of them.
apiVersion: v1
kind: Namespace
metadata:
name: mcp
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: redis-cloud
namespace: mcp
labels: &id001
app: redis-cloud
spec:
replicas: 1
selector:
matchLabels: *id001
template:
metadata:
labels: *id001
spec:
containers:
- name: redis-cloud
image: mcp/redis-cloud
ports:
- containerPort: 8000
name: http
env:
- name: SECRET_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SECRET_KEY
---
apiVersion: v1
kind: Service
metadata:
name: redis-cloud
namespace: mcp
spec:
selector:
app: redis-cloud
ports:
- port: 8000
targetPort: http
name: http
generated from the record, not tested yet
CHANGE_ME: check the image's README for its transport and port; this assumes streamable HTTP at :8000/mcp. If it speaks stdio only, use it from clients/mcp.json as a `docker run -i` command instead.
# Generated by Hub for toolset "my-agent" (2026-10-17T23:56:41+00:00).
# Credentials come from the Secret 'mcp-credentials' (kubectl create secret generic ... --from-env-file=.env).
# Each server under `servers` is one Deployment + Service; the keys after it configure
# upstream charts a worker verified.
servers:
redis-cloud:
enabled: true
replicas: 1
port: 8000
path: /mcp
container:
name: redis-cloud
image: mcp/redis-cloud
ports:
- containerPort: 8000
name: http
env:
- name: SECRET_KEY
valueFrom:
secretKeyRef:
name: mcp-credentials
key: SECRET_KEY
# helm install my-agent helm/my-agent -n mcp
in the cloud
one click: the provider's deploy form opens filled in, in your own account- koyeb
-
The form opens with CHANGE_ME for each value you supply: SECRET_KEY. Fill them in before you deploy.
Clients connect to the service's https://…koyeb.app address plus /mcp.
- azure
-
A Container Apps environment with one app per server, each with HTTPS ingress and one replica. The portal asks for each value you supply as a secure parameter; the deployment's outputs list the endpoints.
connect to it
copy what your client needsdocker run -i --rm -e SECRET_KEY mcp/redis-cloud
{
"mcpServers": {
"redis-cloud": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SECRET_KEY",
"mcp/redis-cloud"
],
"env": {
"SECRET_KEY": "${SECRET_KEY}"
}
}
}
}
#!/usr/bin/env bash
# Registers every server with Claude Code (run once; `claude mcp list` to check).
set -euo pipefail
set -a; [ -f .env ] && source .env; set +a
claude mcp add redis-cloud -e "SECRET_KEY=${SECRET_KEY}" -- docker run -i --rm -e SECRET_KEY mcp/redis-cloud
{
"mcpServers": {
"redis-cloud": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SECRET_KEY",
"mcp/redis-cloud"
],
"env": {
"SECRET_KEY": "${SECRET_KEY}"
}
}
}
}
{
"servers": {
"redis-cloud": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"SECRET_KEY",
"mcp/redis-cloud"
],
"env": {
"SECRET_KEY": "${SECRET_KEY}"
}
}
}
}
name: my-agent target: local servers: - hub: io.docker.mcp/redis-cloud
- not probed yet: tools unpinned, ingest lists them
tools
Probe result: faileddocker: the container exited: [DEBUG 2026-10-17T14:52:59.392Z] Missing API key or secret key. Please provide them via environment variables (API_KEY, SECRET_KEY) or command line arguments (--api-key=value --secret-key=value)
runs · 1
the latest tests of this entry by the hub and its workers, newest first| date | worker | method | status | sandbox | reason |
|---|---|---|---|---|---|
| 2026-10-17 14:53 | local-mac-vm | docker | failed | gvisor | docker: the container exited: [DEBUG 2026-10-17T14:52:59.392Z] Missing API key or secret key. Please provide them via environment variables (API_KEY, SECRET_KEY… |