---
name: upstash-cli
description: Run the Upstash CLI (`upstash`) from a terminal, shell script, or CI job when no Upstash MCP tools are in the session. Do not load this skill when Upstash MCP tools are available (the Upstash plugin registers mcp.upstash.com) - they already cover creating, listing, renaming, and deleting Redis databases, running Redis commands, usage stats, backups, Vector and Search indexes, QStash schedules and messages, Blob buckets, and Box, so call them directly. Use this skill for shell work the MCP does not do - a CI step or provisioning script that needs `upstash` commands with JSON output, piping results into other commands, `upstash auth login` and API-key setup, team and member management, changing plans, regions, TLS, eviction, auto-upgrade, or budgets, minting temporary S3 credentials for a Blob bucket, connecting a coding agent to Upstash with `upstash setup` (the Upstash plugin, or the remote MCP server plus skills), or when the user explicitly asks for the CLI or for managing Upstash without the console.
license: MIT
metadata:
author: Upstash
homepage: https://upstash.com
---
## Prefer the MCP server when it is available
If Upstash MCP tools are in the session, call them instead of shelling out to the CLI. They are
already authenticated and cover the same ground — creating and inspecting Redis databases, running
Redis commands, usage stats, backups, Vector and Search indexes, Blob buckets, QStash schedules and
messages, the DLQ, and logs. Installing the Upstash plugin registers the hosted server at
`https://mcp.upstash.com/mcp`.
Use the CLI when there is no MCP in the session, or when the work is inherently shell work — a CI
step, a provisioning script, or piping JSON into other commands.
The Upstash CLI (`upstash`) manages Upstash services via the Upstash Developer API. All commands are non-interactive and emit JSON on stdout. Errors go to stderr as `{ "error": "..." }` with exit code `1`.
## Install
```bash
npm i -g upstash
```
Or run a single command without installing: `npx upstash `.
## Connect coding agents to Upstash
`upstash setup` connects coding agents to Upstash in one step. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (the Upstash skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server (`https://mcp.upstash.com/mcp`) in their config plus the `upstash` skill. The MCP server signs in with OAuth on first use, so setup never writes an API key into an agent's config.
A person at a terminal can run `npx upstash`: with no arguments in a terminal it starts `upstash setup` and asks which agents to set up. Outside a terminal a bare `upstash` only prints the help, so from an agent or a script call `upstash setup` with `--yes` and the agent flags:
```bash
npx -y upstash setup --yes --claude # or --codex, --cursor, --gemini, --vscode, --copilot, --opencode
npx -y upstash setup --yes --cursor --mode mcp # remote MCP server + skill instead of the plugin
npx -y upstash setup --yes --claude --project # this project instead of the user config
npx -y upstash setup --yes --dry-run # show what would change; without agent flags, --yes covers every detected agent
```
With `--project`, Claude Code installs the plugin at project scope; Codex, Cursor, and Gemini CLI plugins install per user only, so they get project-level MCP config plus the skill instead. Rerunning `setup` updates what it installed. Afterwards the agent needs a restart or reload (in Claude Code, `/reload-plugins`; in Cursor, Developer: Reload Window).
## Authentication
Recommended: run `upstash login` once per machine. Prompts for email and a Developer API key (create one at https://console.upstash.com/account/api), verifies them, and saves to `~/.config/upstash/config.json`.
```bash
upstash login
```
Alternatives — env vars (also auto-loaded from a `.env` in cwd), or `--email` / `--api-key` inline, or `--env-path ` to point at a specific `.env`:
```bash
export
[email protected]
export UPSTASH_API_KEY=your_api_key
```
Precedence: flags > env vars > `.env` > saved config. Prefer a **read-only** API key for agents when possible — mutations fail at the API, the same way they would in the console.
## Resource ID flags
| Flag | Products |
|------|----------|
| `--db-id ` | Redis |
| `--index-id ` | Vector, Search |
| `--qstash-id ` | QStash |
| `--bucket-id ` | Blob |
| `--team-id ` | Team |
## Redis
```bash
upstash redis list
upstash redis get --db-id [--hide-credentials]
upstash redis create --name --region [--read-regions ]
upstash redis delete --db-id [--dry-run]
upstash redis rename --db-id --name
upstash redis reset-password --db-id
upstash redis stats --db-id
upstash redis enable-tls --db-id
upstash redis {enable,disable}-eviction --db-id
upstash redis {enable,disable}-autoupgrade --db-id
upstash redis change-plan --db-id --plan
upstash redis update-budget --db-id --budget
upstash redis update-regions --db-id --read-regions
upstash redis move-to-team --db-id --team-id
```
Regions — AWS: `us-east-1`, `us-east-2`, `us-west-1`, `us-west-2`, `ca-central-1`, `eu-central-1`, `eu-west-1`, `eu-west-2`, `sa-east-1`, `ap-south-1`, `ap-northeast-1`, `ap-southeast-1`, `ap-southeast-2`, `af-south-1`. GCP: `us-central1`, `us-east4`, `europe-west1`, `asia-northeast1`.
### Redis backups
```bash
upstash redis backup list --db-id
upstash redis backup create --db-id --name
upstash redis backup delete --db-id --backup-id [--dry-run]
upstash redis backup restore --db-id --backup-id
upstash redis backup {enable,disable}-daily --db-id
```
### Redis exec (REST, not the Developer API key)
```bash
upstash redis exec --db-url --db-token SET key value
upstash redis exec --db-url --db-token --json '["SET","key","value"]'
```
`--db-url` / `--db-token` fall back to `UPSTASH_REDIS_REST_URL` / `UPSTASH_REDIS_REST_TOKEN`. Get both from `endpoint` and `rest_token` in `upstash redis get --db-id `.
## Team
```bash
upstash team list
upstash team create --name [--copy-cc]
upstash team delete --team-id [--dry-run]
upstash team members --team-id
upstash team add-member --team-id --member-email --role
upstash team remove-member --team-id --member-email [--dry-run]
```
## Vector
```bash
upstash vector list
upstash vector get --index-id
upstash vector create --name --region --similarity-function --dimension-count [--type payg] [--index-type ] [--embedding-model ] [--sparse-embedding-model ]
upstash vector delete --index-id [--dry-run]
upstash vector rename --index-id --name
upstash vector reset-password --index-id
upstash vector set-plan --index-id --plan
upstash vector transfer --index-id --target-account
upstash vector stats # aggregate across all indexes
upstash vector index-stats --index-id [--period <1h|3h|12h|1d|3d|7d|30d>]
```
Regions: `eu-west-1`, `us-east-1`, `us-central1`. Similarity: `COSINE`, `EUCLIDEAN`, `DOT_PRODUCT`. Index types: `DENSE`, `SPARSE`, `HYBRID`. Dense models: `BGE_SMALL_EN_V1_5`, `BGE_BASE_EN_V1_5`, `BGE_LARGE_EN_V1_5`, `BGE_M3`. Sparse models: `BM25`, `BGE_M3`. For `HYBRID` with managed embeddings, set `--dimension-count 0`.
## Search
```bash
upstash search list
upstash search get --index-id
upstash search create --name --region --type
upstash search delete --index-id [--dry-run]
upstash search rename --index-id --name
upstash search reset-password --index-id
upstash search transfer --index-id --target-account
upstash search stats
upstash search index-stats --index-id [--period <1h|3h|12h|1d|3d|7d|30d>]
```
Regions: `eu-west-1`, `us-central1`.
## QStash
```bash
upstash qstash list # run first; maps region → id
upstash qstash get --qstash-id
upstash qstash rotate-token --qstash-id
upstash qstash set-plan --qstash-id --plan
upstash qstash stats --qstash-id [--period <1h|3h|12h|1d|3d|7d|30d>]
upstash qstash ipv4 # CIDR blocks for allowlisting
upstash qstash move-to-team --qstash-id --target-team-id
upstash qstash update-budget --qstash-id --budget # 0 = no limit
upstash qstash {enable,disable}-prodpack --qstash-id
```
## Blob
Run `upstash blob --help` to check that the installed CLI includes Blob support. If the command is unavailable, use the console for bucket management and `upstash-blob-js` for application code until a CLI release includes it.
```bash
upstash blob list
upstash blob get --bucket-id [--hide-credentials]
upstash blob create --name [--visibility ] [--cors ]
upstash blob delete --bucket-id [--dry-run]
upstash blob credentials [--bucket-id ]
```
Buckets are `private` by default. `blob get` returns the bucket token, which is a bearer secret for the whole bucket — pass `--hide-credentials` when you only need the metadata.
`blob credentials` exchanges a bucket token for temporary, bucket-scoped S3 credentials to use with the AWS CLI, rclone, or any S3 SDK. With `--bucket-id` it reads the token through the Developer API; with no flag it uses `UPSTASH_BLOB_TOKEN` and needs no account auth at all. `expiresAt` is the expiry as a **unix timestamp in seconds** (multiply by 1000 before comparing with `Date.now()`) — re-mint before it passes rather than caching.
```bash
CREDS=$(upstash blob credentials --bucket-id )
export AWS_ACCESS_KEY_ID=$(echo "$CREDS" | jq -r .accessKeyId)
export AWS_SECRET_ACCESS_KEY=$(echo "$CREDS" | jq -r .secretAccessKey)
export AWS_SESSION_TOKEN=$(echo "$CREDS" | jq -r .sessionToken)
aws s3 cp image.png "s3://$(echo "$CREDS" | jq -r .bucket)/image.png" \
--endpoint-url "$(echo "$CREDS" | jq -r .endpoint)" --region auto
```
Object operations are not CLI commands — the bucket is S3-compatible, so use the credentials above with an S3 tool, or the `upstash-blob-js` skill for the TypeScript SDK.
## Conventions
- Pipe any output to `jq` for field extraction, e.g. `upstash redis list | jq '.[].database_id'`.
- Use `--dry-run` first on any `delete` or `remove-member`.
- Use `--hide-credentials` on `redis get` and `blob get` when the secret isn't needed.
