Exposes Redis key-value store operations to AI agents including GET/SET, list operations, hash manipulation, and pub/sub debugging. Agents can inspect caches, debug session stores, and check feature flags without dumping entire databases. Supports Redis Cluster and Sentinel configurations.
Use cases
- Backend developer inspects cache contents to debug stale data issues
- DevOps agent checks session store TTLs during user login debugging
- Feature flag operator queries feature flag states across environments
- SRE agent monitors pub/sub channels for message flow issues
- Developer inspects rate limiter keys to understand current limits
Key features
- Claude Desktop
- Cursor
- Codex
Frequently Asked Questions
- Can agents see all keys including sensitive data?
- Yes, if connected with sufficient Redis permissions. Use Redis ACLs to restrict access. Avoid connecting production Redis instances directly to untrusted agents.
- What Redis data types are supported?
- All standard Redis types: strings, lists, sets, sorted sets, hashes, bitmaps, hyperloglogs, and geospatial indexes. JSON values stored as strings are also supported.
- Does it support Redis Cluster?
- Yes, the server can connect to Redis Cluster configurations. Operations that span multiple slots may have limited support depending on the cluster topology.
Related
Related
3 Indexed items
Supabase MCP
Connects agents to Supabase projects for table inspection, Edge Function debugging, database triggers, and real-time subscriptions. Agents can inspect RLS policies, view logs, and manage database types without the Supabase dashboard. Supports both hosted and self-hosted Supabase instances.
Postgres MCP
Enables AI agents to execute read-only SQL queries against PostgreSQL databases, inspect table schemas, and analyze query performance. Agents can debug data issues or prepare analytics without requiring direct database credentials in the conversation. Supports connection pooling and multiple database targets.
DuckDB MCP community extension (`duckdb_mcp`)
The DuckDB-distributed community extension `duckdb_mcp` embeds MCP client and server capabilities directly inside DuckDB. Installers load it via `INSTALL duckdb_mcp FROM community` followed by `LOAD duckdb_mcp`, after which SQL can attach remote MCP servers (stdio/TCP/WebSocket transports), enumerate resources (`mcp_list_resources`), invoke remote tools (`mcp_call_tool`), and wrap responses with `read_csv`/`read_json`/`read_parquet` URIs routed through `mcp://`. In reverse direction, DuckDB can publish tables, queries, and execution-bound tools (`mcp_publish_table`, `mcp_publish_query`, `mcp_publish_execution_tool`) while `mcp_server_start` exposes them to external MCP-compatible clients.