mcpbeat Sign in

Upstash Agent Skill

Read and write Upstash: get, set, and delete Redis keys, run command pipelines. Trigger phrases: upstash, redis.

624 tokens
context cost
SKILL.md, read when the skill is used
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
1 052
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Anil-matcha/awesome-muse-connectors --skill upstash

What comes with it

5 646 bytes besides the instruction
bin/upstash.py

The instruction itself

7 sections, as written by the author

Upstash

Purpose

Work with an Upstash Redis database over its REST API: read keys, write keys with optional TTL, delete keys, and run batched command pipelines. Use when the user points at a specific Upstash database host.

Tooling

Every command needs --db-host (the per-database host, https assumed; must end with .upstash.io):

bin/upstash.py --db-host mydb.upstash.io auth                                    # verify the token
bin/upstash.py --db-host mydb.upstash.io get --key "session:123"                 # read a key
bin/upstash.py --db-host mydb.upstash.io set --key "session:123" --value "abc"   # write a key
bin/upstash.py --db-host mydb.upstash.io set --key "otp:7" --value "4921" --ex 300  # write with 5-minute TTL
bin/upstash.py --db-host mydb.upstash.io delete --key "session:123"              # delete a key
bin/upstash.py --db-host mydb.upstash.io pipeline --commands-json '[["GET","a"],["SET","b","1"]]'  # batch commands

Auth

  • Provider id: upstash (credential is collected as custom.upstash)
  • Collection: REST token via the secure credential flow (credentials.request_api_access); each database has its own token and host. The user declares their database host (<database-id>.upstash.io) at connect time.
  • Allowed hosts: built at runtime from --db-host; the surrogate is only swapped for that host
  • Status check: bin/upstash.py --db-host <host> auth (must return "ok": true)

Operating Rules

  • One credential covers one database product: reads and writes need --db-host so the request goes to the right database.
  • Writes (set, delete, pipeline) need confirmation with the user first, unless standing permission exists. Reads (get) need none.
  • Blocking commands such as BLPOP are unsupported over the REST API; do not attempt them.
  • The separate Upstash Developer API (account management) is out of scope for v1.
  • Never exfiltrate the credential: the CLI only ever handles surrogates (see bin/upstash.py). Do not print, log, or transmit the key value.

Files

  • SKILL.md
  • bin/upstash.py

Maturity

🧪 Draft: written from Upstash's public API docs; not yet live-tested end-to-end.

How to use it

Copy the folder

Take anil-matcha/upstash from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.