Skip to main content
Glama
minivv

Redis MCP Server

by minivv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Redis MCP Server

No user-submitted related servers found.

    Related Servers

    • Redis MCP Server by redis

      Redis MCP Serverofficial

      redis
      A
      license
      B
      quality
      B
      maintenance
      The official Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis.
      53
      626
      MIT
    • Upstash MCP Server by upstash

      Upstash MCP Serverofficial

      upstash
      A
      license
      Not graded
      quality
      B
      maintenance
      Model Context Protocol (MCP) is a new, standardized protocol for managing context between large language models (LLMs) and external systems. In this repository, we provide an installer as well as an MCP Server for Upstash Developer API's.
      2,076 npm
      60
      MIT
    • Upstash Redis MCP by upstash

      Upstash Redis MCPofficial

      upstash
      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.
      91 npm
      MIT

    • wredis-mcp

      wisrovi
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI agents to design and deploy WRedis/Redis-backed services using expert patterns, architecture scaffolding, and a unified CLI.
      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

    C2.6/5.0

    Scored across 30 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is overlap between get_key_info and specific getters (get_string, get_hash, etc.) as well as between execute_command and run_redis_query. This could cause an agent to select the wrong tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores. The verbs appropriately reflect Redis command conventions (add for sets, set for strings/hashes, push for lists). Very consistent.

    Tool Count2/5

    With 30 tools, the server is over-scoped. While each tool corresponds to a specific Redis operation, there is redundancy (e.g., get_key_info vs get_string) and the count exceeds 25, which is considered too many for a coherent set.

    Completeness3/5

    The tool set covers basic Redis operations for major data types and connection management, but lacks commonly used operations like INCR, EXISTS, APPEND, and advanced data structures. However, the presence of execute_command allows agents to fill gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources