Upstash for Meta Muse
Community draft proposes: Run Redis commands over REST.
Pinned source description: 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.
Community-authored Draft; OpenTools has not independently installed or live-tested this skill. Ask for the exact Upstash database host, use its matching REST token, read a key first, and confirm each set/delete/pipeline write. Blocking Redis commands are not supported.
View original source ↗How to set it up
Paste a promptDraft — these instructions come from the linked source and have not been independently live-tested by OpenTools.
Source maturity: 🧪 Draft: written from Upstash's public API docs; not yet live-tested end-to-end.
Before you start
- Per-database token (host declared at connect time)
Steps
- Review the pinned connectors/upstash/SKILL.md and its listed files (SKILL.md, bin/upstash.py). This community draft has not been live-tested end to end.
- Before setup: Ask for the exact Upstash database host, use its matching REST token, read a key first, and confirm each set/delete/pipeline write. Blocking Redis commands are not supported.
- Only if the Muse runtime supports pinned repository installs and the source-declared credential and host flow, try `bin/upstash.py --db-host <host> auth`. Report the actual response and verify one safe read before any writes.
Prompt to paste into Muse
Inspect this community skill: https://raw.githubusercontent.com/bluman1/muse-connectors/6e31fd44a71f9f28377a1460e64cd7483c3cce22/connectors/upstash/SKILL.md Read its Files manifest. If this Muse account supports custom skill installation and secure credentials, install exactly those files; otherwise report that the setup is unavailable. Collect credentials through Muse's secure credential flow; never ask me for raw keys in chat. Run the skill's status check and report the actual result.
Account access: 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: *.upstash.io
Source status check: Source-proposed status check (not live-tested by OpenTools): `bin/upstash.py --db-host <host> auth`
A successful source status check may verify only configuration or credentials; it is not proof of a working end-to-end integration.
Services it connects with
These are the services the connector uses. The publisher is identified separately.
Upstash