Redis

Redis’s official MCP server exposes the full range of data structures — strings, hashes, lists, sets, sorted sets, streams, and JSON — as agent tools, alongside Redis Search for vector and full-text queries when the module is available, so an agent can inspect and manipulate a live Redis instance the same way a developer would with redis-cli, but in natural language.

It’s equally useful for two different jobs: operational debugging against a production or staging cache (what’s the TTL on this key, why is this counter wrong), and building retrieval features that read or write vector embeddings directly through Redis Search rather than a separate vector database.

Since it runs locally and connects directly to a Redis instance with whatever credentials it’s given, treat connection scope the same way you would any direct database credential — point it at a specific instance and database number, not a shared production cluster, unless that’s genuinely the intent.