High performance Redis MCP Server using node-redis
High performance Redis MCP Server using node-redis. Exposed over MCP by the easy mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A lightweight Model Context Protocol (MCP) server that lets AI assistants inspect and operate Redis through a structured tool interface.
Everything the assistant can do here goes through one of these:
redis_manual — Return the built-in manual. Use this first when you are unsure how to use Redis tools or need help diagnosing an operation errorredis_command — Execute a Redis command with argumentsredis_ping — Ping Redis and optionally echo a messageredis_info — Return server information, optionally for one sectionredis_dbsize — Return the number of keys in the selected databaseredis_time — Return Redis server timeredis_client_list — Return connected client informationredis_config_get — Read Redis configuration valuesredis_command_list — List commands supported by the Redis serverredis_lrange — Read a list rangeredis_smembers — Read all set membersredis_zrange — Read a sorted set range, optionally with scoresInstallation goes through your MCP client rather than a global install: point it at easy-redis-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 7 environment variables: REDIS_HOST, REDIS_PORT, REDIS_DB, REDIS_USERNAME, REDIS_PWD, REDIS_MODE, REDIS_SSL_CA_PATH. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Easy's toolset — redis_manual, redis_command, redis_ping and 11 more — is a fair guide to whether it matches your workflow. It is maintained by chenkumi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Easy's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| redis_manual | Return the built-in manual. Use this first when you are unsure how to use Redis tools or need help diagnosing an operation error |
| redis_command | Execute a Redis command with arguments |
| redis_ping | Ping Redis and optionally echo a message |
| redis_info | Return server information, optionally for one section |
| redis_dbsize | Return the number of keys in the selected database |
| redis_time | Return Redis server time |
| redis_client_list | Return connected client information |
| redis_config_get | Read Redis configuration values |
| redis_command_list | List commands supported by the Redis server |
| redis_lrange | Read a list range |
| redis_smembers | Read all set members |
| redis_zrange | Read a sorted set range, optionally with scores |
| redis_xrange | Read stream entries by ID range |
| redis_xadd | Append a stream entry, only registered in readwrite mode |
{
"mcpServers": {
"easy-redis-mcp": {
"command": "npx",
"args": ["-y", "easy-redis-mcp"],
"env": {
"REDIS_HOST": "localhost",
"REDIS_PORT": "6379",
"REDIS_DB": "0",
"REDIS_USERNAME": "default",
"REDIS_PWD": "YOUR PASSWORD",
"REDIS_MODE": "readwrite"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| REDIS_HOST | Endpoint or connection string the server talks to. | Optional |
| REDIS_PORT | Configuration value read at startup. | Optional |
| REDIS_DB | Configuration value read at startup. | Optional |
| REDIS_USERNAME | Configuration value read at startup. | Optional |
| REDIS_PWD | Configuration value read at startup. | Optional |
| REDIS_MODE | Configuration value read at startup. | Optional |
| REDIS_SSL_CA_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.