Upstash Redis MCP

What it does

• Deliberately minimal: just `redis_run_commands` (pipeline or MULTI/EXEC transaction) + `redis_search_docs`
• HTTP/REST or TCP per database; multi-database naming via UPSTASH_REDIS_<NAME>_* env or repeated --database
• One-liner for Claude Code: `claude mcp add upstash-redis -e UPSTASH_REDIS_REST_URL=... -e UPSTASH_REDIS_REST_TOKEN=... -- npx -y @upstash/redis-mcp`

When to use it

The lightest Redis MCP: two tools, zero config files, env vars only. Best fit when your Redis lives on Upstash REST anyway, or when you want `--readonly` write-blocking for an agent.

Getting started

{
  "command": "npx",
  "args": ["-y", "@upstash/redis-mcp"],
  "env": {
    "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",
    "UPSTASH_REDIS_REST_TOKEN": "<token>"
  }
}

TCP instead: set UPSTASH_REDIS_TCP_URL (or REDIS_URL) to a rediss:// string.

Things to know

`--readonly` is best-effort client-side filtering — the README itself says server-side read-only REST tokens are the robust option. Per-call credential overrides flow through model context; prefer env/CLI for secrets.