Redis MCP Serverofficial
A
securityA
licenseA
qualityThe official Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis.
Last updated -
42
51
Python
MIT License
Redis is an open-source, in-memory data structure store used as a database, cache, message broker, and streaming engine.
Why this server?
Provides comprehensive Redis database management through natural language, supporting strings, hashes, lists, sets, sorted sets, streams, JSON documents, vector search, and pub/sub functionality.
Why this server?
Enables management of Redis Cloud resources, including account management, subscription management (Pro and Essential), database capabilities configuration, cloud provider selection, and task monitoring through the Redis Cloud API.
Why this server?
Allows interaction with Redis databases, including creating new databases, running Redis commands, listing databases, managing backups, and viewing usage statistics.
Why this server?
Supports implementation of Redis caching for applications, allowing setup and configuration of caching with specified TTL values
Why this server?
Enables caching and data structure operations through Redis integration, supporting high-performance data access for tools and workflows
Why this server?
Provides access to Redis database operations through a Model Context Protocol (MCP) server. Includes tools for various Redis commands such as HMSET, HGET, HGETALL, SCAN, SET, GET, DEL, ZADD, ZRANGE, ZRANGEBYSCORE, ZREM, SADD, and SMEMBERS.
Why this server?
Mentioned as a potential data store for session persistence when customizing the implementation, suggesting the server can be extended to use Redis for data storage.
Why this server?
Provides caching functionality to improve performance of URL validations and reputation checks, with configurable connection settings through environment variables.
Why this server?
Supports Redis database deployment, configuration, and management within the Coolify platform.
Why this server?
Allows querying of Redis data by exposing it as relational SQL models through the CData JDBC Driver.
Why this server?
Enables Server-Sent Events (SSE) transport for MCP functionality when deployed on Vercel.
Why this server?
Enables SQL-based access to Redis in-memory data structure store.
Why this server?
Allows SQL-based querying of Redis key-value store data
Why this server?
Offers read-only access to Redis in-memory data structure store keys and values.
Why this server?
Listed as a supported data source for integration with the MCP server, allowing access to Redis data.
Why this server?
Allows SQL-based querying of Redis key-value stores.
Why this server?
Allows SQL-based access to Redis in-memory data structures.
Why this server?
Listed as a supported data source for accessing Redis in-memory data structure store.
Why this server?
Enables SQL-like access to Redis key-value stores.
Why this server?
Allows querying Redis in-memory data structure store data through SQL interfaces.
Why this server?
Allows access to data stored in Redis databases through SQL-like interfaces.
Why this server?
Allows querying of Redis data by exposing Redis as a relational SQL model, enabling access to live Redis data through natural language queries without requiring SQL knowledge.
Why this server?
Provides querying capabilities for Redis database data through SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC driver.
Why this server?
Provides read access to Redis in-memory data structure store information through SQL interfaces, enabling natural language querying of key-value data.
Why this server?
Listed as a supported data source in the compatibility table, enabling access to Redis data.
Why this server?
Utilizes Redis for persistent conversation storage and session management with configurable time-to-live functionality
Why this server?
Planned integration in Q3 2025 roadmap that will provide key-value pattern recognition for AI when working with Redis databases.
Why this server?
Mentioned as a storage strategy option for the stateful implementation of the server
Why this server?
Enables caching and real-time data processing for fast ETA calculations and service alerts distribution across the BMTC transportation network.
Why this server?
Provides the ability to query Redis key-value data as relational tables, enabling SQL-like access to Redis data structures.
Why this server?
Can be extended to use Redis for session tracking instead of in-memory storage.
Why this server?
Provides tools for interacting with Redis databases, including basic operations (get, set, delete, increment), list operations, hash operations, set operations, and pub/sub functionality, with automatic reconnection handling.
Why this server?
Implements a queue system for asynchronous processing of AI generation requests, providing job status tracking and efficient handling of concurrent requests.
Why this server?
Allows querying Redis key-value store data through SQL.
Why this server?
Listed as a supported data source for integration, allowing access to Redis data through the MCP server.
Why this server?
Allows querying of Redis database data through relational SQL models.
Why this server?
Listed as a supported data source for integration through the CData JDBC Driver
Why this server?
Enables SQL-based access to Redis key-value store data, treating Redis structures as relational tables.
Why this server?
Planned integration for Redis operations, including key-value operations, caching mechanisms, pub/sub functionality, and data structure operations.
Why this server?
Provides caching and real-time data handling for AI operations, enhancing response times and supporting state management across requests.
Why this server?
Enables interaction with Redis databases through a standardized set of tools for key-value operations, including setting values with optional expiration times, retrieving values, deleting keys, and listing keys matching patterns.
Why this server?
Utilized for caching frequently accessed blockchain data to improve performance
Why this server?
Leverages Redis for caching and high-performance data operations
Why this server?
Required for using the SSE transport in production, serving as the backing store for message handling
Why this server?
Optional integration for enhancing caching capabilities in high-load scenarios to replace in-memory caches
Why this server?
Optional integration with Redis for distributed caching to improve performance
Why this server?
Uses Redis for session storage in production environments, providing persistence across server restarts and distributed state management
Why this server?
Provides storage functionality for the MCP server, required for maintaining state and storing data when deployed on Vercel.
Why this server?
Used for session state persistence and OAuth token storage, enabling horizontal scaling and stateless server architecture.
Why this server?
Uses Redis as a backend storage for parsed decision tree data and to-do list items, enabling persistent storage of the server's state.
Why this server?
Provides capabilities to set up and manage Redis instances within Coolify.
Why this server?
Provides integration with Redis databases for key-value operations and data caching capabilities
Why this server?
Integrates with Redis for MCP server communication, allowing the Django migrations service to use Redis as a transport layer for message passing in distributed environments.
Why this server?
Provides data storage and caching capabilities for the MCP services