Skip to main content
Glama
farhankaz

Redis MCP Server

by farhankaz

Related Servers

Alternatives to Redis MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Redis. Connect to any Redis instance and execute queries through AI assistants.
      30
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides comprehensive Redis database operations supporting all major data types (strings, lists, sets, hashes, sorted sets) with full CRUD functionality through natural language commands.
      9
      18 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to perform comprehensive Redis database operations including managing strings, hashes, lists, sets, sorted sets, TTL management, and data backup/restore. Supports secure connections and provides batch operations for efficient Redis interaction through natural language.
      34
      14 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Provides access to Redis databases. This server enables LLMs to interact with Redis key-value stores through a set of standardized tools.
      166 npm
      30
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables key-value storage operations using multiple backends (memory, filesystem, redis, MongoDB, HTTP) via MCP tools like get, set, and list.
      22 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to manage and search data in Redis using natural language. Supports hashes, lists, sets, sorted sets, streams, JSON, and vector search.
      44
      MIT

    TDQS

    B3/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting different Redis data types and operations, with minimal overlap. However, 'get' and 'set' for strings versus 'hget' and 'hmset' for hashes follow similar patterns but are differentiated by the 'h' prefix, which could cause minor confusion for agents unfamiliar with Redis naming conventions.

    Naming Consistency5/5

    The tool names are highly consistent, following Redis command conventions with lowercase, concise verb-based names (e.g., 'get', 'set', 'del', 'sadd', 'zadd'). All tools adhere to this pattern without mixing styles, making them predictable and easy to interpret.

    Tool Count5/5

    With 13 tools, this server is well-scoped for Redis operations, covering key data types (strings, hashes, sets, sorted sets) and essential commands. The count is appropriate, providing a focused set without being overwhelming or too sparse for the domain.

    Completeness4/5

    The tool set offers strong coverage for core Redis operations, including CRUD-like actions for multiple data types and scanning. Minor gaps exist, such as missing list operations (e.g., 'lpush', 'lrange') and transaction commands, but agents can still handle many common workflows effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues