Upstash Redis
Read and write an Upstash Redis database over its HTTP REST API.
About
Upstash Redis ships in the w6w first-party pack. It declares 15 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.upstash- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Databases
Overview
Upstash Redis is a serverless Redis database reachable entirely over HTTP, and this app reads and writes it directly: getting and setting keys, incrementing counters, managing lists, hashes, and sets, and setting expirations. It is built for workflows that need fast key-value storage or simple counters and queues — caching a value, tracking a count, or building a small work queue — without needing a persistent connection.
It covers the commands most commonly automated: string get/set with optional expiry, atomic increment and decrement, list pushes and range reads, hash field get/set and full-hash reads, and set membership operations. Because Upstash exposes its full command set over a REST API rather than the raw Redis wire protocol, every one of these works from a sandboxed workflow step the same way a normal API call would, with no socket or driver required.
Build with Upstash Redis
Three routes to the same 15 actions. The Workflow tab is generated from Upstash Redis's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Upstash Redis's real ids.
{
"manifestVersion": "2",
"name": "upstash-example",
"steps": [
{
"id": "decr",
"uses": {
"app": "io.w6w.upstash",
"action": "decr",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"key": "<key>"
}
}
]
}Here are some of the things you can do
-
Decrement
performdecr -
Delete Key(s)
performdel -
Check Exists
readexists -
Set Expiry
performexpire -
Get Value
readget
+10 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Upstash Redis, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Upstash Redis. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "set",
payload: {
key: "<value>",
value: "<value>",
// ttlSeconds: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action set --payload '{"key":"<value>","value":"<value>"}'Give an AI agent Upstash Redis — without giving it Upstash Redis's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.upstash#decr",
"input": {
"key": "<key>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Upstash Redis connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Upstash Redis's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Upstash Redis itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Upstash Redis declares its own checks, so its health is a property of the app rather than something the host guesses at.
Upstash platform status
status.upstash.com's JSON summary — Redis, Vector and QStash across every region.
Database host reachable
Unauthenticated PING against this connection's REST URL. A 401 passes — it proves the host is answering; credential validity is the auth:rest-token check's job.