--- title: "Upstash MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/upstash/ description: "Connects a local MCP client to Upstash resource inspection and account-authorized management tools." --- # Upstash MCP: review, setup & limitations · Undominated.ai > Connects a local MCP client to Upstash resource inspection and account-authorized management tools. [← Explore all mcp servers](/mcp-servers/) DATABASES AND SEARCH / Upstash # Upstash MCP Connects a local MCP client to Upstash resource inspection and account-authorized management tools. [See setup guidance ↓](#setup)[Original source ↗](https://github.com/upstash/mcp-server) SOURCE REVIEW Reviewed 2026-10-14 Evidence 6 linked sources Publisher Upstash Licence [MIT ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/LICENSE) Revision 9a0f49f9e241 [Read what was—and wasn’t—checked ↓](#review) “The Upstash MCP server lets your agent manage and debug your Upstash resources directly, across Redis, QStash, Workflow, and Upstash Box.” [Upstash · upstream description ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/README.md) Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Includes resource inspection across several Upstash products rather than only generic Redis commands. - The published package has read-only account-key detection and tool filtering; the review checks those boundaries against the package build as well as documentation. ### A good fit for - Inspect Redis/QStash/Workflow state with a read-only account key before diagnosing a failed delivery. - Review dead-letter and workflow-run evidence before separately approving retries or schedule changes. ### Weigh up before choosing - Use local stdio for the documented setup here. The reviewed HTTP listener has permissive CORS and no client authentication; do not expose it without an independently protected deployment. - Read-only filtering depends on account-key detection and per-tool annotations, not a sandbox. Begin with a read-only account key, omit the separate Box credential, and inspect exposed tools after updates. - The publisher recommends its skill and CLI for many workflows. Choose MCP when your host specifically benefits from tool integration. - Startup contacts Upstash and probes a deliberately nonexistent database with a DELETE request to detect read-only credentials; this is not an offline server. - Retrying workflows and changing schedules can repeat downstream side effects; a retry is not a harmless diagnostic operation. - --debug writes internal events to client-visible stderr logs. Review log contents before sharing a diagnostic extract. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - README.md, package.json, LICENSE, src/server.ts, src/index.ts and src/test-connection.ts at the npm-declared gitHead - Published npm 0.3.0 tarball integrity and dist/index.js transport, credential and tool-filtering sections - 2026-10-14 reread of retained pinned setup/configuration evidence for the specific operational details added in this batch. ### Our findings - The selected npm 0.3.0 command is matched to its registry-declared source revision. The downloaded tarball matches the registry SHA-512 integrity value. - The published code defaults to stdio, supports credential environment variables and --disable-telemetry, and filters by tool.readonly for detected read-only account keys. - A newer repository revision changes Box filtering, so its behavior was not substituted for the selected package version. - README explicitly separates account credentials from the optional Box key, documents retry/schedule workflows and sends debug output to stderr. Existing source-qualified read-only-detection caveats remain applicable. ### Not established by this review - No MCP server or upstream package was installed or run. - No authenticated account, client handshake, query, write operation or security test was performed. - No authenticated session, installation, permission bypass or package-to-source parity test was performed. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. [Upstream setup instructions ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/README.md) DOCUMENTED COMMAND npx -y @upstash/mcp-server@latest --email YOUR_EMAIL --api-key YOUR_API_KEY Copy command ↗ Copying does not execute this command. It may retrieve a newer version than the reviewed source. - Create a scoped account API key; begin with a read-only key and no Box credential. - The README's command uses @latest, which npm resolved to the reviewed 0.3.0 on 2026-10-13. Use @upstash/mcp-server@0.3.0 to stay on the reviewed build, and add --disable-telemetry to opt out of the diagnostic headers the README describes. - Prefer UPSTASH_EMAIL and UPSTASH_API_KEY in the client environment over the flags, so the key is not in shared configuration. Review the exposed tools before authorizing any write operation. ### Before you start - Node.js 20 or later and npm - An Upstash account with the necessary resource permissions ### Documented configuration example Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts. { "mcpServers": { "upstash": { "command": "npx", "args": [ "-y", "@upstash/mcp-server@latest", "--email", "YOUR_EMAIL", "--api-key", "YOUR_API_KEY" ] } } } Copy configuration ↗ ### Compatibility stdio MCP clients ### Implementation TypeScript ### Transports stdio ### Account-scoped MCP integration - Query account resources, logs and data using the supplied account key - A writable account key enables resource creation, updates and deletion; a Box key independently enables Box operations ### Cost model MIT-licensed server; Upstash resource consumption and agent usage follow their separate service terms. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - [Official setup and capabilities ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/README.md) Checked 2026-10-14 https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/README.md Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review, configExample - [Licence at reviewed source revision ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/LICENSE) Checked 2026-10-07 https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/LICENSE Supports: license, access.cost - [Server initialization and tool filtering ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/server.ts) Checked 2026-10-07 https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/server.ts Supports: review, limitations, access - [CLI transport and authentication handling ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/index.ts) Checked 2026-10-07 https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/index.ts Supports: install, limitations, review - [Published npm version metadata ↗](https://registry.npmjs.org/@upstash%2Fmcp-server/0.3.0) Checked 2026-10-07 https://registry.npmjs.org/@upstash%2Fmcp-server/0.3.0 Supports: install - [Account-key detection on startup ↗](https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/test-connection.ts) Checked 2026-10-07 https://github.com/upstash/mcp-server/blob/9a0f49f9e241d604b0820251eb5b47e268dea5bd/src/test-connection.ts Supports: review, limitations, access KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Redis Cloud API MCP Server ↗ Manages a Redis Cloud account through the Redis Cloud API from an MCP client: account and payment-method lookup, Pro and Essential subscriptions, plans, regions and task tracking.](/mcp-servers/redis-cloud-api/)[### Upstash Redis MCP ↗ Minimal two-tool Upstash server that runs Redis commands over REST or TCP and searches Redis docs, holding multiple named databases.](/mcp-servers/upstash-redis/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/) ## Continue your investigation - [Inspect resource evidence](/tools/) - [Choose a host](/agents/) - [Inspect reusable workflows](/skills/) - [Use Undominated data](/api/)