Upstash MCP Server

Upstash's official MCP server: manage and debug Redis, QStash, Workflow, and Upstash Box using natural language from Claude Code, Cursor, and more.

Description

The Upstash MCP Server is the official Model Context Protocol connection to your own Upstash account, letting AI agents manage and debug Redis databases, QStash message queues, Workflow runs, and Upstash Box containers directly. Instead of switching between the Upstash console, terminal, and AI assistant, a coding agent can create databases, search logs, retry failed workflows, or spin up sandbox containers — all through natural language chat in Claude Code, Cursor, Codex, or other MCP-capable clients.

What the server does

Per the provider, for Redis you can create new databases in a specific region, list existing databases sorted by memory usage, have the schema of stored data explained, find keys matching certain patterns along with their contents, create backups and clear databases, and analyze throughput spikes over recent days. For QStash and Workflow, an agent can search logs for failure causes, find and retry failed workflow runs from the last 24 hours, summarize the dead-letter queue by error type, or pause scheduled tasks. For Upstash Box, you can spin up sandbox containers, clone repositories and run tests directly inside them, create and duplicate snapshots, or identify failure causes in container logs.

Free test database without sign-up

One tool is aimed directly at AI agents: via redis_database_start_free or a direct POST request to https://upstash.com/start-redis, a free, temporary Redis database can be started without registration or an API key. The response contains credentials and a quickstart guide in markdown; the database expires after 72 hours but can be permanently claimed via an Upstash account. Per the provider, this is especially useful for agents that need scratch storage on the fly.

Credentials and permissions

Before setup, you need your account email and an API key from the Upstash console. The server supports read-only API keys: when started with one, it automatically disables every state-changing tool, such as creating databases, deleting backups, or retrying workflows — the agent can then only read and query the account, not modify it. Accessing Upstash Box additionally requires a separate Box API key, which can be wired into the server configuration to avoid repeated manual input.

Supported clients

Per the provider, the server works with any MCP-compatible client over stdio, with officially documented setup instructions for Claude Code, Cursor, Devin Desktop, OpenCode, OpenAI Codex, Visual Studio Code, Google Antigravity, Claude Desktop, Zed, DeepSeek Harness, and Gemini CLI. For clients without dedicated instructions, a generic stdio configuration using the command npx -y @upstash/mcp-server@latest is enough.

Provider's note: consider the skill instead of the MCP server

Upstash itself recommends in the repository that, for most workflows, installing the Upstash skill and letting the agent drive the upstash command line through it is preferable to running the MCP server continuously. The MCP server is best suited when the agent needs direct, interactive tool access to live resources — for example, searching logs in real time or retrying workflows mid-conversation.

Telemetry and privacy

Per the provider, the server sends anonymous diagnostic data to Upstash: SDK version, runtime version, and basic platform information such as OS and architecture. Account data, tool arguments, or results are not transmitted. Anyone who doesn't want even that can disable telemetry with the --disable-telemetry flag.

License and cost

The repository is licensed under MIT. The MCP server itself doesn't add separate costs; billing runs entirely through your existing Upstash plan for the managed resources.

Who benefits most

The server is especially useful for development teams already building on Upstash services like Redis or QStash: troubleshooting without switching consoles, automatically creating test databases for new projects, or quickly debugging failed workflows right from the editor. Per the provider, anyone working with just a single Redis database is often better served by the leaner, dedicated Redis MCP server.

Requirements

An Upstash account (account email + API key from Console → Account → API Keys) plus an MCP-capable client with stdio support (Node.js/npx available). Upstash Box tools additionally require a separate Box API key.

Installation instructions

The Upstash MCP Server runs locally via npx and connects directly to the Upstash API; no separate server infrastructure is needed.

Preparing credentials

Two things are needed before setup: your Upstash account email and an API key, created in the Upstash console under Account → API Keys. For a first test, a read-only key is recommended — the server then automatically disables all tools that could modify data.

Step 1: Setting it up in Claude Code

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

Step 2: Setting it up in Codex

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

Step 3: Setting it up in other clients

Any MCP client with stdio support can be configured with the same base command:

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

Officially documented step-by-step instructions are also available for Cursor, Devin Desktop, OpenCode, VS Code, Google Antigravity, Claude Desktop, Zed, DeepSeek Harness, and Gemini CLI.

Preparing Upstash Box access

Tools around Upstash Box additionally require a separate Box API key. Instead of entering it manually every session, it can be wired permanently into the server configuration — either as an additional CLI flag or as an environment variable.

Free Redis database to try it out

Anyone who just wants to quickly experiment with Redis doesn't even need an account for that: a simple prompt like "start a temporary Redis database for me" calls redis_database_start_free in the background and returns credentials for a free database valid for 72 hours.

Considering the skill instead of the MCP server

For pure command-line tasks, Upstash itself recommends installing the Upstash skill instead of the MCP server, letting the agent drive the upstash CLI. The MCP server is most worthwhile when the agent needs to interact live with running resources, for example searching logs or retrying workflows mid-conversation.

Common setup issues

If the connection fails with an authentication error, it's usually a mistyped API key or an email address that doesn't match the Upstash account. Both values can be viewed again anytime in the Upstash console under Account, and regenerated if needed.

Step 4: Verifying the setup

After starting, test with a harmless, read-only task, such as "List my Redis databases" or "Show me the details for database X." Only swap the read-only test key for one with full access once this works reliably and write actions are actually needed.

Starting with a read-only key by default is a small habit that catches most accidental misconfigurations before they touch live data.

Source: github.com/upstash/mcp-server and upstash.com/docs/agent-resources/mcp, checked on 2026-09-06.

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

Authentication

Account email plus an API key from the Upstash console, passed as CLI flags on startup. Read-only API keys are supported and automatically disable all state-changing tools. Upstash Box requires an additional Box API key.

Required access permissions

The server acts with the permissions of the API key used. With a read-only key, the agent can only read and query, not modify; with full access it can also create databases, delete backups, and retry workflows.

Transmitted or stored data

Requests run locally through the npx process and communicate directly with the Upstash API. Per the provider, the server sends anonymous telemetry (SDK version, runtime version, OS/architecture) to Upstash, but no account data, tool arguments, or results. Telemetry can be disabled via --disable-telemetry.

Security risks

With a full API key, an agent can delete databases, remove backups, or modify production data. Upstash recommends using read-only API keys where possible and granting full access only once a clear need is demonstrated.

License and costs

License
MIT
Cost
free

The MCP server itself is provided without a separate license or usage fee. It requires an existing Upstash account; usage of the managed resources (Redis, QStash, Workflow, Box) runs through the regular Upstash plan. Purchasing an Upstash plan happens exclusively on upstash.com, not through Skill Road.

Alternatives

Not recorded yet.

At a glance

Provider
Upstash
Status
Official server
Deployment
Local
Current version
Not recorded yet.
GitHub stars
61
Last reviewed
06.09.2026

Repository and documentation

Categories

Supported clients