Supabase
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
Description from the maker (original English)
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, UPSTASH_REDIS_TCP_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"redis": {
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp"
],
"env": {
"UPSTASH_REDIS_REST_URL": "your-value",
"UPSTASH_REDIS_REST_TOKEN": "your-value",
"UPSTASH_REDIS_TCP_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add redis --env UPSTASH_REDIS_REST_URL=your-value --env UPSTASH_REDIS_REST_TOKEN=your-value --env UPSTASH_REDIS_TCP_URL=your-value -- npx -y @upstash/redis-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"redis": {
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp"
],
"env": {
"UPSTASH_REDIS_REST_URL": "your-value",
"UPSTASH_REDIS_REST_TOKEN": "your-value",
"UPSTASH_REDIS_TCP_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"redis": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp"
],
"env": {
"UPSTASH_REDIS_REST_URL": "your-value",
"UPSTASH_REDIS_REST_TOKEN": "your-value",
"UPSTASH_REDIS_TCP_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
UPSTASH_REDIS_REST_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account upstash, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: UPSTASH_REDIS_REST_TOKEN, UPSTASH_REDIS_TCP_URL
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Supabase, MongoDB MCP Server, Elasticsearch MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Supabase’s official server lets AI create tables, query data and review project settings in your Supabase database.
MongoDB Model Context Protocol Server
MCP server for interacting with Elasticsearch
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Lightweight MCP server for Redis with only two tools:
One server can hold multiple named databases. Configuration is pure environment variables and CLI flags.
Claude Code
Run this in your terminal. See the Claude Code MCP docs for more.
claude mcp add upstash-redis \
-e UPSTASH_REDIS_REST_URL=https:// .upstash.io \ -e UPSTASH_REDIS_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.
{
"mcpServers": { "upstash-redis": { "command": "npx", "args": ["-y", "@upstash/redis-mcp"], "env": { "UPSTASH_REDIS_REST_URL": "https:// .upstash.io", "UPSTASH_REDIS_REST_TOKEN": " " } } } }
VS Code
Add to .vscode/mcp.json (per-project) or your user mcp settings. See the VS Code MCP docs.
{
"servers": { "upstash-redis": { "command": "npx", "args": ["-y", "@upstash/redis-mcp"], "env": { "UPSTASH_REDIS_REST_URL": "https:// .upstash.io", "UPSTASH_REDIS_REST_TOKEN": " " } } } }
Codex
Add to ~/.codex/config.toml (or a project-level .codex/config.toml). See the Codex MCP docs.
[mcp_servers.upstash-redis]
command = "npx" args = ["-y", "@upstash/redis-mcp"] env = { UPSTASH_REDIS_REST_URL = "https:// .upstash.io", UPSTASH_REDIS_REST_TOKEN = " " }
OpenCode
Add to opencode.json (project) or ~/.config/opencode/opencode.json (global). See the OpenCode MCP docs.
{
"mcp": { "upstash-redis": { "type": "local", "command": ["npx", "-y", "@upstash/redis-mcp"], "environment": { "UPSTASH_REDIS_REST_URL": "https:// .upstash.io", "UPSTASH_REDIS_REST_TOKEN": " " } } } }
[!TIP]
Any MCP-compatible client works. If yours isn't listed, add a stdio server that runs
npx -y @upstash/redis-mcpwith the two env vars above.
redis_run_commandsRun 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.
{
"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_docsSearches 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.
{ "query": "SEARCH.AGGREGATE date histogram" }
Everything is set through environment variables and CLI flags; there are no config files.
| Transport | Environment | CLI |
|---|---|---|
| HTTP | UPSTASH_REDIS_REST_URL + UPSTASH_REDIS_REST_TOKEN | --rest-url --rest-token |
| TCP | UPSTASH_REDIS_TCP_URL (or REDIS_URL) | --url |
Give each database a name. The name becomes a selectable database value in redis_run_commands.
Environment: insert a segment:
UPSTASH_REDIS_PROD_REST_URL="https://prod-db.upstash.io"
UPSTASH_REDIS_PROD_REST_TOKEN=" " UPSTASH_REDIS_CACHE_TCP_URL="rediss://default: @cache-db.upstash.io:6379"
CLI: repeat --database to start each group:
npx -y @upstash/redis-mcp \
--database prod --rest-url https://prod-db.upstash.io --rest-token \ --database cache --url rediss://default: @cache-db.upstash.io:6379
[!NOTE]
Raw credentials per call. A
redis_run_commandscall may also passrest_url+rest_token(HTTP) orconnection_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.
| Flag | Env | Default | Purpose |
|---|---|---|---|
--transport | stdio | Server transport | |
--port | 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 |
HTTP/REST requests carry Upstash-Telemetry-{Sdk,Platform,Runtime} headers. Disable with --disable-telemetry or UPSTASH_DISABLE_TELEMETRY=true.
bun install
bun run build # emits dist/index.js cp .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.
bun install
bun run build bun test bun run lint
MIT © Upstash