Upstash

Q: Does Upstash need an API key?

Yes. It reads UPSTASH_EMAIL, UPSTASH_API_KEY and UPSTASH_BOX_API_KEY from its environment, and UPSTASH_API_KEY and UPSTASH_BOX_API_KEY are secrets. Put the value in your client's config on your own machine, never in a shared file.

listing.by

Manage Upstash Redis, QStash, Workflow and Box resources and debug them from your agent through the Upstash Developer API.

state.local.longlisting.badge.runs_withstate.key.long

listing.install

listing.local.explain

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

listing.local.needs listing.local.note

UPSTASH_EMAIL Email address of your Upstash account.
UPSTASH_API_KEY listing.env.secret Upstash Developer API key (create one at https://console.upstash.com/account/api).
UPSTASH_BOX_API_KEY listing.env.secret listing.env.optional Upstash Box API key for Box-related tools.

act.add_to

listing.about

Connects your agent to the Upstash Developer API so it can manage and debug Upstash resources across Redis, QStash, Workflow and Upstash Box. It can read and query your account, including Redis databases, QStash logs, schedules and Workflow logs, and it can make changes such as creating databases or deleting backups. A free Redis database can also be started without an account through the redis_database_start_free tool.

It runs locally over stdio with npx. You need your Upstash account email and a Developer API key from the Upstash console. Readonly API keys are supported: the server then disables every tool that modifies state. An optional Box API key enables Box tools.

listing.can

Manage Upstash Redis databases and backups
Inspect QStash logs and schedules
Read Workflow logs and retry workflows
Work with Upstash Box resources
Start a free temporary Redis database without signup
Run in read-only mode with a readonly API key

listing.tools

listing.notools.key

listing.prompts

List my Upstash Redis databases and show their usage stats.
Create a new Upstash Redis database in eu-west-1.
Show recent QStash logs for failed messages.
Start a free temporary Redis database for testing.

listing.setup.h

listing.setup.local

Claude Code

Run this in a terminal, in your project folder:

claude mcp add --transport stdio upstash --env "UPSTASH_EMAIL=<YOUR_UPSTASH_EMAIL>" --env "UPSTASH_API_KEY=<YOUR_UPSTASH_API_KEY>" --env "UPSTASH_BOX_API_KEY=<YOUR_UPSTASH_BOX_API_KEY>" -- npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY

Start Claude Code and type /mcp. upstash should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:

claude_desktop_config.json

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest",
        "--email",
        "YOUR_EMAIL",
        "--api-key",
        "YOUR_API_KEY"
      ],
      "env": {
        "UPSTASH_EMAIL": "<YOUR_UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "<YOUR_UPSTASH_API_KEY>",
        "UPSTASH_BOX_API_KEY": "<YOUR_UPSTASH_BOX_API_KEY>"
      }
    }
  }
}

Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Add to Cursor a11y.new_tab

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest",
        "--email",
        "YOUR_EMAIL",
        "--api-key",
        "YOUR_API_KEY"
      ],
      "env": {
        "UPSTASH_EMAIL": "<YOUR_UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "<YOUR_UPSTASH_API_KEY>",
        "UPSTASH_BOX_API_KEY": "<YOUR_UPSTASH_BOX_API_KEY>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json

{
  "servers": {
    "upstash": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest",
        "--email",
        "YOUR_EMAIL",
        "--api-key",
        "YOUR_API_KEY"
      ],
      "env": {
        "UPSTASH_EMAIL": "<YOUR_UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "${input:upstash-api-key}",
        "UPSTASH_BOX_API_KEY": "${input:upstash-box-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "upstash-api-key",
      "description": "UPSTASH_API_KEY",
      "password": true
    },
    {
      "type": "promptString",
      "id": "upstash-box-api-key",
      "description": "UPSTASH_BOX_API_KEY",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):

mcp_config.json

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest",
        "--email",
        "YOUR_EMAIL",
        "--api-key",
        "YOUR_API_KEY"
      ],
      "env": {
        "UPSTASH_EMAIL": "<YOUR_UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "<YOUR_UPSTASH_API_KEY>",
        "UPSTASH_BOX_API_KEY": "<YOUR_UPSTASH_BOX_API_KEY>"
      }
    }
  }
}

Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add upstash --env "UPSTASH_EMAIL=<YOUR_UPSTASH_EMAIL>" --env "UPSTASH_API_KEY=<YOUR_UPSTASH_API_KEY>" --env "UPSTASH_BOX_API_KEY=<YOUR_UPSTASH_BOX_API_KEY>" -- npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY

Or edit ~/.codex/config.toml directly:

config.toml

[mcp_servers.upstash]
command = "npx"
args = ["-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY"]
env = { UPSTASH_EMAIL = "<YOUR_UPSTASH_EMAIL>", UPSTASH_API_KEY = "<YOUR_UPSTASH_API_KEY>", UPSTASH_BOX_API_KEY = "<YOUR_UPSTASH_BOX_API_KEY>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "UPSTASH_EMAIL=<YOUR_UPSTASH_EMAIL>" -e "UPSTASH_API_KEY=<YOUR_UPSTASH_API_KEY>" -e "UPSTASH_BOX_API_KEY=<YOUR_UPSTASH_BOX_API_KEY>" upstash npx -- -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest",
        "--email",
        "YOUR_EMAIL",
        "--api-key",
        "YOUR_API_KEY"
      ],
      "env": {
        "UPSTASH_EMAIL": "<YOUR_UPSTASH_EMAIL>",
        "UPSTASH_API_KEY": "<YOUR_UPSTASH_API_KEY>",
        "UPSTASH_BOX_API_KEY": "<YOUR_UPSTASH_BOX_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

listing.faq

Can I paste mcp.tc/i/upstash into my MCP client?

No. Upstash runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY.

Does Upstash need an API key?

Yes. It reads UPSTASH_EMAIL, UPSTASH_API_KEY and UPSTASH_BOX_API_KEY from its environment, and UPSTASH_API_KEY and UPSTASH_BOX_API_KEY are secrets. Put the value in your client's config on your own machine, never in a shared file.

Is Upstash a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY, which needs Node.js.

What can Upstash do?

You can manage Upstash Redis databases and backups, inspect QStash logs and schedules and read Workflow logs and retry workflows.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Who wrote this page?

mcp.tc's robot read Upstash's public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can't confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

listing.em.h

listing.em.lead_local listing.em.how

listing.em.badge

Markdown

[![Upstash on mcp.tc](https://mcp.tc/i/upstash/badge.svg)](https://mcp.tc/i/upstash)

HTML

<a href="https://mcp.tc/i/upstash"><img src="https://mcp.tc/i/upstash/badge.svg" alt="Upstash on mcp.tc" height="20"></a>

listing.em.badge_note

listing.em.widget

HTML

<script src="https://mcp.tc/w/upstash.js" async></script>

listing.em.widget_note

iframe

HTML

<iframe src="https://mcp.tc/embed/upstash" title="Upstash on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

listing.em.iframe_note

JSON

listing.em.json_local

https://mcp.tc/i/upstash.json

listing.em.fields

listing.disclaimer_checked

listing.install

listing.share.h

listing.about

listing.can

listing.tools

listing.prompts

listing.setup.h

Claude Code

Claude Desktop

Cursor

VS Code

Devin Desktop

Codex

Gemini CLI

Any client

listing.faq

listing.em.h

listing.em.badge

listing.em.widget

iframe

JSON

listing.related

Context7vf.sr

dbt

Neo4jvf.sr

Convex

Pineconevf.sr

Qdrant