Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Upstash MCP Server for Claude

Connect Claude to Upstash — create and manage serverless Redis databases, inspect QStash message logs, and debug Workflow runs — with Upstash's official Model Context Protocol server.

by Upstash·added 2026-06-17·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Tools can create and delete databases and modify resources; a read-only API key automatically disables state-modifying tools.
  • Database deletion and configuration changes affect live resources; review before running them through Claude.

Privacy notes

  • Resource metadata, metrics, and message logs enter the MCP client context and the model's prompt.
  • The Upstash email and API key are credentials — keep them in the client config or environment, never in shared repositories.

Prerequisites

  • An Upstash account.
  • Your Upstash account email and a management API key (Upstash Console -> Account -> API Keys).
  • Node.js (npx) and an MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
5 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "<your-email>", "--api-key", "<your-api-key>"]
    }
  }
}

About this resource

Overview

The Upstash MCP Server is Upstash's official Model Context Protocol server. It lets Claude manage and debug Upstash resources in natural language — creating and managing serverless Redis databases, inspecting QStash message logs, diagnosing Workflow runs, and operating Upstash Box. It runs over stdio via npx @upstash/mcp-server and is licensed under MIT.

Key capabilities

  • Redis — create and manage serverless databases, backups, and performance metrics.
  • QStash — inspect webhook/message logs and manage messages.
  • Workflow — monitor runs, diagnose failures, and retry operations.
  • Upstash Box — provision VMs, manage snapshots, and inspect logs.

A read-only API key automatically disables the state-modifying tools.

How it compares

MCP server Focus Hosting Notable
Upstash MCP Serverless Redis, QStash, Workflow Fully managed (Upstash Cloud) Manage + debug resources, not raw key access
Redis MCP Redis data operations Self-host or Redis Cloud Direct key/value and data-structure access

Use the Upstash server to provision and debug Upstash resources; pair it with a Redis data server when you also need direct key-level operations.

Installation

Claude Code

claude mcp add upstash -- npx -y @upstash/mcp-server@latest --email <your-email> --api-key <your-api-key>

Claude Desktop

{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "<your-email>", "--api-key", "<your-api-key>"]
    }
  }
}

Requirements

  • An Upstash account, account email, and a management API key.
  • Node.js (npx) and an MCP client (Claude Code or Claude Desktop).

Security

  • Use a read-only API key when Claude only needs to inspect resources — it disables modifying tools.
  • Database deletion and config changes affect live resources; review destructive actions first.
  • Treat the Upstash email and API key as credentials.

Source Verification Notes

Verified on 2026-06-17:

  • The official repository github.com/upstash/mcp-server (MIT) documents the @upstash/mcp-server package, the --email/--api-key arguments, stdio transport, the read-only key behavior, and the Redis, QStash, Workflow, and Box capabilities above.
  • Upstash's documentation describes the underlying serverless Redis, QStash, and Workflow products.
  • Claude Code's MCP documentation describes the connector setup pattern used here.
#upstash#redis#serverless#qstash#database

Source citations

Add this badge to your README

Show that Upstash MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/upstash-mcp-server.svg)](https://heyclau.de/entry/mcp/upstash-mcp-server)

How it compares

Upstash MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldUpstash MCP Server for Claude

Connect Claude to Upstash — create and manage serverless Redis databases, inspect QStash message logs, and debug Workflow runs — with Upstash's official Model Context Protocol server.

Open dossier 		Meilisearch MCP Server for Claude

Connect Claude to Meilisearch — manage indexes, add and search documents, tune settings, and monitor tasks — with Meilisearch's official Model Context Protocol server.

Open dossier 		DigitalOcean MCP Server for Claude

Connect Claude to DigitalOcean — manage Apps, Droplets, managed Databases, Kubernetes, Container Registry, networking, and Functions — with DigitalOcean's official Model Context Protocol server.

Open dossier 		Elasticsearch MCP Server for Claude

Connect Claude to your Elasticsearch cluster — search indices, inspect mappings, run ES|QL, and check shard health — with Elastic's official Model Context Protocol server.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorUpstashMeilisearchDigitalOceanElastic
Added2026-06-172026-06-172026-06-172026-06-17
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Tools can create and delete databases and modify resources; a read-only API key automatically disables state-modifying tools. Database deletion and configuration changes affect live resources; review before running them through Claude.✓Tools create and delete indexes and documents and rotate API keys — scope the key and confirm destructive actions. Settings and index deletes change live search behavior; review before running them through Claude.✓Tools can create, update, restart, and delete live infrastructure (Apps, Droplets, Databases) — scope the API token and select only the --services you need. Destructive actions (delete, rollback) act on production resources; confirm before running them through Claude.✓Search, ES|QL, and shard tools run live read queries against the configured cluster; a broad or expensive query can add load. Scope the Elasticsearch API key to least privilege (read-only on the indices Claude should see) before connecting.
Privacy notes✓Resource metadata, metrics, and message logs enter the MCP client context and the model's prompt. The Upstash email and API key are credentials — keep them in the client config or environment, never in shared repositories.✓Indexed documents and search results enter the MCP client context and the model's prompt. MEILI_HTTP_ADDR and MEILI_MASTER_KEY are secrets — keep them in the client config or environment.✓Resource metadata, logs, and metrics enter the MCP client context and the model's prompt. The DIGITALOCEAN_API_TOKEN is a secret — store it in the client config or environment, never in shared repositories.✓Index data, field mappings, and query results enter the MCP client context and the model's prompt. ES_URL and ES_API_KEY are secrets — store them in the client config or environment, never in shared repositories.
Prerequisites
  • An Upstash account.
  • Your Upstash account email and a management API key (Upstash Console -> Account -> API Keys).
  • Node.js (npx) and an MCP client such as Claude Code or Claude Desktop.
  • A reachable Meilisearch instance URL (MEILI_HTTP_ADDR).
  • A Meilisearch master or API key (MEILI_MASTER_KEY) when your instance requires authentication.
  • uv (uvx) or pip to run meilisearch-mcp, or Docker (getmeili/meilisearch-mcp).
  • An MCP client such as Claude Code or Claude Desktop.
  • A DigitalOcean account.
  • A DigitalOcean API token (DIGITALOCEAN_API_TOKEN) with the scopes for the services you enable.
  • Node.js (npx) to run @digitalocean/mcp, or use the hosted remote endpoint.
  • An MCP client such as Claude Code or Claude Desktop.
  • Docker installed (the server is distributed as the docker.elastic.co/mcp/elasticsearch image).
  • An Elasticsearch cluster URL (ES_URL) you can reach.
  • An Elasticsearch API key (ES_API_KEY) or username/password (ES_USERNAME + ES_PASSWORD).
  • An MCP client such as Claude Code or Claude Desktop.
Install
claude mcp add upstash -- npx -y @upstash/mcp-server@latest --email <your-email> --api-key <your-api-key>
claude mcp add meilisearch -e MEILI_HTTP_ADDR=<your-meili-url> -e MEILI_MASTER_KEY=<your-key> -- uvx -n meilisearch-mcp
claude mcp add digitalocean -e DIGITALOCEAN_API_TOKEN=<your-token> -- npx -y @digitalocean/mcp --services apps,droplets,databases
claude mcp add elasticsearch -- docker run -i --rm -e ES_URL=<your-cluster-url> -e ES_API_KEY=<your-api-key> docker.elastic.co/mcp/elasticsearch stdio
Config
{
  "mcpServers": {
    "upstash": {
      "command": "npx",
      "args": ["-y", "@upstash/mcp-server@latest", "--email", "<your-email>", "--api-key", "<your-api-key>"]
    }
  }
}
{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"],
      "env": {
        "MEILI_HTTP_ADDR": "<your-meili-url>",
        "MEILI_MASTER_KEY": "<your-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "digitalocean": {
      "command": "npx",
      "args": ["-y", "@digitalocean/mcp", "--services", "apps,droplets,databases"],
      "env": {
        "DIGITALOCEAN_API_TOKEN": "<your-token>"
      }
    }
  }
}
{
  "mcpServers": {
    "elasticsearch-mcp-server": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "ES_URL", "-e", "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch", "stdio"
      ],
      "env": {
        "ES_URL": "<elasticsearch-cluster-url>",
        "ES_API_KEY": "<elasticsearch-api-key>"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.