Redis MCP Server
Related Servers
Alternatives to Redis MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server that exposes Redis API to AI models4427 PyPIMIT

Redis MCP Serverofficial
AlicenseBqualityBmaintenanceThe official Redis MCP Server is a natural language interface designed for agentic applications to efficiently manage and search data in Redis.533,039 PyPI642MIT
Upstash MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceModel 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.1,499 npm61MIT
Upstash Redis MCPofficial
AlicenseNot gradedqualityCmaintenanceLightweight MCP server for Redis that allows running any Redis command and searching Redis documentation. Supports multiple named databases with HTTP/REST or TCP transport.127 npmMIT- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to design and deploy WRedis/Redis-backed services using expert patterns, architecture scaffolding, and a unified CLI.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for Redis interaction with dynamic connection setup and management.-
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: redis_query is strictly read-only, redis_execute handles writes/deletes/admin/high-risk commands, and redis_context manages connection/database context. Boundary is reinforced by server-side read-only enforcement and rejection messages directing callers to the right tool.
All tools use the redis_ prefix and are readable, giving a predictable grouping. However, query and execute are verbs while context is a noun, so the convention is slightly mixed but still intuitive.
Three tools are well-scoped for a Redis MCP server: read, write/admin, and context management cover the main interaction modes without redundancy. Each tool earns its place and there is no obvious tool bloat.
The surface covers read-only queries, write/admin commands, and context switching/listing, which are the core Redis operations an agent needs. Minor gaps exist around saved-connection lifecycle management (create/delete saved connections) and possibly transaction/pipeline workflows, but agents can work around these.