Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 5
- 4 6
- 3 6
- 2 0
- 1 0
Trust in production
- Trust it - 53%
- With caveats - 41%
- Wouldn't - 6%
76% would recommend this server
How reviewers scored it
- Setup & docs 3.8
- Auth experience 3.6
- Reliability 3.9
- Maintainer responsiveness 4.5
Why it got a B
Redis's own server, MIT licensed, local stdio only, with no advisories on record. It can write and delete keys, streams and indexes, so connect as a Redis ACL user limited to what the agent needs (the README shows a read-only +@read -@write user) and use rediss:// with certificate checks for remote databases. Azure Managed Redis can use Entra ID sign-in instead of a password. Biggest deductions: auth is just whatever Redis user you give it, often no password at all on localhost, and nearly all recent code comes from one maintainer.
How to connect
// claude_desktop_config.json (use the full path to uvx)
{ "mcpServers": { "redis-mcp-server": { "type": "stdio",
"command": "/Users/mortensi/.local/bin/uvx",
"args": ["--from", "redis-mcp-server@latest", "redis-mcp-server",
"--url", "redis://localhost:6379/0"] } } }Is Redis MCP Server safe?
Is Redis MCP Server safe to use?
Redis MCP Server grades B (solid, with minor gaps). Login is optional, so check that it is turned on in your setup. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It runs locally over stdio, so it acts with your machine's access.
Does Redis MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Redis MCP Server support authentication?
Optionally. It can run with a login, but it does not require one, so turn it on.
Alternatives in Databases & Data Stores
- A MongoDB MCP ServerQuery and administer MongoDB and Atlas clusters from an agent.
- A Neon MCP ServerOfficial hosted Neon server to manage Postgres projects and branches, run SQL, and inspect schema.
- A Supabase MCP ServerOfficial hosted Supabase server to manage projects, run SQL, and inspect schema.
- B BigQuery MCP ServerGoogle-hosted remote server to list datasets and tables, read schemas, and run SQL in BigQuery.
- B MCP Toolbox for DatabasesGoogle's open-source MCP server with prebuilt tools for Postgres, MySQL, BigQuery, AlloyDB, Cloud SQL, Spanner, and more.
Embed this badge
[](https://trustedmcp.io/servers/redis-mcp-server)<a href="https://trustedmcp.io/servers/redis-mcp-server"><img src="https://trustedmcp.io/badge/redis-mcp-server.svg" alt="TrustedMCP grade B" height="80"></a>Community reviews
Saves me a context switch every hour
Hooked Redis MCP Server into Claude Code and it worked on the first try. I run it with auth enabled. Without it I would not let it near anything shared. Turned on read-only mode on day one, highly recommend doing the same. Releases come often and the changelog is clear. Happy to run it in production.
Used for Read-only analytics questions
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Our team uses it every day
Our agents call this dozens of times a day. I run it with auth enabled. Without it I would not let it near anything shared. Nice to use something maintained by Redis rather than a random fork. Would recommend without hesitation.
Used for Debugging data issues in staging
- Setup & docs 5/5
- Auth experience 3/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Good, but read the permissions first
I like it, with reservations. Releases come often and the changelog is clear. Being official from Redis counts for a lot when I pitch it to security. For anything real I would look elsewhere.
Used for Incident investigation
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
The Redis integration I wanted
Simple to set up in Cursor, simple to reason about. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Schema exploration during a migration
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Surprisingly polished
Of the Redis integrations I tried, this one is the most predictable. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Recommended, with sensible guardrails.
Used for Answering support questions from the database
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Easy win for our agent setup
Installed it on a Friday, it was part of my workflow by Monday. Read-only mode is the first thing I enable, and it covers most of what I need. Filed an issue and got a reply within two days. It is in our production agent and I sleep fine.
Used for Prototyping queries before writing code
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Quietly reliable
Tried it on a side project first, then rolled it out at work. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Read-only mode is the first thing I enable, and it covers most of what I need.
Used for Read-only analytics questions
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Useful, with a few rough edges
It does the job, but it took some tweaking. I run it with auth enabled. Without it I would not let it near anything shared. You can tell it is actively maintained, the rough edges keep getting fixed.
Used for Checking data quality after imports
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Clean integration, sensible permissions
Set this up for our team after comparing a few options. Turned on read-only mode on day one, highly recommend doing the same. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Easy recommendation.
Used for Schema exploration during a migration
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Mixed feelings after two weeks
Mostly reliable, with the odd timeout. Releases come often and the changelog is clear. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Worth it, just do not skip the hardening steps.
Used for Answering support questions from the database
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Trustworthy enough for real work
I use this almost daily. Updates land regularly, and nothing broke when I upgraded. Turned on read-only mode on day one, highly recommend doing the same. I run it with auth enabled. Without it I would not let it near anything shared.
Used for Incident investigation
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Handy for dev, careful in prod
Useful tool, though I would not hand it to a junior unsupervised. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Keep permissions tight and it is a good tool.
Used for Debugging data issues in staging
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 5/5
OK for read-only work
Some tools are great, a couple feel half finished. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Turned on read-only mode on day one, highly recommend doing the same. Fine in production if you sandbox it.
Used for Checking data quality after imports
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Does the job, docs could be better
Good for experimenting, still deciding about production. Read-only mode is the first thing I enable, and it covers most of what I need. Filed an issue and got a reply within two days. I would use it in prod, but only with a human approving writes.
Used for Prototyping queries before writing code
- Setup & docs 3/5
- Auth experience 2/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Better than the DIY script it replaced
Started with it as an experiment, now it is a fixture. Filed an issue and got a reply within two days. Runs locally over stdio, so startup is instant and nothing leaves my machine unless a tool calls out.
Used for Generating SQL for ad-hoc reports
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Recommended it to two teams already
Clear tool names, sensible outputs, very few surprises. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Generating SQL for ad-hoc reports
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 4/5
No complaints after a month
Replaced a homegrown script with Redis MCP Server and have not looked back. Nice to use something maintained by Redis rather than a random fork. Good choice if you need Redis in your agent.
Used for Generating SQL for ad-hoc reports
- Setup & docs 3/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.