MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations
MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations. That is what the mcp redis diagnostics mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
mcp-redis-diagnostics on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 7 tools. What each one is for:
analyze_memory — The analyze_memory tool exposed by this serveranalyze_slowlog — The analyze_slowlog tool exposed by this serveranalyze_clients — The analyze_clients tool exposed by this serveranalyze_keyspace — Analyze Redis keyspace distribution and cache effectivenessanalyze_latency — The analyze_latency tool exposed by this serveranalyze_config — Analyze Redis configuration for security and reliability risksanalyze_performance — Comprehensive health assessment — runs all analyzers and produces a unified reportConfiguration is passed through the environment: REDIS_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Redis Diagnostics's toolset — analyze_memory, analyze_slowlog, analyze_clients and 4 more — is a fair guide to whether it matches your workflow. It is maintained by dmitriusan; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| analyze_memory | The analyze_memory tool exposed by this server. |
| analyze_slowlog | The analyze_slowlog tool exposed by this server. |
| analyze_clients | The analyze_clients tool exposed by this server. |
| analyze_keyspace | Analyze Redis keyspace distribution and cache effectiveness. |
| analyze_latency | The analyze_latency tool exposed by this server. |
| analyze_config | Analyze Redis configuration for security and reliability risks. |
| analyze_performance | Comprehensive health assessment — runs all analyzers and produces a unified report. |
{
"mcpServers": {
"redis-diagnostics": {
"command": "npx",
"args": ["-y", "mcp-redis-diagnostics"],
"env": {
"REDIS_URL": "redis://localhost:6379"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| REDIS_URL | Endpoint or connection string the server talks to. | Yes |
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.