Skip to main content
Pick your agent below. The first block in each section is the recommended setup: it connects the remote MCP server at https://mcp.upstash.com/mcp and installs the Upstash Skills. Neither needs credentials up front. The MCP server asks you to sign in over OAuth on the first tool call. Everything else, such as editing the config file by hand or running the local (stdio) server with your email and a Developer API key, is under Other options in each section. See the MCP server page for how the remote and local servers compare.

Claude Code

From inside Claude Code:
The plugin bundles the skills and the remote MCP server. Approve the consent screen on the first tool call.
MCP server only, without the plugin
Then run /mcpAuthenticate.Local (stdio) server
See the Claude Code plugin docs and MCP docs for more info.

Claude Desktop

Go to Customize → Plugins, click Add → Add marketplace, choose Add from a repository, and enter upstash/skills. Install the upstash plugin from that marketplace. The plugin bundles the skills and the remote MCP server. Approve the consent screen on the first tool call.

Cursor

Add the MCP server with one click: Install MCP Server Then install the skills:
Add the MCP server by handPut this in ~/.cursor/mcp.json, or in .cursor/mcp.json to scope it to one project:
Local (stdio) server

OpenAI Codex

The plugin bundles the skills and the remote MCP server. Approve the consent screen on the first tool call.
MCP server only, without the pluginPut this in ~/.codex/config.toml, or in .codex/config.toml for one project:
Local (stdio) server
See the Codex plugin docs and MCP docs for more info.

OpenCode

Add the MCP server to opencode.json, or ~/.config/opencode/opencode.json for every project:
Then install the skills (add --global to make them available in every project):
Local (stdio) server
See the OpenCode skills and MCP docs for more info.

Zed

Add the MCP server to settings.json, or through Settings → AI → MCP Servers → Add Server → Add Remote Server:
Context servers are project-scoped in Zed. Open a folder before testing, otherwise the server never starts.
Then install the skills (add --global to make them available in every project):
Local (stdio) serverThe 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, plus an optional upstash_box_api_key to enable Upstash Box tools.See the Zed skills and MCP docs for more info.

GitHub Copilot

Add the MCP server to VS Code with one click: Install in VS Code Then install the skills:
Add the MCP server by handPut this in .vscode/mcp.json:
Local (stdio) server
See the VS Code MCP docs for more info.

Devin Desktop

Devin Desktop is the new name for Windsurf and keeps its settings. Add the MCP server to ~/.codeium/windsurf/mcp_config.json:
Then install the skills:
Local (stdio) server
See the Devin Desktop migration notes for more info.

Gemini CLI

The extension bundles the skills and the remote MCP server. Approve the consent screen on the first tool call.
MCP server and skills separately
Or add the server to ~/.gemini/settings.json by hand:
Local (stdio) server
See the Gemini CLI extension and MCP docs for more info.

Google Antigravity

Add the MCP server to your Antigravity MCP config. Antigravity registers itself as an OAuth client, so no credentials go in the file:
Then install the skills:
Local (stdio) server
See the Antigravity MCP docs for more info.

DeepSeek Harness

Requires pnpm on your PATH. Install the bundle into a profile (web is the one dsh web boots) and start the harness:
The bundle loads the skills right away. It also mounts the local (stdio) MCP server, which starts once you store your credentials from inside a session:
Credentials are saved to ~/.dsh/.credentials.yaml. The server restarts whenever they change.

Grok

Pass --scope project to grok mcp add to write the server to .grok/config.toml in the current directory. Run grok mcp doctor upstash to check the connection.
Grok Build also reads Claude Code plugins, so if you already installed the Claude Code plugin, the skills are available without the second command.
Add the MCP server by handPut this in ~/.grok/config.toml:
Local (stdio) server
See the Grok Build MCP docs for more info.

Kilo Code

Add the MCP server to kilo.jsonc in the project root, or ~/.config/kilo/kilo.jsonc for every project:
Then install the skills:
Local (stdio) server

Copilot CLI

Add the MCP server by handPut this in ~/.copilot/mcp-config.json:
Local (stdio) server

Warp

Go to Settings → Agents → MCP servers → + Add and paste:
Then install the skills:
Local (stdio) server

Qwen Code

Add the MCP server by handPut this in ~/.qwen/settings.json, or .qwen/settings.json for one project:
Local (stdio) server

Hermes

Add the MCP server to ~/.hermes/config.yaml:
Then install the skills:
Local (stdio) server

Factory

Local (stdio) server

fx

From inside an fx session:
Add the MCP server by handPut this in ~/.fx/mcp.json:
Local (stdio) server
See the fx MCP docs for more info.

Crush

Add the MCP server to your Crush config file:
Then install the skills:
Local (stdio) server

Any other agent

Add the MCP server to your client’s config. Most clients take this shape:
Then install the skills. The Agent Skills CLI supports 70+ agents and detects the ones on your machine:
Skills CLI flagsAdd --global (-g) to install for every project, --agent (-a) to target one agent, and --skill (-s) to install a single SDK skill, for example --skill upstash-qstash-js.Transport typeSome clients want the transport named next to the URL: "type": "http" for most, "type": "streamable-http" for Roo Code, "type": "remote" for OpenCode and Kilo Code. Unrecognized keys are usually ignored, so start with the plain url.Local (stdio) server
Where some other clients take it, with their Agent Skills CLI id: