Skip to content

Redis MCP

Natural-language access to data stored in Redis.

Setup instructions ↗

How it runs

This server runs on your own machine. Your MCP client starts it as a local process (usually through npx, uvx or Docker) and talks to it over standard input/output. It runs with your user's permissions, so scope paths and credentials tightly.

Who maintains it

This is an official server published by the vendor behind the product it connects to, generally the safest choice for that integration.

Safety checklist

  • Review which tools it exposes, and prefer read-only modes where available.
  • Use scoped, least-privilege credentials or a test account first.
  • Keep human approval on for actions with side effects (writes, payments, deletions).
  • Treat content returned from the web or user data as untrusted, because it can contain prompt-injection attempts.

Similar MCP servers

Supabase MCP

Manage Supabase projects, run SQL and fetch logs.

Official (vendor)Local & remote

Neon MCP

Create branches, run queries and migrate Neon Postgres databases.

Official (vendor)Local & remote

MongoDB MCP

Query MongoDB and manage Atlas clusters.

Official (vendor)Local (stdio)

Elasticsearch MCP

Search and inspect Elasticsearch indices.

Official (vendor)Local (stdio)

ClickHouse MCP

Run read-only SQL against ClickHouse clusters.

Official (vendor)Local (stdio)

MotherDuck / DuckDB MCP

Query DuckDB files and MotherDuck from agents.

Official (vendor)Local (stdio)