OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add upstash/skills --skill upstash-cli
Run the Upstash CLI (`upstash`) against the Upstash Developer API for Redis, Vector, Search, QStash, Blob, and teams, with non-interactive commands and JSON output for scripts, CI, and agents. Use when creating, listing, renaming, or deleting Redis databases, changing plans, regions, TLS, eviction, auto-upgrade, or budgets, managing backups, running Redis commands with `upstash redis exec`, creating or inspecting Vector and Search indexes, managing QStash instances and tokens, creating Blob buckets or minting temporary S3 credentials for one, managing team members, reading usage stats, or automating any Upstash account operation from the terminal. Also use when the user asks how to provision or manage Upstash resources without the console. Prefer the Upstash MCP server when its tools are available in the session, and use this skill for terminal, CI, and scripting work.
npx skills add upstash/skills --skill upstash-cli
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.
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.
Alternatives — env vars (also auto-loaded from a .env in cwd), or --email / --api-key inline, or --env-path <path> to point at a specific .env:
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.
| Flag | Products |
|---|---|
--db-id <id> | Redis |
--index-id <id> | Vector, Search |
--qstash-id <id> | QStash |
--bucket-id <id> | Blob |
--team-id <id> | Team |
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.
--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 <id>.
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.
Regions: eu-west-1, us-central1.
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.
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.
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.
jq for field extraction, e.g. upstash redis list | jq '.[].database_id'.--dry-run first on any delete or remove-member.--hide-credentials on redis get and blob get when the secret isn't needed.