Upstash Agent Skills

A collection of skills for AI coding agents working with Upstash SDKs. Skills are packaged instructions and resources that extend agent capabilities.

This repo works as an Agent Skills repo, a Claude Code plugin, a Cursor plugin, an OpenAI Codex plugin, and a DeepSeek Harness bundle.

Available Skills

Installation

Claude Code Plugin

# Add the marketplace
/plugin marketplace add upstash/skills

# Install the plugin
/plugin install upstash@upstash

Cursor Plugin

We are waiting for this plugin to be accepted to the official Cursor Marketplace. Once listed, it can be installed from Customize in the Cursor sidebar.

OpenAI Codex Plugin

# Add the marketplace
codex plugin marketplace add upstash/skills

# Install the plugin
codex plugin add upstash@upstash

Zed

Zed loads Agent Skills from .agents/skills/ in a project and ~/.agents/skills/ globally, which is exactly where the Agent Skills CLI writes them:

# Available in every project
npx skills add upstash/skills --agent zed --global

# Or just this project
npx skills add upstash/skills --agent zed

The skills then show up in Zed's Agent Panel, and the agent can load them on its own or via /upstash. Zed's extension marketplace carries languages, themes, debuggers, snippets, and MCP servers, but has no channel for skills, so the CLI is the only way to install them. The Zed extension in zed-extension/ covers the [MCP server](#mcp-server) instead.

Context7 CLI

npx ctx7 skills install upstash/skills

Agent Skills CLI

npx skills add upstash/skills

DeepSeek Harness

Installs the skills and the [Upstash MCP server](#mcp-server) in one step. Requires pnpm on your PATH.

# Install into a profile (`web` is the one `dsh web` boots)
dsh plugin --profile web add github:upstash/skills

# Start the harness
dsh web

Then store your Upstash credentials from inside a session:

/upstash-login YOUR_EMAIL YOUR_API_KEY

Credentials are stored in ~/.dsh/.credentials.yaml and the MCP server connects as soon as both are set. The skills work without them.

MCP Server

For full access to Upstash APIs (create databases, publish messages, query vectors, etc.), you can also set up the @upstash/mcp-server:

<details> <summary>Claude Code</summary>

claude mcp add upstash -- npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY

</details>

<details> <summary>Cursor</summary>

Add to .cursor/mcp.json:

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"]
    }
  }
}

</details>

<details> <summary>Zed</summary>

This repo ships a Zed MCP extension in [zed-extension/](zed-extension/). Once it is accepted into the Zed extension registry, install Upstash Redis MCP Server from Settings → AI → MCP Servers → Add Server → Install from Extensions, and Zed will prompt for upstash_email and upstash_api_key. Until then, install it as a dev extension (zed: install dev extension, then pick the zed-extension/ directory).

To skip the extension entirely, add the server to your Zed settings by hand (zed: open settings file):

{
  "context_servers": {
    "upstash": {
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"]
    }
  }
}

</details>

<details> <summary>DeepSeek Harness</summary>

Already included in the bundle — see [DeepSeek Harness](#deepseek-harness) above. </details>

Making changes

Updating an existing skill

1. Edit the files in the individual skill folder (e.g. skills/upstash-qstash-js/). 2. Run npm run build to regenerate skills/upstash/. 3. Commit both the source changes and the regenerated output.

Adding a new skill

1. Create a new folder under skills/ (e.g. skills/upstash-redis-js/). 2. Add a SKILL.md with the standard frontmatter (name and description) and any supporting files. 3. Run npm run build — the new skill will be picked up automatically. 4. Commit everything.

Changing the combined skill header

The frontmatter and introductory text for skills/upstash/SKILL.md comes from scripts/header.md. Edit that file, then run npm run build.

Updating the plugin version

When making a release, bump the version field in every manifest that carries one: plugin.json (the portable Agent Plugins manifest), .claude-plugin/plugin.json, .cursor-plugin/plugin.json, and .codex-plugin/plugin.json.

The Zed extension

zed-extension/ is a Zed MCP server extension that runs [@upstash/mcp-server](#mcp-server). It is a Rust crate compiled to WebAssembly, and it is only about the MCP server — Zed extensions cannot carry skills.

cd zed-extension
rustup target add wasm32-wasip2   # once
cargo build --release --target wasm32-wasip2

Test a local build with zed: install dev extension and point Zed at zed-extension/. Open Zed on a folder while testing — context servers are project-scoped, so with no project open (or one whose worktree fails to open) the server never starts and the panel sits on "Connecting Server..." until Zed's 60s timeout.

To publish or update it, open a PR against zed-industries/extensions that adds this repo as a submodule under extensions/mcp-server-upstash and an entry in extensions.toml:

[mcp-server-upstash]
submodule = "extensions/mcp-server-upstash"
path = "zed-extension"
version = "0.1.0"

The version there has to match version in zed-extension/extension.toml, so bump both together. zed-extension/LICENSE is a symlink to the repo's MIT license — Zed requires a license at the extension path, not just at the repo root, and rejects the PR in CI without one.

> Zed plans to deprecate MCP server extensions > in favor of the official MCP registry. If that lands, publishing @upstash/mcp-server to > registry.modelcontextprotocol.io replaces this > extension.

Scripts

CI

The GitHub Actions workflow (.github/workflows/check.yml) runs npm run check on every push and PR. If you forget to run npm run build before pushing, CI will fail.