What it does & operational scope
Redis MCP Server gives agents an operational window into Redis instances, clusters, and RediSearch indexes via stdio transport. Maintained by Redis Inc., it connects over standard TCP to expose commands for retrieving key values, inspecting TTL expirations, reading stream entries, and querying hash maps without raw redis-cli terminal access.
Redis MCP Server is an open-source Model Context Protocol server developed by Redis Inc. under BSD-3-Clause that connects AI assistants to Redis key-value structures, streams, and RediSearch vector indexes.
Your AI coding agent requires live access to Redis tools and resources over local IPC or streamable transport.
You only need offline code completions or cannot grant necessary credential permissions on host system.
Client configuration & wire setup
Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.
claude_desktop_config.json{ "mcpServers": { "redis": { "command": "uvx", "args": ["--from", "git+https://github.com/redis/mcp-redis.git", "redis-mcp-server", "--url", "redis://localhost:6379/0"] } }}Exposed tool endpoints & primitives
Discovered MCP Tools
4 Tools Readyget_key🟢 Read-Only (Safe)Retrieve string value associated with a specified Redis key
set_key🟡 State MutationStore string or numeric value under key with optional TTL expiration
hgetall🟢 Read-Only (Safe)Fetch all field-value pairs from a target Redis hash table
keys🟢 Read-Only (Safe)Scan Redis database keyspace using pattern matching expressions
Scopes, secret storage, and sandbox boundaries
Configure Redis ACL rules: ACL SETUSER agent_user on >agent_secret ~cache:* +get +mget -flushdb -keys. Restrict command execution.Real conversational prompts & expected tool calls
💬 "Find latest technical updates for Redis MCP Server from the last 7 days"get_key({ query: "Redis MCP Server updates", limit: 5 })Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.
💬 "Inspect status and health boundaries for Redis MCP Server"get_key_status({ verbose: true })Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.
Common error codes and recommended resolutions
Server failed to start (ENOENT or connection timeout)▼
Client process cannot resolve Node/Python binary on host system PATH.
Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").
Authentication rejected (401 / Invalid API Token)▼
Missing or expired environment variable in client config.
Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.
Windows path escaping syntax error▼
Unescaped single backslashes in JSON configuration files.
Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").
Technical trade-offs and operational friction
+ Provides sub-millisecond inspection of hot in-memory key state and queues.
+ Eliminates raw terminal access to redis-cli in developer environments.
+ Direct integration with RediSearch indexes and Redis streams.
− Unbounded keyspace queries like KEYS * on multi-gigabyte production clusters block Redis single-threaded event loops, spiking overall database latency.
− Lacks structured schema enforcement, so erratic agent writes can corrupt serialized cache payloads and invalidate downstream application state.
Side-by-side rival comparisons
Compare Redis MCP Server vs PostgreSQL MCP Server across transport protocols and exposed tools.
Enter ShowdownJSON-RPC 2.0 wire trace & receipts
Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
1{2 "jsonrpc": "2.0",3 "id": 7,4 "method": "tools/call",5 "params": {6 "name": "get",7 "arguments": {8 "key": "session:user_102:state"9 }10 }11}
