Redis Mcp

io.github.upstashPublished by GitHub account upstashv0.1.1Updated Oct 24, 2026

Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.

VerifiedSTDIODesktop onlyDatabases Knowledge & Memory

Server details

Identifier: io.github.upstash/redis-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account upstash for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.upstash%2Fredis-mcp.svg)](https://sourceweft.com/mcp/io.github.upstash%2Fredis-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant run Redis commands on Upstash Redis over HTTP or TCP and look up Upstash Redis documentation.

What you can do: Run arbitrary Redis commands (GET, SET, SCAN, ZADD, EVAL, SEARCH.* and more), as a pipeline or an atomic MULTI/EXEC transaction, against one or more named databases over HTTP/REST or TCP. Search the Upstash Redis documentation live and get the most relevant pages, including Upstash-specific SEARCH.* features.
When to use it: Use it when an assistant needs to read or modify data in an Upstash Redis database, or when you want in-context help with Redis commands and Upstash-specific search features without leaving the chat.
Requirements: Runs locally via npx (Node.js) as a stdio process. Needs an Upstash Redis database: UPSTASH_REDIS_REST_URL plus UPSTASH_REDIS_REST_TOKEN for HTTP, or UPSTASH_REDIS_TCP_URL (rediss://) for TCP; multiple databases can be named via environment variables or CLI flags. Doc search uses Context7's free tier and needs no key. Network access required.

Before you install

The REST token and TCP connection string are credentials; prefer environment variables or CLI flags over passing them inline per call, since inline values flow through the model's context. Commands can write, change or delete data; the read-only flag is best-effort, so use a server-side read-only REST token for real protection. HTTP requests send Upstash telemetry headers unless disabled.

Installation

In SourceWeft

Open Redis Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Upstash Redis MCP

[Add to Cursor]

Lightweight MCP server for Redis with only two tools:

🧪 redis_run_commands: run one or more Redis commands over HTTP/REST or TCP, as a pipeline or an atomic transaction.
📚 redis_search_docs: search the Redis docs using Context7 public api.

One server can hold multiple named databases. Configuration is pure environment variables and CLI flags.

🔌 Quickstart

Claude Code

Run this in your terminal. See the Claude Code MCP docs for more.

bash

claude mcp add upstash-redis \  -e UPSTASH_REDIS_REST_URL=https://<your-db>.upstash.io \  -e UPSTASH_REDIS_REST_TOKEN=<your-rest-token> \  -- npx -y @upstash/redis-mcp

claude mcp add upstash-redis \  -e UPSTASH_REDIS_REST_URL=https://<your-db>.upstash.io \  -e UPSTASH_REDIS_REST_TOKEN=<your-rest-token> \  -- npx -y @upstash/redis-mcp

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project), or go to Settings → MCP → Add new MCP server. See the Cursor MCP docs.

json

{  "mcpServers": {    "upstash-redis": {      "command": "npx",      "args": ["-y", "@upstash/redis-mcp"],      "env": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

{  "mcpServers": {    "upstash-redis": {      "command": "npx",      "args": ["-y", "@upstash/redis-mcp"],      "env": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

VS Code

Add to .vscode/mcp.json (per-project) or your user mcp settings. See the VS Code MCP docs.

json

{  "servers": {    "upstash-redis": {      "command": "npx",      "args": ["-y", "@upstash/redis-mcp"],      "env": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

{  "servers": {    "upstash-redis": {      "command": "npx",      "args": ["-y", "@upstash/redis-mcp"],      "env": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

Codex

Add to ~/.codex/config.toml (or a project-level .codex/config.toml). See the Codex MCP docs.

toml

[mcp_servers.upstash-redis]command = "npx"args = ["-y", "@upstash/redis-mcp"]env = { UPSTASH_REDIS_REST_URL = "https://<your-db>.upstash.io", UPSTASH_REDIS_REST_TOKEN = "<your-rest-token>" }

[mcp_servers.upstash-redis]command = "npx"args = ["-y", "@upstash/redis-mcp"]env = { UPSTASH_REDIS_REST_URL = "https://<your-db>.upstash.io", UPSTASH_REDIS_REST_TOKEN = "<your-rest-token>" }

OpenCode

Add to opencode.json (project) or ~/.config/opencode/opencode.json (global). See the OpenCode MCP docs.

json

{  "mcp": {    "upstash-redis": {      "type": "local",      "command": ["npx", "-y", "@upstash/redis-mcp"],      "environment": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

{  "mcp": {    "upstash-redis": {      "type": "local",      "command": ["npx", "-y", "@upstash/redis-mcp"],      "environment": {        "UPSTASH_REDIS_REST_URL": "https://<your-db>.upstash.io",        "UPSTASH_REDIS_REST_TOKEN": "<your-rest-token>"      }    }  }}

[!TIP] Any MCP-compatible client works. If yours isn't listed, add a stdio server that runs npx -y @upstash/redis-mcp with the two env vars above.

🧰 Tools

🧪 `redis_run_commands`

Run any Redis command: GET, SET, SCAN, ZADD, EVAL, the SEARCH.* family, and everything else. Each command is an array of args (numbers are accepted and coerced to strings). By default multiple commands run as a pipeline: each returns its own result/error, aligned to the input, and one failure doesn't abort the rest. Set transaction: true for an atomic MULTI/EXEC.

jsonc

{  "commands": [    ["SET", "visits", 0],    ["INCR", "visits"],    ["GET", "visits"],  ],  "transaction": false, // optional: true => atomic MULTI/EXEC  // "database": "prod"       // only when more than one database is configured  // raw credential overrides (optional):  // "rest_url", "rest_token" // HTTP  // "connection_string"      // TCP, rediss://}

{  "commands": [    ["SET", "visits", 0],    ["INCR", "visits"],    ["GET", "visits"],  ],  "transaction": false, // optional: true => atomic MULTI/EXEC  // "database": "prod"       // only when more than one database is configured  // raw credential overrides (optional):  // "rest_url", "rest_token" // HTTP  // "connection_string"      // TCP, rediss://}

The transport (HTTP vs TCP) is determined by how the target database is configured; the agent never picks it.

📚 `redis_search_docs`

Searches the Upstash Redis documentation live and returns the most relevant pages. Reach for it whenever you're unsure about a command or feature, especially Upstash-specific ones like the SEARCH.* full-text search family. It's powered by Context7's free tier, so no API key or extra setup is required.

⚙️ Configuration

Everything is set through environment variables and CLI flags; there are no config files.

Single database

Multiple databases

Give each database a name. The name becomes a selectable database value in redis_run_commands.

Environment: insert a <NAME> segment:

bash

UPSTASH_REDIS_PROD_REST_URL="https://prod-db.upstash.io"UPSTASH_REDIS_PROD_REST_TOKEN="<prod-rest-token>"UPSTASH_REDIS_CACHE_TCP_URL="rediss://default:<password>@cache-db.upstash.io:6379"

UPSTASH_REDIS_PROD_REST_URL="https://prod-db.upstash.io"UPSTASH_REDIS_PROD_REST_TOKEN="<prod-rest-token>"UPSTASH_REDIS_CACHE_TCP_URL="rediss://default:<password>@cache-db.upstash.io:6379"

CLI: repeat --database to start each group:

bash

npx -y @upstash/redis-mcp \  --database prod  --rest-url https://prod-db.upstash.io --rest-token <prod-rest-token> \  --database cache --url rediss://default:<password>@cache-db.upstash.io:6379

npx -y @upstash/redis-mcp \  --database prod  --rest-url https://prod-db.upstash.io --rest-token <prod-rest-token> \  --database cache --url rediss://default:<password>@cache-db.upstash.io:6379

[!NOTE] Raw credentials per call. A redis_run_commands call may also pass rest_url + rest_token (HTTP) or connection_string (TCP) inline; these override the registry and work even with no configured database. They flow through the model's context, so prefer env/CLI for anything sensitive.

Flags & options

Flag	Env	Default	Purpose
`--transport <stdio\|http>`		`stdio`	Server transport
`--port <n>`		`3000`	Port for the `http` transport
`--readonly`	`UPSTASH_REDIS_READONLY`	off	Best-effort: reject write commands on both transports. Server-side read-only REST tokens remain the robust option.
`--disable-telemetry`	`UPSTASH_DISABLE_TELEMETRY`	off	Stop sending `Upstash-Telemetry-*` headers on HTTP requests
`--debug`		off	Verbose logging to stderr + `redis-mcp-debug.log`

📡 Telemetry

HTTP/REST requests carry Upstash-Telemetry-{Sdk,Platform,Runtime} headers. Disable with --disable-telemetry or UPSTASH_DISABLE_TELEMETRY=true.

🏃 Run it locally

bash

bun installbun run build                 # emits dist/index.jscp .env.example .env          # add UPSTASH_REDIS_REST_URL + UPSTASH_REDIS_REST_TOKEN
node dist/index.js                          # stdio (what clients spawn)node dist/index.js --transport http --port 3000   # HTTP: endpoint /mcp, health /ping

bun installbun run build                 # emits dist/index.jscp .env.example .env          # add UPSTASH_REDIS_REST_URL + UPSTASH_REDIS_REST_TOKEN
node dist/index.js                          # stdio (what clients spawn)node dist/index.js --transport http --port 3000   # HTTP: endpoint /mcp, health /ping

The server auto-loads .env. To point a client at your local build, swap npx -y @upstash/redis-mcp in any Quickstart config for node /absolute/path/to/redis-mcp/dist/index.js.

🛠️ Development

📄 License

MIT © Upstash

Source: README.md at commit 9bbfcfa

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

Transport	Environment	CLI
HTTP	`UPSTASH_REDIS_REST_URL` + `UPSTASH_REDIS_REST_TOKEN`	`--rest-url <url> --rest-token <token>`
TCP	`UPSTASH_REDIS_TCP_URL` (or `REDIS_URL`)	`--url <rediss://…>`

Redis Mcp

Overview

Installation

In SourceWeft

Other MCP clients

README

Upstash Redis MCP

🔌 Quickstart

🧰 Tools

🧪 redis_run_commands

📚 redis_search_docs

⚙️ Configuration

Single database

Multiple databases

Flags & options

📡 Telemetry

🏃 Run it locally

🛠️ Development

📄 License

Tools

Version history

Score

🧪 `redis_run_commands`

📚 `redis_search_docs`