Production-grade Postgres MCP with index advice, EXPLAIN, and health checks.
Redis
Inspect keys, run commands, and debug Redis from an AI agent.
Quick answer
What it does
Connects to a Redis server and exposes key inspection, value retrieval for all core data types, TTL inspection, and a curated set of read-only debug commands.
Best for
- Cache inspection
- Session debugging
- Queue depth checks
- TTL audits
Not for
- Production-wide KEYS scans
- Write operations from an LLM
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "redis": { "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export REDIS_URL=redis://default:pass@localhost:6379/0 claude mcp add redis -- uvx --from "git+https://github.com/redis/mcp-redis" redis-mcpRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "redis": { "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "redis": { "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "redis": { "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "redis": { "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ], "env": { "REDIS_URL": "${REDIS_URL}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.redis] command = "uvx" args = [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp", ] env = { REDIS_URL = "${REDIS_URL}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "redis": { "command": { "path": "uvx", "args": [ "--from", "\"git+https://github.com/redis/mcp-redis\"", "redis-mcp" ] }, "env": { "REDIS_URL": "${REDIS_URL}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneRedis doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
REDIS_URLin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
| Tool | Description | Args | Side effects |
|---|---|---|---|
scan_keys | Iterate keys matching a pattern using SCAN. | pattern: string | Read |
get_string | GET a string value. | key: string | Read |
hgetall | Return all fields and values of a hash. | key: string | Read |
lrange | Return a range of list elements. | key: string, start: number, stop: number | Read |
ttl | Return the TTL of a key. | key: string | Read |
Security & scope
- Access scope
- Read-only
- Sandbox
- Connects to a Redis instance via REDIS_URL. Read-only mode disables write commands at the tool layer. Use a Redis user with read-only ACL as defence in depth.
- Gotchas
- KEYS is replaced by SCAN intentionally — do not enable a custom passthrough tool that re-introduces KEYS.
- TLS is required for managed providers (Upstash, Redis Cloud). Use rediss:// in the URL.
- Pub/Sub subscriptions are not exposed — agents holding open subscriptions is a footgun.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. databases work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-databases
Compare Redis MCP vs [Postgres MCP Pro MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/redis - top-mcps.com listing for Postgres MCP Pro
Install the Redis MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/redis (fetch https://top-mcps.com/mcp/redis.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (REDIS_URL) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Databases MCPs
Other tools in the same category worth evaluating.
Compared with Redis
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Databases? See all Databases MCPs →
