Log inSubmit server
MCP Server logo

MCP Server

by upstash

Manage and debug Upstash Redis, QStash, Workflow, and Box resources from MCP-compatible clients.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server-165": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/mcp-server@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.

npx -y @upstash/mcp-server@latest

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

The upstash/mcp-server MCP server connects MCP-compatible agents to the Upstash Developer API for managing and debugging Redis, QStash, Workflow, and Upstash Box resources. It runs as a local stdio process through npx and authenticates with an Upstash email address and API key. Readonly keys automatically remove state-changing tools while retaining read and query access. Use it when an agent needs to inspect Upstash resources, review logs, manage databases, or operate supported platform resources.

Use cases

  • Manage Upstash Redis databases from an AI client
  • Inspect QStash logs and schedules
  • Review and retry Workflow executions
  • Create temporary Redis databases for experiments
  • Debug Upstash resources with a readonly API key

Key features

  • Redis resource management and queries
  • QStash logs and schedules
  • Workflow logs and retries
  • Upstash Box resource access
  • Readonly-key tool filtering
  • Temporary Redis database creation

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

8/8 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 8d ago via OSV.dev · @upstash/mcp-server@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars60Stargazers on the source repository.
npm downloads8kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How MCP Server works

What upstash/mcp-server MCP server does

The upstash/mcp-server MCP server gives an AI agent access to Upstash account resources through the Upstash Developer API. It covers four product areas named in the project documentation: Redis, QStash, Workflow, and Upstash Box. The available operations include resource management and debugging rather than only database queries.

For Redis, the server can provide account and database access, including querying Redis resources. QStash support includes access to logs and schedules. Workflow support includes workflow logs and actions such as retrying workflows. The documentation also references operations for creating databases and deleting backups. Upstash Box tools are included for accounts using an API key with the required permissions.

A separate redis_database_start_free tool can start a temporary Redis database without an Upstash account. The resulting database expires after 72 hours unless claimed with an Upstash account.

How it works

The upstash/mcp-server MCP server uses the standard local stdio transport. An MCP client launches the package with npx, passing the account email and API key as command-line arguments. The agent then discovers and calls the server's tools through the client.

A readonly API key changes the exposed tool set at startup. Operations that modify state are disabled, including creating databases, deleting backups, and retrying workflows. Read operations remain available, including Redis queries and access to QStash schedules, QStash logs, and Workflow logs. Upstash Box tools are not available when the server uses a readonly key.

The temporary Redis provisioning tool accepts a user_agent value so the request can identify the agent. When calling the corresponding HTTP endpoint directly instead of using MCP, the request also needs a fresh UUIDv4 Idempotency-Key and a User-Agent header.

Setup and configuration

Create an Upstash API key from the Account → API Keys area of the Upstash Console. Start the server with:

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

Add that command as a local or stdio MCP server in the client of your choice. The README provides configurations for Claude Code, Cursor, Windsurf, OpenAI Codex, and VS Code. VS Code can prompt for the email and API key and store the key in secret storage. Codex users may need to raise startup_timeout_sec to 40 if the default startup timeout is insufficient.

Tools and capabilities

  • Manage Upstash Redis resources and query Redis databases.
  • Inspect QStash logs and schedules.
  • Inspect Workflow logs and retry workflows when permitted.
  • Create databases and delete backups with a non-readonly key.
  • Access Upstash Box tools with a writable API key.
  • Start a no-signup, temporary Redis database with redis_database_start_free.

Limitations and notes

The upstash/mcp-server MCP server requires an Upstash email address and API key for normal operation. Its capabilities depend on the key's permissions: readonly keys cannot change state, and they cannot use Upstash Box tools. The free Redis database created through the no-account flow expires after 72 hours unless it is claimed through an Upstash account.

The project documentation recommends considering the Upstash Skill with @upstash/cli for most workflows instead of running the MCP server. That recommendation does not change the server's MCP compatibility or its stdio setup.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCP Server

upstash/mcp-server is an MCP server that connects AI clients to the Upstash Developer API. Its main tools manage and debug Redis, QStash, Workflow, and Upstash Box resources, including Redis queries, QStash logs and schedules, Workflow logs, and permitted resource-changing operations.

Install it by adding a local stdio server that runs `npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY`. The README also provides setup instructions for Claude Code, Cursor, Windsurf, OpenAI Codex, and VS Code.

Yes, upstash/mcp-server works with Cursor as a local MCP server. Add its `npx` command and the `--email` and `--api-key` arguments to Cursor's MCP settings or `~/.cursor/mcp.json`.

Yes, readonly API keys are supported. The server disables tools that modify state, such as database creation, backup deletion, and workflow retries, while retaining read access to Redis, QStash logs and schedules, and Workflow logs. Upstash Box tools are unavailable with readonly keys.

Related MCP servers

All in Databases All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcp-server-165?style=directory)](https://allmcps.com/mcp/mcp-server-165)
HTML Embed
<a href="https://allmcps.com/mcp/mcp-server-165"><img src="https://allmcps.com/api/badge/mcp-server-165?style=directory" alt="MCP Server on AllMCPs" /></a>