Last Verified: September 2026 — commit activity, star counts, and install commands checked against live GitHub sources
Every popular MCP list has a Postgres server and a Supabase server on it. Fewer of them tell you that Anthropic’s own reference Postgres server is archived and has a documented read-only bypass, or that a “1.7k-star” MongoDB integration can be outranked by an official server that ships weekly. We ran the same maintenance check from our first curation guide against the database and backend category. Two names got cut for being stale or unsafe; five made it through.
Quick Start
Install any of these with the Claude Code CLI. Swap in your own credentials before running.
claude mcp add supabase -- npx -y @supabase/mcp-server-supabase@latest --access-token=$SUPABASE_ACCESS_TOKEN
claude mcp add redis -- uvx --from git+https://github.com/redis/mcp-redis.git redis-mcp-server --url redis://localhost:6379/0
claude mcp add mongodb -- npx -y mongodb-mcp-server --connectionString="$MDB_URI"
claude mcp add postgres -- uvx postgres-mcp --access-mode=restricted "$DATABASE_URI"
claude mcp add clickhouse -- uvx mcp-clickhouse⚡ Copy This Prompt
Paste this into Claude Code to let it install only what your stack actually uses:
I work with [Postgres / Supabase / Redis / MongoDB / ClickHouse -- name your stack].
Install only the matching MCP server(s) from this list, using the credentials I have
available in my environment variables. After installing, run one safe read-only
command through each server (e.g. list tables, list keys, or list databases) to
confirm the connection actually works. Tell me plainly if a connection or a
permission check fails -- don't guess or paper over an error.| What You’ll Need | Notes |
|---|---|
| Claude Code CLI installed | Any recent version supports claude mcp add |
| Connection string or access token per database | Never paste raw credentials into chat — use environment variables |
uv / uvx installed | Required for the Redis, Postgres, and ClickHouse servers (Python-based) |
| Node.js + npm | Required for the Supabase and MongoDB servers (JS-based, run via npx) |
1. Supabase MCP (supabase-community/supabase-mcp)
Supabase’s own team maintains this server, and it’s the one we’d point most readers to first — it covers the whole BaaS surface (Postgres tables, auth, storage, edge functions) through one connection instead of stitching together separate tools.
Why it made the cut: official repo, consistent commit cadence (roughly 20+ commits/month in recent audits), and it ranks near the top of every independent “best database MCP” comparison we checked.
Watch out for: by default it can run destructive operations against your project. Pass --read-only if you’re pointing it at anything other than a scratch/dev project.
2. Redis MCP (redis/mcp-redis)
Smaller star count than the others on this list, but it’s the vendor’s own server, not a community reimplementation — and an unofficial alternative with more stars (GongRzhe/REDIS-MCP-Server) was archived in March 2026, which makes this the safer long-term pick despite the lower number.
Why it made the cut: actively released by Redis Inc. itself; covers strings, hashes, streams, and pub/sub through one consistent tool surface.
Watch out for: star count alone would make this look like the “unpopular” option. Don’t let that fool you — vendor backing matters more than stars for a cache/session-store integration you’re trusting with production data.
3. MongoDB MCP (mongodb-js/mongodb-mcp-server)
MongoDB’s official server is now generally available, with 41+ tools spanning database operations, Atlas cluster management, and performance advisory — and it ships new releases roughly every 1-2 weeks.
Why it made the cut: vendor-official, GA status, and read-only mode plus environment-variable credentials are the security defaults, not an opt-in.
Watch out for: several older community MongoDB servers still show up in search results with similar names. If the repo isn’t under the mongodb-js or mongodb-developer org, you’re looking at an unofficial fork with a smaller maintenance team behind it.
4. Postgres MCP Pro (crystaldba/postgres-mcp)
This is the one with the asterisk. It’s the most popular general-purpose Postgres server, with index tuning, EXPLAIN plan analysis, and health checks built in — genuinely useful tools the official (now-archived) Anthropic server never had. But development has slowed: our check found roughly one commit in the last 12 weeks and a backlog of open issues, some unanswered since early 2025.
Why it made the cut anyway: “slower” is not “abandoned” — it’s still shipping, still the most feature-complete option, and it beats the alternative of using Anthropic’s archived reference server, which has a documented read-only bypass and receives no security patches at all.
Watch out for: if you need a strict read-only default for a production database, look at HenkDz/postgresql-mcp-server instead — smaller (~200 stars) but built specifically so writes, DDL, and arbitrary SQL all require an explicit opt-in flag.
5. ClickHouse MCP (ClickHouse/mcp-clickhouse)
The odd one out on most “top 5 database MCP” lists, and that’s exactly why it’s here — if your backend does analytics or event logging at scale, a transactional-database server won’t help you. ClickHouse’s own team maintains this one, distributed as a Docker Hub Verified Publisher image.
Why it made the cut: official, actively maintained, and it’s the only analytics-database option that passed our maintenance check — most of the community ClickHouse servers we found were single-author projects with no recent activity.
Watch out for: it expects ClickHouse-specific connection env vars (host, port, user, password) rather than a single connection-string argument like the others on this list.
Verify Each One Actually Works
✓ supabase — connected
✓ redis — connected
✓ mongodb — connected
✓ postgres — connected
✓ clickhouse — connected
Then ask Claude Code to run one read-only action through each — list tables, list keys, list databases — before you trust it with anything that writes.
Common Mistakes to Avoid
- Judging by star count alone. Redis’s official server has a fraction of the stars of some abandoned forks. Vendor backing and commit recency matter more than the number.
- Pointing a write-capable server at production on day one. Test every new MCP connection against a dev/staging database first.
- Assuming “modelcontextprotocol/*” means officially supported. Anthropic archived 13 of its 20 original reference servers in 2025, including Postgres, SQLite, and Redis — those repos still run, but they get no security patches.
- Skipping the read-only flag on Supabase. Without it, the server can alter schema and data in your connected project.
Q&A
Why is Postgres MCP Pro included if development slowed down?
Because “slower than ideal” still beats the alternative: Anthropic’s own reference Postgres server is archived and has a known read-only bypass vulnerability. If you need a stricter security posture, we also name a smaller alternative (HenkDz/postgresql-mcp-server) in that section.
Should I use the official or community server when both exist?
Default to official when the vendor maintains one — as with Redis, Supabase, MongoDB, and ClickHouse here. Community servers can still be worth using, but check commit recency first; we cover that process on our Methodology page.
Can I install more than one of these at once?
Yes — each runs as an independent MCP connection. If you use Playwright or GitHub MCP alongside these, see our Playwright MCP guide and GitHub MCP guide for the same install pattern.
Official Resources
- supabase-community/supabase-mcp on GitHub
- redis/mcp-redis on GitHub
- mongodb-js/mongodb-mcp-server on GitHub
- crystaldba/postgres-mcp on GitHub
- ClickHouse/mcp-clickhouse on GitHub
We re-check every server on this list before we call it verified. Follow along for the next curation drop.
Follow @quickpromptco
Leave a Reply