Upstash MCP Server – Manage Redis and Workflows
The Upstash MCP Server is the official Upstash Model Context Protocol server for letting MCP-compatible agents work with Upstash account resources. It exposes tools for Redis, QStash, Workflow, and Upstash Box workflows, with write tools automatically disabled when a read-only Upstash API key is used.
Overview
The Upstash MCP Server connects an MCP-compatible AI agent to an Upstash account. Upstash documents it as a way for an agent to manage and debug Upstash resources directly across Redis, QStash, Workflow, and Upstash Box. It is useful when an agent needs live operational context from Upstash rather than relying on static documentation or manually copied console output.
What the MCP server enables
Through the stdio MCP server, an agent can perform account-aware Upstash tasks such as listing Redis databases, checking database memory or throughput, creating backups, reviewing QStash logs, investigating failed Workflow runs, retrying failed workflow executions, inspecting dead-letter queues, and pausing schedules that are failing. Upstash also documents Box-related prompts such as creating a Box, running tests, taking snapshots, creating copies, and inspecting Box startup logs.
The server supports both read and write workflows. A key operational safeguard is that read-only Upstash API keys are supported: when the server is started with a read-only key, it automatically disables tools that would modify state, while still allowing the agent to read and query account information.
When to use it
Use this MCP server when an AI agent needs to assist with Upstash operations, debugging, or incident investigation. Practical examples include finding why a webhook is repeatedly failing in QStash, summarizing failed workflow runs for a user, checking whether Redis throughput spiked during a time window, or comparing Redis databases by memory usage. It is also suitable for developer workflows where an agent needs to provision or inspect Upstash resources from an MCP client.
Connection and authentication
Upstash documents the MCP server as a local stdio server started with npx -y @upstash/mcp-server@latest. The required credentials are an Upstash account email and an Upstash API key, passed with --email and --api-key. For Upstash Box capabilities, a Box API key can be supplied either with --box-api-key or through the UPSTASH_BOX_API_KEY environment variable.
Key considerations
Store the Upstash API key in your MCP client's secret storage when possible instead of hard-coding it in shared configuration files. Use a read-only Upstash API key for investigation or reporting workflows where the agent should not create, delete, retry, pause, or otherwise change resources. Upstash also documents optional debugging with --debug and telemetry opt-out with --disable-telemetry; telemetry is described as anonymous diagnostic information that excludes account data, tool arguments, and results.
Supported Transports
stdio
Command: npx
Args:
-y@upstash/mcp-server@latest--email${UPSTASH_EMAIL}--api-key${UPSTASH_API_KEY}
Frequently Asked Questions
- When should an AI agent use the Upstash MCP Server?
- Use it when an agent needs to inspect, manage, or debug live Upstash resources, such as Redis databases, QStash delivery logs, Workflow runs, schedules, dead-letter queues, or Upstash Box environments.
- What does this MCP server add to an AI agent's capabilities?
- It gives the agent MCP tools backed by an authenticated Upstash account, so the agent can work with current Redis, QStash, Workflow, and Box state instead of relying on pasted logs or general model knowledge.
- What can the AI agent access or manage through this server?
- Upstash documents use cases for listing and inspecting Redis databases, checking throughput, creating backups, reviewing QStash logs, finding and retrying failed Workflow runs, summarizing dead-letter queues, pausing failing schedules, and working with Upstash Box when a Box API key is provided.
- How is authentication configured for this MCP server?
- The stdio command requires an Upstash account email and Upstash API key passed with the --email and --api-key arguments. Optional Box operations can use a Box API key supplied with --box-api-key or the UPSTASH_BOX_API_KEY environment variable. A read-only Upstash API key can be used to prevent state-changing tools from being enabled.
- Which transport should be used for this MCP server?
- Use the local stdio transport documented by Upstash. The official setup starts the server with npx and @upstash/mcp-server@latest; no hosted Streamable HTTP or SSE endpoint is documented for this Upstash MCP server.