Upstash MCP Server

What is Upstash MCP Server?

The Upstash MCP server lets your agent manage and debug your Upstash resources directly, across Redis, QStash, Workflow, and Upstash Box. It is designed for users of MCP-compatible clients who want to interact with their Upstash account through natural language prompts.

How to use Upstash MCP Server?

Install by running npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY in any MCP-compatible client, or use one-click install buttons for Cursor and VS Code. Optionally pass --box-api-key or the UPSTASH_BOX_API_KEY environment variable for Upstash Box tools, and --debug for verbose logging.

Key features of Upstash MCP Server

• Manage Redis databases, backups, and throughput metrics
• Inspect and retry QStash and Workflow executions
• Read and manage Dead Letter Queue (DLQ) entries
• Pause or modify schedules throwing errors
• Spin up and snapshot Upstash Box environments
• Readonly API key support disables all write tools
• Debug mode writes all internal events to stderr

Use cases of Upstash MCP Server

• Create, list, and manage Redis databases with natural language prompts
• Debug failing QStash webhooks and Workflow runs from chat
• Perform bulk operations like cloning Box snapshots across GitHub issues
• Inspect throughput spikes or error patterns in your Upstash account

FAQ from Upstash MCP Server

What Upstash products does the server support?

Redis, QStash, Workflow, and Upstash Box.

Do I need an API key, and how do I get one?

Yes. You need your Upstash account email and an API key. Create one at Upstash Console → Account → API Keys.

Does the server support readonly API keys?

Yes. When a readonly API key is used, every tool that would modify state is automatically disabled. Your agent can still read and query your account but cannot make changes. Upstash Box tools are not available with a readonly key.

What runtime and transport does the server use?

The server runs as a stdio-based MCP server executed via npx. It requires Node.js (or Bun) and communicates through standard input/output with the MCP client.

What telemetry does the server send?

The server sends anonymous diagnostic info with each request: the MCP server SDK version, your runtime version (Node, Bun, etc.), and basic platform info (OS and architecture). No account data, tool arguments, or results are included.