Skip to main content
Glama
antonio-mello-ai

mcp-redis-monitor

Related Servers

Alternatives to mcp-redis-monitor

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Lightweight MCP server for Redis that allows running any Redis command and searching Redis documentation. Supports multiple named databases with HTTP/REST or TCP transport.
      87 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets an agent inspect and operate Redis-backed job queues, supporting Asynq and BullMQ backends with per-state counts, job details, and state transitions.
      6
      13 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Read-only Redis MCP server with a configurable command allowlist for safe production diagnostics, enabling exact read-only subcommands like CLIENT LIST and SLOWLOG GET.
      5
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A lightweight npm MCP server for deep Redis diagnostics, offering tools for memory, slowlog, clients, keyspace, latency, and config analysis with AI-powered recommendations.
      8
      50 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A safe, connection-efficient Redis MCP server that provides tools for reading and managing Redis data, with safeguards like confirmation requirements for destructive operations.
      70 npm
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCPWatch: observability for MCP servers. One line instruments any Python MCP server (FastMCP and the low-level Server) and tracks per-tool latency (p50/p95/p99), error rates, silent failures (empty/null returns and isError), and call volume. REST API, CLI, and alert hooks. MIT, no config required.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct monitoring aspect: Celery queues, connected clients, key counts by database, queue depths in a specific DB, and server info. No overlapping purposes.

    Naming Consistency5/5

    All tool names follow a consistent 'get_' prefix with descriptive snake_case nouns (e.g., get_celery_queue_status, get_connected_clients).

    Tool Count5/5

    Five tools is well-scoped for a Redis monitor, covering key monitoring areas without being too few or excessive.

    Completeness4/5

    Covers essential monitoring: server info, clients, key counts, and queue depths. Minor gaps like slowlog or replication are acceptable for a focused utility.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive