Registry / database / mcp-redis-diagnostics

mcp-redis-diagnostics

JSON →
library0.1.14jsnpmunverified

MCP server for Redis diagnostics — analyze memory usage, slowlog, client connections, and keyspace health with AI-powered recommendations. Version 0.1.14, MIT license. Lightweight npm package (no Docker/SaaS required) offering 7 diagnostic tools: analyze_memory, analyze_slowlog, analyze_clients, analyze_keyspace, analyze_latency, analyze_config, analyze_performance. Install via npx, requires Node >=20.0.0. Differentiates from CRUD-only Redis MCP servers and enterprise-focused tools by providing deep diagnostics as a zero-setup package. Pro tier available for HTML/PDF report generation.

npm install mcp-redis-diagnostics
INSTALL
IMPORT
SIG · MCP-REDIS-DIAGNOST
M
mcp-redis-diagnostics
databasejavascriptv0.1.14
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

default
import server from 'mcp-redis-diagnostics'
const server = require('mcp-redis-diagnostics')
ESM-only; CommonJS require will fail in Node >=20
startServer
import { startServer } from 'mcp-redis-diagnostics'
Named export for programmatic usage; not documented in README but available in source
RedisDiagnosticsServer
import { RedisDiagnosticsServer } from 'mcp-redis-diagnostics'
const RedisDiagnosticsServer = require('mcp-redis-diagnostics').RedisDiagnosticsServer
Class export for extending; ESM only

Run the MCP Redis Diagnostics server via npx or programmatically with ESM import. Sets REDIS_URL and starts the server.

// Run directly with npx (no install needed) // npx mcp-redis-diagnostics // Or programmatic usage: import { startServer } from 'mcp-redis-diagnostics'; // Set Redis connection via environment or default to localhost process.env.REDIS_URL = process.env.REDIS_URL ?? 'redis://localhost:6379'; // Start the server (default port 3000) startServer().then(() => { console.log('MCP Redis Diagnostics server started'); }).catch((err: Error) => { console.error('Failed to start server:', err); process.exit(1); });
Debug
Known issues
breakingNode.js >=20 required; versions below 20 will fail with engine error
fix
Upgrade Node.js to version 20 or higher
affects: <20.0.0
gotchaDefault Redis connection is localhost:6379 without authentication; production deployments must set REDIS_URL with password
fix
Set REDIS_URL environment variable to redis://user:password@host:port
affects: >=0.1.0
gotchaThe analyze_latency tool requires the CONFIG SET latency-monitor-threshold 100 command on Redis side; otherwise no latency events will be captured
fix
Run CONFIG SET latency-monitor-threshold 100 on your Redis server before using analyze_latency
affects: >=0.1.0
deprecatedPro license key is currently a placeholder; generate_report tool may not work until Stripe integration is finalized
fix
Wait for official Pro tier release with working payment link
affects: >=0.1.0
Errors
Common errors & fixes
Error: Cannot find module 'mcp-redis-diagnostics'
Package not installed or running without npx; CJS require used in ESM-only package
fix
Use `npx mcp-redis-diagnostics` or import ESM style: `import { startServer } from 'mcp-redis-diagnostics'`
Connection refused: connect ECONNREFUSED 127.0.0.1:6379
Redis server not running on localhost:6379 or REDIS_URL not set to correct host
fix
Start Redis locally or set REDIS_URL environment variable to a valid Redis connection string (e.g., redis://user:password@host:port)
ERR wrong number of arguments for 'CONFIG' command
Issued CONFIG SET without proper parameters; or Redis version incompatible
fix
Ensure Redis version >= 2.6 and use correct command: CONFIG SET latency-monitor-threshold 100
Upgrade
Version history
0.1.14latest on npm
Audit
Dependencies
@modelcontextprotocol/sdkrequiredMCP server framework
ioredisrequiredRedis client for database connection and diagnostics queries
Agent activity
7 hits · last 30 days
node
6
Resources
mcp-redis-diagnostics — npm install mcp-redis-diagnostics · libregistry