This server also ships inside Upstash Agent Skills — a plugin that installs it already configured.
An agent can operate your Upstash account, not just read it.
What it takes off you is the console work: find the database behind a failing job, read why the job died, retry it, stand up the index the next feature needs — asked in the words the problem arrived in. The reach is every resource in the account the grant covers, and on a read/write connection one call deletes a database and everything in it, so the read-only choice on the consent page is a real decision rather than a formality.
What it is
Upstash runs this server at a URL, so nothing is installed and your client holds only the address. The first tool call opens a consent page where you choose which account it reaches — your own or a team's — and whether it may change anything. Upstash calls this the recommended setup; the local server it also publishes covers four of these products rather than all seven.
What you get
- Create, back up, rename and delete Redis databases, and run Redis commands against one over the REST API
- QStash and Workflow delivery logs and the dead-letter queue, with failed runs restartable, resumable or cancellable
- Vector and Search indexes queried by similarity, by full text or by document ID, and documents upserted or deleted
- Sandboxed containers with a shell, git, an optional headless browser and cron schedules of their own
- Buckets and presigned upload URLs, for getting a file an agent produced back out as a link
- A read-only mode — chosen on the consent page, or a key scoped to read only
- A ?features= switch that gives one connection only the products you name
Requirements
An Upstash account, and a client that can reach a remote endpoint. There is nothing to paste on the default path: sign-in happens in the browser on the first tool call, and the config holds only the URL. For headless or CI use, an account email plus a Developer API key, sent as an Authorization header instead of signing in.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen