Install by agent - Upstash Documentation

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). Every section sets up the remote MCP server (https://mcp.upstash.com/mcp), which needs no credentials up front — it authenticates over OAuth on first use, and the Upstash plugin for Claude Code, Claude Desktop, and Codex bundles it, so installing the plugin also connects the MCP. The local (stdio) server is the alternative, folded into each section. It needs your account email and a Developer API key (readonly keys work; the server then disables every mutating tool), and it is the only one that carries Upstash Box tools — the remote server covers Redis, QStash, Workflow, Vector, and Search. The skills need no credentials either way. See the MCP server page for remote vs. local, authentication, and feature options.

Claude Code

The upstash/skills repo is a Claude Code plugin marketplace. From inside Claude Code:

/plugin marketplace add upstash/skills
/plugin install upstash@upstash

The plugin bundles the remote MCP server (over OAuth), so this one install sets up both the skills and the MCP — approve the consent screen on the first tool call. To add the remote server on its own, without the plugin:

claude mcp add --scope user --transport http upstash https://mcp.upstash.com/mcp

Then run /mcp → Authenticate.

Local (stdio) server instead

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

See the Claude Code plugin docs and MCP docs for more info.

Claude Desktop

Claude Desktop reads the same upstash/skills plugin marketplace as Claude Code, and the plugin bundles the skills and the remote MCP server (over OAuth) together. Go to Customize → Plugins, click Add → Add marketplace, choose Add from a repository, and give it upstash/skills. Install the upstash plugin from that marketplace, then approve the consent screen on the first tool call.

Cursor

Install the skills with the Agent Skills CLI:

npx skills add upstash/skills --agent cursor

For the MCP server, use the one-click install:

It writes a global server; move the upstash entry into .cursor/mcp.json in your repo to scope it to one project instead. Or add it to ~/.cursor/mcp.json by hand — Cursor runs the OAuth flow on the first tool call:

{
  "mcpServers": {
    "upstash": { "url": "https://mcp.upstash.com/mcp" }
  }
}

Local (stdio) server instead

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

OpenAI Codex

The repo is also a Codex plugin. Install it with the Codex CLI:

codex plugin marketplace add upstash/skills
codex plugin add upstash@upstash

The plugin bundles the remote MCP server (over OAuth), so this also connects the MCP — approve the consent screen on the first tool call. To add the remote server on its own, put this in ~/.codex/config.toml (or .codex/config.toml):

[mcp_servers.upstash]
url = "https://mcp.upstash.com/mcp"

Local (stdio) server instead

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

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:

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

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

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.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "upstash": {
      "type": "remote",
      "url": "https://mcp.upstash.com/mcp",
      "enabled": true
    }
  }
}

Local (stdio) server instead

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "upstash": {
      "type": "local",
      "command": ["npx", "-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"],
      "enabled": true
    }
  }
}

Zed

Zed loads Agent Skills from .agents/skills/ in a project and ~/.agents/skills/ globally:

# 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 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, go to Settings → AI → MCP Servers, click Add Server → Add Remote Server, or put this in settings.json. With no Authorization header configured, Zed runs the standard MCP OAuth flow:

{
  "context_servers": {
    "upstash": {
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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).

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:

npx skills add upstash/skills --agent github-copilot

For the MCP server, use the one-click install:

It writes the server to .vscode/mcp.json. See the VS Code MCP docs for more info.

{
  "servers": {
    "upstash": {
      "type": "http",
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Devin Desktop

Devin Desktop is the new name for Windsurf. It keeps the same skill target and settings. Install the skills with the Agent Skills CLI:

npx skills add upstash/skills --agent windsurf

For the MCP server, add this to ~/.codeium/windsurf/mcp_config.json. See the Devin Desktop migration notes for more info.

{
  "mcpServers": {
    "upstash": {
      "serverUrl": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Gemini CLI

Install the skills with the Agent Skills CLI:

npx skills add upstash/skills --agent gemini-cli

Add the MCP server with the CLI:

gemini mcp add --transport http upstash https://mcp.upstash.com/mcp

Or open ~/.gemini/settings.json and add Upstash to mcpServers by hand. See the Gemini CLI configuration docs for details.

{
  "mcpServers": {
    "upstash": {
      "httpUrl": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Google Antigravity

Install the skills with the Agent Skills CLI:

npx skills add upstash/skills --agent antigravity

For the MCP server, add this to your Antigravity MCP config. Antigravity registers itself as an OAuth client, so no credentials go in the file. See the Antigravity MCP docs for more info.

{
  "mcpServers": {
    "upstash": {
      "serverUrl": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

DeepSeek Harness

The repo is a DeepSeek Harness bundle. 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

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 local (stdio) MCP server (npx -y @upstash/mcp-server@latest), the one client here that does not use the remote server. It only starts once your credentials are stored. Run this from inside a session:

/upstash-login YOUR_EMAIL YOUR_API_KEY

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):

npx skills add upstash/skills --agent grok

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.

grok mcp add --transport http upstash https://mcp.upstash.com/mcp

Or add it to ~/.grok/config.toml by hand. Grok opens the OAuth flow on first use and stores the tokens in ~/.grok/mcp_credentials.json. See the Grok Build MCP docs for more info.

[mcp_servers.upstash]
url = "https://mcp.upstash.com/mcp"

Local (stdio) server instead

[mcp_servers.upstash]
command = "npx"
args = ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"]

Run grok mcp doctor upstash to check the connection.

Kilo Code

npx skills add upstash/skills --agent kilo

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

{
  "mcp": {
    "upstash": {
      "type": "remote",
      "url": "https://mcp.upstash.com/mcp",
      "enabled": true
    }
  }
}

Local (stdio) server instead

{
  "mcp": {
    "upstash": {
      "type": "local",
      "command": ["npx", "-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"],
      "enabled": true
    }
  }
}

Copilot CLI

npx skills add upstash/skills --agent github-copilot

copilot mcp add --transport http upstash https://mcp.upstash.com/mcp

Or add it to ~/.copilot/mcp-config.json by hand:

{
  "mcpServers": {
    "upstash": {
      "type": "http",
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Warp

npx skills add upstash/skills --agent warp

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

{
  "upstash": {
    "url": "https://mcp.upstash.com/mcp",
    "start_on_launch": true
  }
}

Local (stdio) server instead

{
  "upstash": {
    "command": "npx",
    "args": ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"],
    "env": {},
    "working_directory": null,
    "start_on_launch": true
  }
}

Qwen Code

npx skills add upstash/skills --agent qwen-code

qwen mcp add --transport http upstash https://mcp.upstash.com/mcp

Or add the entry to ~/.qwen/settings.json or .qwen/settings.json by hand:

{
  "mcpServers": {
    "upstash": {
      "httpUrl": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Hermes

npx skills add upstash/skills --agent hermes-agent

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

mcp_servers:
  upstash:
    url: "https://mcp.upstash.com/mcp"

Local (stdio) server instead

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

Factory

npx skills add upstash/skills --agent droid

droid mcp add upstash https://mcp.upstash.com/mcp --type http

Local (stdio) server instead

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

fx

fx installs skills straight from a GitHub repo. From inside a session:

/skills install upstash/skills --skill upstash

Add the MCP server the same way:

/mcp add --transport http upstash https://mcp.upstash.com/mcp

Or add it to ~/.fx/mcp.json by hand. See the fx MCP docs for more info.

{
  "mcp": {
    "upstash": {
      "type": "http",
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

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

Crush

npx skills add upstash/skills --agent crush

Add this to your Crush config file:

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "upstash": {
      "type": "http",
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Local (stdio) server instead

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "upstash": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"]
    }
  }
}

Any other agent

The Agent Skills CLI supports 70+ agents and detects the ones on your machine:

npx skills add upstash/skills

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:

{
  "mcpServers": {
    "upstash": {
      "url": "https://mcp.upstash.com/mcp"
    }
  }
}

Some clients want the transport named alongside the URL — "type": "http" for most, "type": "streamable-http" for Roo Code, "type": "remote" for OpenCode and Kilo Code. An unrecognized key is usually ignored, so when in doubt start with the plain url above.

Local (stdio) server instead

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

Some of the clients that use it, with their Agent Skills CLI id:

Client	Skills `id`	MCP server
Amp	`amp`	`amp mcp add upstash https://mcp.upstash.com/mcp`
Kiro	`kiro-cli`	`.kiro/settings/mcp.json`, or Kiro → MCP Servers → + Add; takes `url`
Cline	`cline`	MCP Servers → Remote Servers → Edit Configuration; takes `url`
Roo Code	`roo`	MCP settings file (`mcp_settings.json`); needs `"type": "streamable-http"`
Trae	`trae`	MCP → Add manually; takes `url`
Augment Code	`augment`	Settings → MCP → + Add remote MCP, connection type HTTP
Zencoder	`zencoder`	Agent tools → Add custom MCP, paste the `upstash` entry
Rovo Dev CLI	`rovodev`	`acli rovodev mcp` opens the config file; takes `url`

​Claude Code

​Claude Desktop

​Cursor

​OpenAI Codex

​OpenCode

​Zed

​GitHub Copilot

​Devin Desktop

​Gemini CLI

​Google Antigravity

​DeepSeek Harness

​Grok

​Kilo Code

​Copilot CLI

​Warp

​Qwen Code

​Hermes

​Factory

​fx

​Crush

​Any other agent

Claude Code

Claude Desktop

Cursor

OpenAI Codex

OpenCode

Zed

GitHub Copilot

Devin Desktop

Gemini CLI

Google Antigravity

DeepSeek Harness

Grok

Kilo Code

Copilot CLI

Warp

Qwen Code

Hermes

Factory

fx

Crush

Any other agent