Agent skill · software engineering · upstash
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.
Why this skill is useful
Adds specific commands and workflows for managing Upstash services that the AI wouldn't reliably generate on its own.
What it needs
Requires @upstash/cli installed locally. Requires upstash account access. About 5k tokens when loaded. Last updated 2026-07-14. 17 stars on the source repository.
What this skill does
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, 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 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. 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. Resource ID flags Flag Products ------ ---------- --db-id <id> Redis --index-id <id> Vector, Search --qstash-id <id> QStash --bucket-id <id> Blob --team-id <id> Team Redis 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 Redis exec (REST, not the Developer API key) --db-url / --db-token fall back to UPSTASHREDISRESTURL / UPSTASHREDISRESTTOKEN. Get both from endpoint and resttoken in upstash redis get --db-id <id>. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills upstash/upstash-cli