Skip to main content
Glama
YawLabs

redis-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to redis-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-redis-allowlist

      TeaBambooNGU
      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

    • redis-guard-mcp

      BerkantACUN
      A
      license
      A
      quality
      C
      maintenance
      Enables safe, read-only interaction with Redis databases via cursor-based tools for retrieving keys, hashes, lists, sets, and sorted sets, backed by ACL DRYRUN-verified privilege checks.
      13
      MIT

    • mcp-server-redis

      atengk
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables LLMs to safely explore and operate Redis instances, with read-only keyspace inspection, multi-structure data access, memory and big-key analysis, slow query diagnostics, and optional opt-in write operations.
      105 PyPI
      MIT

    • redis-mcp-server

      lm203688
      A
      license
      A
      quality
      D
      maintenance
      Enables AI to safely view and operate Redis databases with read-only mode by default and support for key operations.
      11
      MIT

    • signalk-mcp-ops

      eriksnijder
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides read-only MCP access to Signal K vessel data for diagnostics, letting clients retrieve allowed self values, discover paths, list plugins, and report capability/security policy without write or control commands.
      160 npm
      MIT

    • mcp-opensearch

      dmayan-ss
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for exploring and searching OpenSearch clusters, enabling log analysis, index exploration, and query execution.
      8
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a largely distinct purpose: reads, metadata, enumeration, generic commands, and health checks. The only mild overlap is between redis_health and redis_advisor, both covering memory and TTL concerns, but their descriptions clearly differentiate a snapshot from a lint-style rollout.

    Naming Consistency4/5

    All tools share the redis_ prefix and snake_case, which provides a strong visual pattern. However, the second part mixes actions (get, scan), objects (key_info, slowlog), and abstract nouns (health, advisor, command), so it is not a uniform verb_noun convention.

    Tool Count5/5

    Seven tools is a well-scoped size for a Redis server. Each tool covers a meaningful capability—reading, scanning, inspecting, commanding, health, advice, and slow-log diagnostics—without unnecessary redundancy.

    Completeness4/5

    Read, scan, metadata inspection, health, and monitoring are all well covered, and redis_command fills gaps for write operations and non-typed commands. The main limitation is that there are no dedicated write tools, but redis_command makes those operations reachable, so agents are not blocked.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources