Skip to main content
Each section below covers everything for one agent: the Upstash Skills (docs and the upstash CLI reference your agent loads on demand) and the MCP server (live tools for your account). The MCP server needs your account email and an API key from Upstash Console → Account → API Keys. Readonly keys work; the server then disables every tool that would change state. The skills need no credentials.

Claude Code

The upstash/skills repo is a Claude Code plugin marketplace. From inside Claude Code:
The plugin only carries the skills. Add the MCP server separately:
See the Claude Code plugin docs and MCP docs for more info.

Claude Desktop

Both Claude Desktop and claude.ai accept custom skills as a ZIP upload. Grab the combined skill folder and zip it:
Then go to Customize → Skills, click + Create skill → Upload a skill, and upload upstash.zip. The skill can be toggled on and off from the same list. For the MCP server, open Claude Desktop’s developer settings and edit claude_desktop_config.json. See the Claude Desktop MCP docs for more info.

Cursor

Install the skills with the Agent Skills CLI:
For the MCP server, use the one-click install: Install MCP Server Or go to SettingsCursor SettingsMCPAdd new global MCP server, or edit ~/.cursor/mcp.json directly. Create .cursor/mcp.json in your repo to scope it to a project instead.

OpenAI Codex

The repo is also a Codex plugin. Install it with the Codex CLI:
Add the MCP server with the CLI as well:
Or add it to ~/.codex/config.toml (or a project-level .codex/config.toml) by hand:
If you see startup timeout errors, increase startup_timeout_sec to 40.
See the Codex plugin docs and MCP docs for more info.

OpenCode

OpenCode loads Agent Skills from .agents/skills/ in a project and ~/.config/opencode/skills/ globally, which is where the Agent Skills CLI writes them:
OpenCode exposes the installed skills through its native skill tool, so only the sub-skill relevant to the task is loaded. For the MCP server, add this to ~/.config/opencode/opencode.json or a project-level opencode.json. See the OpenCode MCP docs for more info.

Zed

Zed loads Agent Skills from .agents/skills/ in a project and ~/.agents/skills/ globally:
The skills show up in Zed’s Agent Panel, and the agent can load them on its own or via /upstash. Zed’s extension marketplace has no channel for skills, so the CLI is the only way to install them. For the MCP server, the repo ships a Zed extension in zed-extension/. Clone the repo, run zed: install dev extension from the command palette, and pick the zed-extension/ directory. Zed then prompts for upstash_email and upstash_api_key (and an optional upstash_box_api_key for Upstash Box tools). To skip the extension, add the server to your Zed settings by hand (zed: open settings file). See the Zed MCP docs for more info.
Context servers are project-scoped in Zed. Open a folder before testing, otherwise the server never starts.

GitHub Copilot

Install the skills for Copilot in VS Code with the Agent Skills CLI:
For the MCP server, use the one-click install: Install in VS Code (npx) Or add this to .vscode/mcp.json, or paste it into the mcp.servers user setting. See the VS Code MCP docs for more info.

Windsurf

Install the skills with the Agent Skills CLI:
For the MCP server, add this to ~/.codeium/windsurf/mcp_config.json. See the Windsurf MCP docs for more info.

Gemini CLI

Install the skills with the Agent Skills CLI:
For the MCP server, open ~/.gemini/settings.json and add Upstash to mcpServers. See the Gemini CLI configuration docs for details.

Google Antigravity

Install the skills with the Agent Skills CLI:
For the MCP server, add this to your Antigravity MCP config. See the Antigravity MCP docs for more info.

DeepSeek Harness

The repo is a DeepSeek Harness bundle. Requires pnpm on your PATH.
Installing the bundle mounts the skills as a skill provider right away; no further setup is needed for them. The same bundle also mounts the MCP server (npx -y @upstash/mcp-server@latest over stdio), but it only starts once your credentials are stored. Run this from inside a session:
Credentials are saved to ~/.dsh/.credentials.yaml and the server starts as soon as both are set, and restarts whenever they change.

Grok

Install the skills for Grok Build with the Agent Skills CLI. They land in .grok/skills/ (project) or ~/.grok/skills/ (global):
Grok Build also reads Claude Code marketplaces and plugins automatically, so if you already installed the Claude Code plugin, the skills are available without any extra setup.
Add the MCP server with the Grok CLI. Pass --scope project to write it to .grok/config.toml in the current directory instead of your user config.
Or add it to ~/.grok/config.toml by hand. See the Grok Build MCP docs for more info.
Run grok mcp doctor upstash to check the connection.

Kilo Code

Add this to ~/.config/kilo/kilo.jsonc (global) or kilo.jsonc in the project root:

Copilot CLI

Add this to ~/.copilot/mcp-config.json:

Warp

Go to Settings → Agents → MCP servers → + Add and paste:

Qwen Code

Or add the standard mcpServers entry above to ~/.qwen/settings.json or .qwen/settings.json.

Hermes

Add this to ~/.hermes/config.yaml:

Factory

fx

fx installs skills straight from a GitHub repo. From inside a session:
Add the MCP server the same way:
Or add it to ~/.fx/mcp.json by hand. See the fx MCP docs for more info.

Crush

Add this to your Crush config file:

Any other agent

The Agent Skills CLI supports 70+ agents and detects the ones on your machine:
Add --global (-g) to make the skills available in every project, --agent (-a) to target a specific agent, and --skill (-s) to install a single SDK skill (for example --skill upstash-qstash-js). For the MCP server, most clients take the standard mcpServers shape below. Check your client’s documentation for where the config lives, then add:
Some of the clients that use it, with their Agent Skills CLI id: