Data · Local MCP server
Redis MCP
Run Redis commands and look up Upstash Redis Search docs against Upstash Redis over HTTP or TCP.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.upstash/redis-mcp- Version
- 0.1.1
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-08
- Updated
- 2026-07-08
- Publisher
- upstash (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/upstash) · how
- Listed under
- Redis MCP servers
- Repository
- github.com/upstash/redis-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @upstash/redis-mcp | 0.1.1 | stdio |
How to connect Redis MCP
Redis MCP runs locally from a Node.js package published to the npm registry: @upstash/redis-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @upstash/redis-mcp@0.1.1. It reads these environment variables: UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN (secret) and UPSTASH_REDIS_TCP_URL (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"redis-mcp": {
"command": "npx",
"args": [
"-y",
"@upstash/redis-mcp@0.1.1"
],
"env": {
"UPSTASH_REDIS_REST_URL": "<value>",
"UPSTASH_REDIS_REST_TOKEN": "<secret>",
"UPSTASH_REDIS_TCP_URL": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from upstash (GitHub)
| Server | Runs |
|---|---|
| upstash MCP-SERVERManage Upstash databases and resources through the Upstash Developer API. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Recipe SignalSearch and compare attributed recipe records through a public read-only remote MCP endpoint. | Remote · HTTPLive check: ✓ handshake |
| RecordantPatent-pending diagnostic + decisions-ledger engine with operator briefs and an MCP console. | Local · stdio |
| Red StringRevenue research and pipeline tools for agencies: scouting, contact intel, ABM, cadences, briefs. | Remote · HTTPLive check: sign-in required |
| RedirectBossManage hosts, redirects, SSL, and traffic analytics from Claude and other AI assistants. | Remote · HTTPLive check: sign-in required |
| redm-mcpRedM / RDR3 docs MCP server: native lookups, semantic search, VORP, RSGCore, oxmysql. | Remote · HTTPLive check: sign-in required |
| Redmine MCP ConnectorStdio MCP server wrapping the Redmine REST API: issues, projects, users, time, wiki, versions. | Local · stdio |
| Redmine MCP ServerRedmine for AI agents: issues, projects, wiki, attachments, time entries and release analytics. | Local · stdio |
| Redmine MCP ServerMCP server that lets AI assistants manage Redmine issues, projects, wikis, and time tracking. | Local · stdio |