From fa5b3ec012a72d10cd7438fdf134b0c8c7a9128c Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 5 Oct 2026 09:43:46 +0000 Subject: [PATCH 1/9] DX-3074: use `upstash` instead of `@upstash/cli`, lead AI setup with `npx upstash setup` - Docs home copy-prompt asks the agent to run `npx -y upstash setup --yes` with its agent flag, falling back to the per-agent commands. Same text as upstash.com and the console. - AI Tools overview: Quick start leads with `npx upstash setup`. - CLI page: install with `npm i -g upstash`, and a new "Connect your AI agent" section for `upstash setup` and its flags. - Skills page: refer to the `upstash` CLI. - Regenerated llms-full.txt. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01LWUubWwYWp1dZTK1S9Ek95 --- agent-resources/cli.mdx | 23 +++++++++++++++++++++- agent-resources/overview.mdx | 10 +++++++++- agent-resources/skills.mdx | 2 +- introduction.mdx | 2 +- llms-full.txt | 37 ++++++++++++++++++++++++++++++++---- 5 files changed, 66 insertions(+), 8 deletions(-) diff --git a/agent-resources/cli.mdx b/agent-resources/cli.mdx index 6aeb7d366..44d1a4420 100644 --- a/agent-resources/cli.mdx +++ b/agent-resources/cli.mdx @@ -9,15 +9,36 @@ You can find the Github Repository [here](https://github.com/upstash/cli). # Installation ```bash -npm i -g @upstash/cli +npm i -g upstash ``` +Or run any command without installing, for example `npx upstash redis list`. + For agents, install the [Upstash Skill](/agent-resources/skills) instead. It bundles Upstash docs with the `upstash` CLI so your agent can implement and debug against your resources without filling up its context window: ```bash npx skills add upstash/skills ``` +# Connect your AI agent + +`upstash setup` wires Upstash into the coding agents on your machine: + +```bash +npx upstash setup +``` + +In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. + +```bash +upstash setup --claude --cursor -y # pick agents, no prompts +upstash setup --project # this repo instead of your user config +upstash setup --mode mcp # MCP + skill everywhere, no plugins +upstash setup --dry-run # show what would change +``` + +Rerunning `setup` updates what it installed. + # Free Redis without an account If you are an AI agent and need a Redis DB to use or experiment with, you don't need an Upstash account: diff --git a/agent-resources/overview.mdx b/agent-resources/overview.mdx index 437325870..135b74c24 100644 --- a/agent-resources/overview.mdx +++ b/agent-resources/overview.mdx @@ -33,7 +33,15 @@ Don't see your agent? See the [full list of agents](/agent-resources/clients). # Quick start -Install the Upstash skill. It includes the `upstash` CLI reference, so this one step is enough for most workflows: +One command connects the coding agents on your machine to Upstash: + +```bash +npx upstash setup +``` + +It detects Claude Code, Codex, Cursor, Gemini CLI, VS Code, GitHub Copilot CLI, and OpenCode, and lets you pick which to set up. Agents with plugin support get the Upstash plugin (skills plus the remote MCP server); the others get the remote MCP server in their config and the Upstash skill. The MCP server signs in with OAuth on first use. See the [CLI page](/agent-resources/cli#connect-your-ai-agent) for flags. + +To set things up by hand instead, install the Upstash skill. It includes the `upstash` CLI reference, so this one step is enough for most workflows: ```bash npx skills add upstash/skills diff --git a/agent-resources/skills.mdx b/agent-resources/skills.mdx index a2ace47b2..dc0b30422 100644 --- a/agent-resources/skills.mdx +++ b/agent-resources/skills.mdx @@ -138,4 +138,4 @@ Add `--global` (`-g`) to make the skills available in every project instead of j # Managing resources -The combined `upstash` skill includes the full `@upstash/cli` command reference, so your agent can create databases, publish QStash messages, query Vector indexes, and more straight from the shell. See the [CLI page](/agent-resources/cli) for credentials and command details. +The combined `upstash` skill includes the full `upstash` CLI command reference, so your agent can create databases, publish QStash messages, query Vector indexes, and more straight from the shell. See the [CLI page](/agent-resources/cli) for credentials and command details. diff --git a/introduction.mdx b/introduction.mdx index 4c6eaa27f..5b7a89121 100644 --- a/introduction.mdx +++ b/introduction.mdx @@ -11,7 +11,7 @@ import { Hero, PromptToolIcons, SectionHead, ProductGrid, UtilityGrid, Community
- Set up Upstash in my coding agent using the official Upstash instructions, and run the commands yourself instead of asking me to. If you are Claude Code, install the Upstash plugin — it bundles the Upstash skills (https://upstash.com/docs/agent-resources/skills) and the remote MCP server over OAuth — by running `claude plugin marketplace add upstash/skills` then `claude plugin install upstash@upstash`, and tell me to run `/reload-plugins`. If you are OpenAI Codex, install the same plugin with `codex plugin marketplace add upstash/skills` then `codex plugin add upstash@upstash`. For any other agent, install the skills with `npx -y skills add upstash/skills --global`, then add the remote MCP server https://mcp.upstash.com/mcp to your MCP config (it authenticates over OAuth on first use); see https://upstash.com/docs/agent-resources/clients for the exact location. When done, verify the skills and MCP server are installed and tell me whether a restart is needed. + Set up Upstash in my coding agent using the official Upstash instructions, and run the commands yourself instead of asking me to. Run `npx -y upstash setup --yes` with the flag for the agent you are (`--claude`, `--codex`, `--cursor`, `--gemini`, `--vscode`, `--copilot` or `--opencode`). It installs the Upstash plugin where your agent supports plugins, and otherwise adds the remote MCP server https://mcp.upstash.com/mcp plus the Upstash skills (https://upstash.com/docs/agent-resources/skills); the MCP server authenticates over OAuth on first use. If you are not one of those agents, install the skills with `npx -y skills add upstash/skills --global` and add the remote MCP server to your MCP config; see https://upstash.com/docs/agent-resources/clients for the exact location. When done, tell me what was installed and whether I need to restart or reload (in Claude Code, `/reload-plugins`).
diff --git a/llms-full.txt b/llms-full.txt index 581bc55a2..5bf300883 100644 --- a/llms-full.txt +++ b/llms-full.txt @@ -56,15 +56,36 @@ You can find the Github Repository [here](https://github.com/upstash/cli). # Installation ```bash -npm i -g @upstash/cli +npm i -g upstash ``` +Or run any command without installing, for example `npx upstash redis list`. + For agents, install the [Upstash Skill](/docs/agent-resources/skills) instead. It bundles Upstash docs with the `upstash` CLI so your agent can implement and debug against your resources without filling up its context window: ```bash npx skills add upstash/skills ``` +# Connect your AI agent + +`upstash setup` wires Upstash into the coding agents on your machine: + +```bash +npx upstash setup +``` + +In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. + +```bash +upstash setup --claude --cursor -y # pick agents, no prompts +upstash setup --project # this repo instead of your user config +upstash setup --mode mcp # MCP + skill everywhere, no plugins +upstash setup --dry-run # show what would change +``` + +Rerunning `setup` updates what it installed. + # Free Redis without an account If you are an AI agent and need a Redis DB to use or experiment with, you don't need an Upstash account: @@ -1359,7 +1380,15 @@ Don't see your agent? See the [full list of agents](/docs/agent-resources/client # Quick start -Install the Upstash skill. It includes the `upstash` CLI reference, so this one step is enough for most workflows: +One command connects the coding agents on your machine to Upstash: + +```bash +npx upstash setup +``` + +It detects Claude Code, Codex, Cursor, Gemini CLI, VS Code, GitHub Copilot CLI, and OpenCode, and lets you pick which to set up. Agents with plugin support get the Upstash plugin (skills plus the remote MCP server); the others get the remote MCP server in their config and the Upstash skill. The MCP server signs in with OAuth on first use. See the [CLI page](/docs/agent-resources/cli#connect-your-ai-agent) for flags. + +To set things up by hand instead, install the Upstash skill. It includes the `upstash` CLI reference, so this one step is enough for most workflows: ```bash npx skills add upstash/skills @@ -1547,7 +1576,7 @@ Add `--global` (`-g`) to make the skills available in every project instead of j # Managing resources -The combined `upstash` skill includes the full `@upstash/cli` command reference, so your agent can create databases, publish QStash messages, query Vector indexes, and more straight from the shell. See the [CLI page](/docs/agent-resources/cli) for credentials and command details. +The combined `upstash` skill includes the full `upstash` CLI command reference, so your agent can create databases, publish QStash messages, query Vector indexes, and more straight from the shell. See the [CLI page](/docs/agent-resources/cli) for credentials and command details. # Disable Production Pack Source: https://upstash.com/docs/api-reference/qstash/disable-production-pack @@ -15224,7 +15253,7 @@ import { Hero, PromptToolIcons, SectionHead, ProductGrid, UtilityGrid, Community
- Set up Upstash in my coding agent using the official Upstash instructions, and run the commands yourself instead of asking me to. If you are Claude Code, install the Upstash plugin — it bundles the Upstash skills (https://upstash.com/docs/agent-resources/skills) and the remote MCP server over OAuth — by running `claude plugin marketplace add upstash/skills` then `claude plugin install upstash@upstash`, and tell me to run `/reload-plugins`. If you are OpenAI Codex, install the same plugin with `codex plugin marketplace add upstash/skills` then `codex plugin add upstash@upstash`. For any other agent, install the skills with `npx -y skills add upstash/skills --global`, then add the remote MCP server https://mcp.upstash.com/mcp to your MCP config (it authenticates over OAuth on first use); see https://upstash.com/docs/agent-resources/clients for the exact location. When done, verify the skills and MCP server are installed and tell me whether a restart is needed. + Set up Upstash in my coding agent using the official Upstash instructions, and run the commands yourself instead of asking me to. Run `npx -y upstash setup --yes` with the flag for the agent you are (`--claude`, `--codex`, `--cursor`, `--gemini`, `--vscode`, `--copilot` or `--opencode`). It installs the Upstash plugin where your agent supports plugins, and otherwise adds the remote MCP server https://mcp.upstash.com/mcp plus the Upstash skills (https://upstash.com/docs/agent-resources/skills); the MCP server authenticates over OAuth on first use. If you are not one of those agents, install the skills with `npx -y skills add upstash/skills --global` and add the remote MCP server to your MCP config; see https://upstash.com/docs/agent-resources/clients for the exact location. When done, tell me what was installed and whether I need to restart or reload (in Claude Code, `/reload-plugins`).
From 4718811efe485776abd4f2318b20cc88a5fded5a Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 5 Oct 2026 12:15:03 +0000 Subject: [PATCH 2/9] DX-3074: lead with `npx upstash`, which runs setup in a terminal AI Tools quick start and the CLI page show `npx upstash`; the CLI page notes that agents and scripts call `upstash setup` explicitly. Regenerated llms-full.txt. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01LWUubWwYWp1dZTK1S9Ek95 --- agent-resources/cli.mdx | 6 +++--- agent-resources/overview.mdx | 2 +- llms-full.txt | 8 ++++---- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/agent-resources/cli.mdx b/agent-resources/cli.mdx index 44d1a4420..3e8ea76fb 100644 --- a/agent-resources/cli.mdx +++ b/agent-resources/cli.mdx @@ -22,13 +22,13 @@ npx skills add upstash/skills # Connect your AI agent -`upstash setup` wires Upstash into the coding agents on your machine: +One command wires Upstash into the coding agents on your machine: ```bash -npx upstash setup +npx upstash ``` -In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. +Run with no arguments in a terminal, `upstash` starts `upstash setup`. From an agent or a script, call `upstash setup` explicitly; a bare `upstash` only prints the help there. In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. ```bash upstash setup --claude --cursor -y # pick agents, no prompts diff --git a/agent-resources/overview.mdx b/agent-resources/overview.mdx index 135b74c24..75f33b0ec 100644 --- a/agent-resources/overview.mdx +++ b/agent-resources/overview.mdx @@ -36,7 +36,7 @@ Don't see your agent? See the [full list of agents](/agent-resources/clients). One command connects the coding agents on your machine to Upstash: ```bash -npx upstash setup +npx upstash ``` It detects Claude Code, Codex, Cursor, Gemini CLI, VS Code, GitHub Copilot CLI, and OpenCode, and lets you pick which to set up. Agents with plugin support get the Upstash plugin (skills plus the remote MCP server); the others get the remote MCP server in their config and the Upstash skill. The MCP server signs in with OAuth on first use. See the [CLI page](/agent-resources/cli#connect-your-ai-agent) for flags. diff --git a/llms-full.txt b/llms-full.txt index 5bf300883..32c99bf3f 100644 --- a/llms-full.txt +++ b/llms-full.txt @@ -69,13 +69,13 @@ npx skills add upstash/skills # Connect your AI agent -`upstash setup` wires Upstash into the coding agents on your machine: +One command wires Upstash into the coding agents on your machine: ```bash -npx upstash setup +npx upstash ``` -In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. +Run with no arguments in a terminal, `upstash` starts `upstash setup`. From an agent or a script, call `upstash setup` explicitly; a bare `upstash` only prints the help there. In a terminal it asks where to install (all projects or just this one) and which agents to set up, with detected agents pre-selected, then shows the plan before changing anything. Claude Code, Codex, Cursor, and Gemini CLI get the Upstash plugin (skills plus the remote MCP server). VS Code, GitHub Copilot CLI, and OpenCode get the remote MCP server in their config plus the Upstash skill. The MCP server signs in with OAuth on first use; setup never writes an API key into an agent's config. ```bash upstash setup --claude --cursor -y # pick agents, no prompts @@ -1383,7 +1383,7 @@ Don't see your agent? See the [full list of agents](/docs/agent-resources/client One command connects the coding agents on your machine to Upstash: ```bash -npx upstash setup +npx upstash ``` It detects Claude Code, Codex, Cursor, Gemini CLI, VS Code, GitHub Copilot CLI, and OpenCode, and lets you pick which to set up. Agents with plugin support get the Upstash plugin (skills plus the remote MCP server); the others get the remote MCP server in their config and the Upstash skill. The MCP server signs in with OAuth on first use. See the [CLI page](/docs/agent-resources/cli#connect-your-ai-agent) for flags. From f7cd5436accac2075800c178bb237b8084bcda2e Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 6 Oct 2026 08:58:17 +0000 Subject: [PATCH 3/9] DX-3074: docs home leads with `npx upstash`; product cards show it Home hero: the first action copies `npx upstash` (replacing the Agent Setup link); the setup prompt stays as the second option. Product pages: the AgentSetup card now says `npx upstash` installs the Upstash MCP server and skills, linking to both pages. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01LWUubWwYWp1dZTK1S9Ek95 --- snippets/agent-setup.jsx | 48 ++++++++++++++++----------------- snippets/landing.jsx | 57 ++++++++++++++++++++++++++++++---------- style.css | 11 ++++++++ 3 files changed, 77 insertions(+), 39 deletions(-) diff --git a/snippets/agent-setup.jsx b/snippets/agent-setup.jsx index a12aab3bb..2fac1b831 100644 --- a/snippets/agent-setup.jsx +++ b/snippets/agent-setup.jsx @@ -1,28 +1,26 @@ -// "Set up your coding agent" card for product landing pages. Links to /agent-resources/overview. -// Usage: +// "Building with an AI coding agent?" card for product landing pages: `npx upstash` +// installs the Upstash MCP server and skills, with links to both pages. +// Usage: (`product` is accepted for existing pages; the command covers every product). // Everything lives inside the exported component: Mintlify does not expose non-exported top-level consts to snippet components. -export const AgentSetup = ({ product }) => { - const desc = product - ? `Connect the Upstash MCP server and the ${product} skill to Claude Code, Cursor, Codex, and other agents.` - : "Connect the Upstash MCP server and skills to Claude Code, Cursor, Codex, and other agents."; - - return ( - -
- -
-
-
Building with an AI coding agent?
-
{desc}
+export const AgentSetup = () => ( + +); diff --git a/snippets/landing.jsx b/snippets/landing.jsx index 5ee0b2103..cd09c1401 100644 --- a/snippets/landing.jsx +++ b/snippets/landing.jsx @@ -1,18 +1,47 @@ -export const Hero = ({ children }) => ( -
-

Build with Upstash

-

- Serverless data, messaging, and AI infrastructure for developers. Scale to - zero, pay per request. -

-
- - Agent Setup - - {children} +// The first action copies `npx upstash`, which (run in a terminal) connects the +// reader's coding agents to Upstash. The setup prompt passed as children is the +// second option, for pasting into an agent instead. +export const Hero = ({ children }) => { + const command = "npx upstash"; + const [copied, setCopied] = useState(false); + const copy = () => { + navigator.clipboard?.writeText(command).then(() => { + setCopied(true); + setTimeout(() => setCopied(false), 1500); + }); + }; + + return ( +
+

Build with Upstash

+

+ Serverless data, messaging, and AI infrastructure for developers. Scale to + zero, pay per request. +

+
+ + {children} +
-
-); + ); +}; export const PromptToolIcons = () => (