Skip to main content
Glama
redis

Redis MCP Server

Official
by redis

rpush

Add a value to the end of a Redis list, with an optional expiration time.

Instructions

Push a value onto the right of a Redis list and optionally set an expiration time.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
valueYes
expireNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'rpush' tool. It connects to Redis, pushes a value onto the right of a list, optionally sets an expiration, and returns a success/error message.
    @mcp.tool()
    async def rpush(name: str, value: FieldT, expire: Optional[int] = None) -> str:
        """Push a value onto the right of a Redis list and optionally set an expiration time."""
        try:
            r = RedisConnectionManager.get_connection()
            r.rpush(name, value)
            if expire:
                r.expire(name, expire)
            return f"Value '{value}' pushed to the right of list '{name}'."
        except RedisError as e:
            return f"Error pushing value to list '{name}': {str(e)}"
  • The input schema for rpush is defined by the function signature (name: str, value: FieldT, expire: Optional[int]) via the @mcp.tool() decorator from FastMCP, which auto-generates the JSON schema. Return type is str.
    @mcp.tool()
    async def rpush(name: str, value: FieldT, expire: Optional[int] = None) -> str:
        """Push a value onto the right of a Redis list and optionally set an expiration time."""
        try:
            r = RedisConnectionManager.get_connection()
            r.rpush(name, value)
            if expire:
                r.expire(name, expire)
            return f"Value '{value}' pushed to the right of list '{name}'."
        except RedisError as e:
            return f"Error pushing value to list '{name}': {str(e)}"
  • Registration of the 'rpush' tool via the @mcp.tool() decorator on the FastMCP server instance (mcp) in src/common/server.py. The load_tools() function in src/common/server.py dynamically imports src.tools.list (and all modules in src/tools), which triggers the decorator registration.
    @mcp.tool()
  • RedisConnectionManager.get_connection() provides the Redis client instance used by the rpush handler to execute the RPUSH command.
    class RedisConnectionManager:
        _instance: Optional[Redis] = None
    
        @classmethod
        def get_connection(cls, decode_responses=True) -> Redis:
            if cls._instance is None:
                try:
                    # Create Entra ID credential provider if configured
                    credential_provider = None
                    if is_entraid_auth_enabled():
                        try:
                            credential_provider = create_credential_provider()
                        except EntraIDAuthenticationError as e:
                            _logger.error(
                                "Failed to create Entra ID credential provider: %s", e
                            )
                            raise
    
                    if REDIS_CFG["cluster_mode"]:
                        redis_class: Type[Union[Redis, RedisCluster]] = (
                            redis.cluster.RedisCluster
                        )
                        connection_params = {
                            "host": REDIS_CFG["host"],
                            "port": REDIS_CFG["port"],
                            "username": REDIS_CFG["username"],
                            "password": REDIS_CFG["password"],
                            "ssl": REDIS_CFG["ssl"],
                            "ssl_ca_path": REDIS_CFG["ssl_ca_path"],
                            "ssl_keyfile": REDIS_CFG["ssl_keyfile"],
                            "ssl_certfile": REDIS_CFG["ssl_certfile"],
                            "ssl_cert_reqs": REDIS_CFG["ssl_cert_reqs"],
                            "ssl_ca_certs": REDIS_CFG["ssl_ca_certs"],
                            "decode_responses": decode_responses,
                            "lib_name": f"redis-py(mcp-server_v{__version__})",
                            "max_connections_per_node": 10,
                        }
    
                        # Add credential provider if available
                        if credential_provider:
                            connection_params["credential_provider"] = credential_provider
                            # Note: Azure Redis Enterprise with EntraID uses plain text connections
                            # SSL setting is controlled by REDIS_SSL environment variable
                    else:
                        redis_class: Type[Union[Redis, RedisCluster]] = redis.Redis
                        connection_params = {
                            "host": REDIS_CFG["host"],
                            "port": REDIS_CFG["port"],
                            "db": REDIS_CFG["db"],
                            "username": REDIS_CFG["username"],
                            "password": REDIS_CFG["password"],
                            "ssl": REDIS_CFG["ssl"],
                            "ssl_ca_path": REDIS_CFG["ssl_ca_path"],
                            "ssl_keyfile": REDIS_CFG["ssl_keyfile"],
                            "ssl_certfile": REDIS_CFG["ssl_certfile"],
                            "ssl_cert_reqs": REDIS_CFG["ssl_cert_reqs"],
                            "ssl_ca_certs": REDIS_CFG["ssl_ca_certs"],
                            "decode_responses": decode_responses,
                            "lib_name": f"redis-py(mcp-server_v{__version__})",
                            "max_connections": 10,
                        }
    
                        # Add credential provider if available
                        if credential_provider:
                            connection_params["credential_provider"] = credential_provider
                            # Note: Azure Redis Enterprise with EntraID uses plain text connections
                            # SSL setting is controlled by REDIS_SSL environment variable
    
                    cls._instance = redis_class(**connection_params)
    
                except redis.exceptions.ConnectionError:
                    _logger.error("Failed to connect to Redis server")
                    raise
                except redis.exceptions.AuthenticationError:
                    _logger.error("Authentication failed")
                    raise
                except redis.exceptions.TimeoutError:
                    _logger.error("Connection timed out")
                    raise
                except redis.exceptions.ResponseError as e:
                    _logger.error("Response error: %s", e)
                    raise
                except redis.exceptions.RedisError as e:
                    _logger.error("Redis error: %s", e)
                    raise
                except redis.exceptions.ClusterError as e:
                    _logger.error("Redis Cluster error: %s", e)
                    raise
                except Exception as e:
                    _logger.error("Unexpected error: %s", e)
                    raise
    
            return cls._instance
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must disclose behavioral traits, but it only states the basic operation. It omits details such as whether the list is created if it doesn't exist, what happens on error, idempotency, or the return value (though an output schema may exist). The mutation implied by 'push' is the only behavioral hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that efficiently communicates the core action and optional parameter. No unnecessary words or redundancy, earning a high score for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and a 0% schema coverage, the description is insufficiently complete. It lacks behavioral context like list creation behavior, error conditions, return value semantics (though output schema may help), and does not leverage sibling tool names to clarify usage boundaries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description should compensate. It adds meaning to 'value' (the element to push) and 'expire' (optional TTL), but does not explain 'name' (the list key) or the allowed data types for 'value' as defined in the schema. Partial coverage, leaving gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Push'), the resource ('a value onto the right of a Redis list'), and an optional feature ('set an expiration time'). It distinguishes this from the sibling tool 'lpush' by specifying 'right', and from other list operations by naming the verb 'push'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use rpush versus alternatives like lpush or other list commands. It does not mention prerequisites, when not to use it, or any specific context where this tool is more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/redis/mcp-redis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server