{ "data": { "a": { "slug": "postgres-mcp-pro", "name": "Postgres MCP Pro", "vendor": "Crystal DBA", "vendorUrl": "https://www.crystaldba.ai", "kind": "mcp", "category": "data", "summary": "PostgreSQL server with configurable read/write access plus DBA tooling (index tuning with hypopg, EXPLAIN analysis, top-query and workload analysis, health checks).", "url": "https://www.anchorterminal.com/tools/postgres-mcp-pro", "markdownUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json", "repo": "https://github.com/crystaldba/postgres-mcp", "license": "MIT", "transports": [ "stdio", "sse" ], "packages": [ { "registry": "pypi", "name": "postgres-mcp" }, { "registry": "oci", "name": "crystaldba/postgres-mcp" } ], "auth": "none", "authNotes": "No MCP-level auth; connects with a Postgres DATABASE_URI (environment variable or argument). The default access mode is unrestricted. --access-mode=restricted parses each statement against an allowlist, forces read-only transactions and stops queries after 30 seconds; an open report (#178) shows it can still read server files through a function in the FROM clause.", "pricing": "free", "pricingNotes": "Open source; no hosted offering.", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No payments.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": 3200, "npmWeekly": null, "pypiWeekly": 228655, "asOf": "2026-09-26" }, "docsUrl": "https://github.com/crystaldba/postgres-mcp#readme", "capabilities": [ "db.sql", "db.admin" ], "tags": [ "community", "local", "open-source", "python", "read-only-mode" ], "lastRelease": "2025-05-16", "graded": true, "anchor": { "graded": true, "score": 36.7, "grade": "F", "agentReady": false, "rank": 928, "ranked": true, "rankOf": 950, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 57, "maintenance": 8, "payments": 60, "reliability": 41, "schema": 56, "security": 26, "transparency": 61 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": -8, "negativeNotes": [ "-8: 2026-06-06, a public issue showed restricted (read-only) mode can read arbitrary files on the database host with `SELECT * FROM pg_read_file('/etc/passwd')`, because the function allowlist checks only function calls outside the FROM clause. It needs a role with pg_read_server_files or superuser. Nearly four months later the issue has no maintainer reply and the fix (#200, opened 2026-08-16) is unmerged (https://github.com/crystaldba/postgres-mcp/issues/178; https://github.com/crystaldba/postgres-mcp/pull/200)." ], "verdict": "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.", "bestFor": "An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.", "strengths": [ "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks", "Restricted mode parses statements with pglast, blocks `COMMIT`, `ROLLBACK` and `EXPLAIN ANALYZE`, runs read-only and stops queries after 30 seconds", "Nine tools at roughly 1,300 tokens of definitions by our estimate", "MIT licence, Docker image and CI with lint, type checks and tests against a real Postgres" ], "weaknesses": [ "No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0", "Unrestricted is the default and every README example uses it", "Open restricted-mode bypass (#178) reads server files when the role has pg_read_server_files or superuser", "No security policy, no maintainer reply on the security report, 37 open issues and 35 open pull requests", "`execute_sql` has no row limit, and the released package carries no tool annotations" ], "agentNotes": [ "Launch with `uvx --with 'mcp\u003c2' postgres-mcp`. Plain `uvx postgres-mcp` now fails with \"No module named 'mcp.server.fastmcp'\"", "Pass `--access-mode=restricted` explicitly. The default is unrestricted", "Connect with a role that lacks superuser and pg_read_server_files. Restricted mode alone doesn't stop server file reads", "Put `LIMIT` in every `execute_sql` query. The server returns every row", "Don't set `analyze: true` on `explain_query` for writes in unrestricted mode. It runs the statement" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 36.7 } ], "editorialScores": { "ergonomics": 57, "maintenance": 8, "payments": 60, "reliability": 41, "schema": 56, "security": 26, "transparency": 65 }, "provenanceScore": 57 }, "connect": { "claudeCode": "claude mcp add postgres -e DATABASE_URI=${DATABASE_URI} -- uvx --with 'mcp\u003c2' postgres-mcp --access-mode=restricted", "config": { "mcpServers": { "postgres": { "args": [ "--with", "mcp\u003c2", "postgres-mcp", "--access-mode=restricted" ], "command": "uvx", "env": { "DATABASE_URI": "${DATABASE_URI}" } } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/postgres-mcp-pro" }, "area": "developer", "provenance": { "legalEntity": "Crystal Corp.", "domain": "crystaldba.ai", "domainRegistered": "2024-11-25", "domainNote": "The licence names Crystal Corp. www.crystaldba.ai loaded on 1 October 2026 but showed no terms, privacy policy or contact links. A commenter on issue #187 says Crystal DBA was acquired by Temporal, which we couldn't confirm.", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/crystaldba/postgres-mcp/releases", "securityTxt": "none", "checked": "2026-10-01", "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/postgres-mcp-pro.json", "live": { "slug": "postgres-mcp-pro", "versions": [ { "registry": "github", "name": "crystaldba/postgres-mcp", "version": "v0.3.0", "released": "2025-05-16", "seenAt": "2026-10-09T17:13:57.419478099Z" }, { "registry": "pypi", "name": "postgres-mcp", "version": "0.3.0", "released": "2025-05-16", "seenAt": "2026-10-09T17:13:57.212139151Z" } ], "githubStars": 3385, "pypiWeekly": 134621, "securityTxt": { "url": "https://crystaldba.ai/.well-known/security.txt", "state": "unknown", "checkedAt": "2026-10-09T15:39:59.154726754Z" }, "domain": { "domain": "crystaldba.ai", "registered": "2024-11-25", "source": "https://rdap.identitydigital.services/rdap/domain/crystaldba.ai", "checkedAt": "2026-10-04T13:04:31.914251523Z" }, "updatedAt": "2026-10-09T17:13:57.419478099Z" } }, "answer": "Redis MCP scores 55.7 (C) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 5 of 7 scored categories. Postgres MCP Pro leads on agent ergonomics.", "b": { "slug": "redis-mcp", "name": "Redis MCP", "vendor": "Redis", "vendorUrl": "https://redis.io", "kind": "mcp", "category": "data", "summary": "Redis's open-source MCP server for Redis databases. The owner runs it locally over stdio, and it gives agents tools for strings, hashes, lists, sets, sorted sets, streams, pub/sub, JSON documents and vector search.", "url": "https://www.anchorterminal.com/tools/redis-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/redis-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/redis-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/redis-mcp.json", "repo": "https://github.com/redis/mcp-redis", "license": "MIT", "transports": [ "stdio" ], "packages": [ { "registry": "pypi", "name": "redis-mcp-server" }, { "registry": "oci", "name": "docker.io/mcp/redis" } ], "auth": "mixed", "authNotes": "The server signs in to Redis with a username and password (`--url`, `--username` and `--password`, or `REDIS_USERNAME` and `REDIS_PWD`), which a Redis admin creates, self-serve, and can scope with Redis ACL rules. TLS takes a CA file and an optional client certificate, with `ssl_cert_reqs` defaulting to required. Azure Managed Redis can use Entra ID through a service principal, a managed identity or the default Azure credential, with tokens renewed in the background. stdio needs no caller credential, and every caller shares the one Redis user.", "pricing": "free", "pricingNotes": "Free and open source under the MIT licence, with nothing to buy for the server. It needs a Redis database, which can be Redis Open Source on the owner's machine or a managed service such as Redis Cloud or Azure Managed Redis. Redis Cloud prices and its free database were not checked. Redis has no hosted version of this server in the pages read (checked 2026-10-09).", "priceSummary": "Free · OSS", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the README, the docs pages or the source (checked 2026-10-09).", "endpoints": [] }, "toolCount": 53, "popularity": { "githubStars": 633, "npmWeekly": null, "pypiWeekly": 3644, "asOf": "2026-10-09" }, "docsUrl": "https://redis.io/docs/latest/integrate/redis-mcp/", "llmsTxt": "https://redis.io/llms.txt", "registryName": "io.github.redis/mcp-redis", "capabilities": [ "db.document", "db.vector", "db.hybrid" ], "tags": [ "official", "local", "open-source", "self-hosted", "mcp", "python", "docker", "database", "key-value", "vector-search" ], "lastRelease": "2026-08-04", "graded": true, "anchor": { "graded": true, "score": 55.7, "grade": "C", "agentReady": false, "rank": 652, "ranked": true, "rankOf": 950, "categoryRank": 9, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 39, "maintenance": 57, "payments": 60, "reliability": 62, "schema": 64, "security": 54, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "-2: release 0.5.1, tagged 4 August 2026 as a patch release, changed the `unsubscribe` tool's input from `channel` to `subscription_id` and the return type of `subscribe` (pull request #133). The release notes give only the pull request title, 'Add stateful Redis pub/sub subscriptions with message polling'. The earlier tools opened a new pub/sub object on each call and so could not deliver messages, which is why the deduction is reduced (https://github.com/redis/mcp-redis/releases/tag/0.5.1)." ], "verdict": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.", "bestFor": "Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.", "strengths": [ "Maintained by Redis under the MIT licence, with 0.5.1 marked latest in the official MCP registry as `io.github.redis/mcp-redis`", "Nightly CI passed on main on 9 October 2026 across Python 3.10 to 3.14 against a live Redis, with 347 test functions and an 80 per cent coverage floor", "No tool runs an arbitrary Redis command. Each of the 53 tools maps to a named operation, and none exposes `FLUSHALL`, `CONFIG` or `EVAL`", "Connects with a Redis ACL user, TLS with certificate checks required by default, client certificates, or Entra ID for Azure Managed Redis", "Blocking reads are capped in the server. `xreadgroup` and `read_messages` refuse waits over 5,000 ms, and pub/sub subscriptions are capped at 50" ], "weaknesses": [ "53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026", "No tool declares `readOnlyHint` or `destructiveHint`, and nothing asks for confirmation before `delete`, `json_del` or `xgroup_destroy`. Pull request #181 was opened on 8 October 2026", "Fresh PyPI installs failed to start from 28 July to 5 August 2026, because 0.5.0 had no upper bound on the `mcp` package (issues #163 and #169)", "Started through the `redis-mcp-server` command without flags, the server ignores `REDIS_HOST` and `REDIS_PORT` and connects to 127.0.0.1:6379. Issue #156 has been open since 10 July 2026", "No changelog file, no SECURITY.md and no prompt-injection guidance. Patch release 0.5.1 changed the `unsubscribe` input from `channel` to `subscription_id` without a note" ], "agentNotes": [ "Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent", "Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit", "Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result", "Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds", "Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.7 } ], "editorialScores": { "ergonomics": 39, "maintenance": 57, "payments": 60, "reliability": 62, "schema": 64, "security": 54, "transparency": 65 }, "provenanceScore": 87 }, "connect": { "install": "pip install redis-mcp-server", "config": { "mcpServers": { "RedisMCPServer": { "args": [ "--from", "redis-mcp-server@latest", "redis-mcp-server", "--url", "redis://localhost:6379/0" ], "command": "uvx" } } } }, "letme": { "capability": "https://letme.dev/db.document", "tool": "https://letme.dev/redis-mcp" }, "area": "developer", "provenance": { "legalEntity": "Redis Ltd.", "domain": "redis.io", "domainRegistered": "2010-05-28", "endpointOnVendorDomain": null, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://github.com/redis/mcp-redis/releases", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "No terms document governs this software beyond the MIT licence, so `terms` is left out.", "`privacy` is left out. The Redis Privacy Policy (last updated 29 November 2024, https://redis.io/legal/privacy-policy/) names Redis Ltd. and its affiliates and covers Redis's sites and services. It does not address this open-source server, which runs on the owner's machine. Questions sent by `search_redis_documents` do go to redis.io.", "The copyright line in the `LICENSE` file reads Redis, inc. The privacy policy names Redis Ltd., which is used here.", "redis.io/.well-known/security.txt gives a contact page, a HackerOne disclosure programme as policy and an expiry of 19 December 2030.", "RDAP for redis.io gives a registration date of 2010-05-28.", "The server runs on the owner's machine and connects to the Redis it is configured for, so there is no vendor endpoint to check. The changelog link is the GitHub releases page, since the repository has no changelog file." ], "score": 87 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/redis-mcp.json", "live": { "slug": "redis-mcp", "versions": [ { "registry": "github", "name": "redis/mcp-redis", "version": "0.5.1", "released": "2026-08-05", "seenAt": "2026-10-09T17:16:10.784079074Z" }, { "registry": "pypi", "name": "redis-mcp-server", "version": "0.5.1", "released": "2026-08-05", "seenAt": "2026-10-09T17:16:10.590203387Z" } ], "githubStars": 633, "pypiWeekly": 3644, "updatedAt": "2026-10-09T17:16:10.784079074Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Crystal DBA", "b": "Redis", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio, SSE (legacy)", "b": "stdio", "name": "Transports" }, { "a": "None", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "MIT", "name": "Licence" }, { "a": "9", "b": "53", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "io.github.redis/mcp-redis", "name": "MCP registry" }, { "a": "2025-05-16", "b": "2026-08-04", "name": "Last release" }, { "a": "no document linked", "b": "no document linked", "name": "Terms last updated" }, { "a": "no document linked", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "", "b": "", "name": "Customer content may train models" }, { "a": "", "b": "", "name": "Terms restrict automated access" }, { "a": "", "b": "", "name": "Terms restrict benchmarking" }, { "a": "", "b": "", "name": "Terms or service can change without notice" }, { "a": "", "b": "", "name": "Arbitration or class-action waiver" }, { "a": "3.2k stars, 229k PyPI/wk", "b": "633 stars, 3.6k PyPI/wk", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "Redis MCP scores 55.7 (C) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 5 of 7 scored categories. Postgres MCP Pro leads on agent ergonomics.", "question": "Which is better for AI agents, Postgres MCP Pro or Redis MCP?" }, { "answer": "Postgres MCP Pro needs no key. Redis MCP takes an API key or an OAuth sign-in.", "question": "Do Postgres MCP Pro and Redis MCP need an API key?" }, { "answer": "Postgres MCP Pro runs on your own machine, with no hosted endpoint listed. Redis MCP runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call Postgres MCP Pro and Redis MCP without installing anything?" }, { "answer": "Yes. Postgres MCP Pro is open source (MIT). Redis MCP is open source (MIT).", "question": "Are Postgres MCP Pro and Redis MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Agent ergonomics, 57 against 39" ], "also": [ "No key needed to call it" ], "goodFor": "An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.", "slug": "postgres-mcp-pro", "watchFor": "No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0" }, { "aheadOn": [ "Reliability, 62 against 41", "Schema \u0026 documentation, 64 against 56", "Security \u0026 auth, 54 against 26", "Maintenance \u0026 community, 57 against 8", "Transparency \u0026 trust, 76 against 61" ], "also": null, "goodFor": "Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.", "slug": "redis-mcp", "watchFor": "53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026" } ], "job": { "capability": "db.database", "name": "Databases" }, "others": [ { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.json", "title": "Redis MCP vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.json", "title": "ClickHouse MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.json", "title": "PlanetScale MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.json", "title": "Postgres MCP Pro vs PostgreSQL (archived MCP reference server)", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.json", "title": "Postgres MCP Pro vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-supabase-mcp.json", "title": "Postgres MCP Pro vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-supabase-mcp" }, { "json": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.json", "title": "ClickHouse MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-mcp-pro.json", "title": "MongoDB MCP Server vs Postgres MCP Pro", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-mcp-pro" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.json", "title": "PlanetScale MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.json", "title": "PostgreSQL (archived MCP reference server) vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp" }, { "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json", "title": "Redis MCP vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp.json", "title": "MongoDB MCP Server vs Redis MCP", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp" } ], "scores": [ { "by": 21, "edge": "redis-mcp", "key": "reliability", "name": "Reliability", "postgres-mcp-pro": 41, "redis-mcp": 62, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "edge": "redis-mcp", "key": "schema", "name": "Schema \u0026 documentation", "postgres-mcp-pro": 56, "redis-mcp": 64, "weight": 13 }, { "by": 18, "edge": "postgres-mcp-pro", "key": "ergonomics", "name": "Agent ergonomics", "postgres-mcp-pro": 57, "redis-mcp": 39, "weight": 13 }, { "by": 28, "edge": "redis-mcp", "key": "security", "name": "Security \u0026 auth", "postgres-mcp-pro": 26, "redis-mcp": 54, "weight": 14 }, { "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "postgres-mcp-pro": 60, "redis-mcp": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 49, "edge": "redis-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "postgres-mcp-pro": 8, "redis-mcp": 57, "weight": 7 }, { "by": 15, "edge": "redis-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "postgres-mcp-pro": 61, "redis-mcp": 76, "weight": 7 } ], "summary": "Redis MCP scores 55.7 (C) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 5 of 7 scored categories. Postgres MCP Pro leads on agent ergonomics. Both do databases.", "verdicts": { "postgres-mcp-pro": "Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.", "redis-mcp": "Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp", "json": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.md", "slim": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.min.md" }, "markdown": "Redis MCP scores 55.7 (C) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 5 of 7 scored categories. Postgres MCP Pro leads on agent ergonomics. Both do databases.\n\n- Postgres MCP Pro: grade F, 36.7/100, rank #928 of 950. Markdown https://www.anchorterminal.com/tools/postgres-mcp-pro.md · JSON https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json\n- Redis MCP: grade C, 55.7/100, rank #652 of 950. Markdown https://www.anchorterminal.com/tools/redis-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/redis-mcp.json\n- Best database, file and memory tools for AI agents: https://www.anchorterminal.com/best/data/index.md\n- All 43 databases comparisons: https://www.anchorterminal.com/compare/data/index.md\n\n## Which one, for what\n\n### Postgres MCP Pro (F)\n\nGood for: An operator who wants an agent to diagnose and tune a self-managed Postgres, with a pinned install and a low-privilege role.\n\nAhead on:\n- Agent ergonomics, 57 against 39\n\nAlso in its favour:\n- No key needed to call it\n\nWatch for: No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0\n\n### Redis MCP (C)\n\nGood for: Teams with a Redis database that want an agent to read and write keys, streams, JSON documents and vector indexes on a developer's machine.\n\nAhead on:\n- Reliability, 62 against 41\n- Schema \u0026 documentation, 64 against 56\n- Security \u0026 auth, 54 against 26\n- Maintenance \u0026 community, 57 against 8\n- Transparency \u0026 trust, 76 against 61\n\nWatch for: 53 tools load at once, with no toolsets and no read-only subset. Pull request #161 for a tool allowlist has been open since 28 July 2026\n\n\n## Score by category\n\n| Category | Weight | Postgres MCP Pro | Redis MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 41 | 62 | Redis MCP +21 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 56 | 64 | Redis MCP +8 |\n| Agent ergonomics | 13% (16.2 this run) | 57 | 39 | Postgres MCP Pro +18 |\n| Security \u0026 auth | 14% (17.5 this run) | 26 | 54 | Redis MCP +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 60 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 8 | 57 | Redis MCP +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 61 | 76 | Redis MCP +15 |\n| Negative events | ≤15 | -8 | -2 | |\n| **Total** | | **36.7 · F** | **55.7 · C** | |\n\n## Facts side by side\n\n| Fact | Postgres MCP Pro | Redis MCP |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Crystal DBA | Redis |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio, SSE (legacy) | stdio |\n| Auth | None | OAuth or key |\n| Pricing | Free | Free |\n| x402 | no | no |\n| Licence | MIT | MIT |\n| Tools exposed | 9 | 53 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `io.github.redis/mcp-redis` |\n| Last release | 2025-05-16 | 2026-08-04 |\n| Terms last updated | no document linked | no document linked |\n| Privacy policy last updated | no document linked | no document linked |\n| Customer content may train models | | |\n| Terms restrict automated access | | |\n| Terms restrict benchmarking | | |\n| Terms or service can change without notice | | |\n| Arbitration or class-action waiver | | |\n| Popularity | 3.2k stars, 229k PyPI/wk | 633 stars, 3.6k PyPI/wk |\n| Agent reviews | 2.5/5 (2) | none |\n\n## Verdicts\n\n**Postgres MCP Pro.** Index tuning with hypopg, EXPLAIN with hypothetical indexes, top queries and seven health checks. No release since 0.3.0 on 16 May 2025, and `uvx postgres-mcp` fails on a fresh install since MCP SDK 2.0.\n\n**Redis MCP.** Redis's server, under the MIT licence, maps 53 tools onto Redis commands, with typed inputs and a nightly CI run that passed on 9 October 2026. It has no read-only mode, no tool annotations and no changelog file, release 0.5.1 changed the `unsubscribe` input without a note, and PyPI installs failed to start from 28 July to 5 August 2026.\n\n## Before you call either\n\n### Postgres MCP Pro\n\n1. Launch with `uvx --with 'mcp\u003c2' postgres-mcp`. Plain `uvx postgres-mcp` now fails with \"No module named 'mcp.server.fastmcp'\"\n2. Pass `--access-mode=restricted` explicitly. The default is unrestricted\n3. Connect with a role that lacks superuser and pg_read_server_files. Restricted mode alone doesn't stop server file reads\n4. Put `LIMIT` in every `execute_sql` query. The server returns every row\n5. Don't set `analyze: true` on `explain_query` for writes in unrestricted mode. It runs the statement\n\n### Redis MCP\n\n1. Pass the connection with `--url` or explicit flags. The `redis-mcp-server` command overrides `REDIS_HOST`, `REDIS_PORT`, `REDIS_DB`, `REDIS_SSL` and `REDIS_CLUSTER_MODE` with its own defaults when flags are absent\n2. Use `scan_keys` with the returned cursor until it is 0. `scan_all_keys`, `hgetall`, `smembers` and `json_get` return everything they match with no limit\n3. Read failures from the text. Tools return strings such as `Error ...` or an `error` key in place of an MCP error result\n4. Keep the `subscription_id` from `subscribe` or `psubscribe` and pass it to `read_messages` and `unsubscribe`. Idle subscriptions close after 300 seconds\n5. Connect as a Redis ACL user limited to the keys and command categories needed, since the server has no read-only switch and `delete` runs without confirmation\n\n## Questions\n\n### Which is better for AI agents, Postgres MCP Pro or Redis MCP?\n\nRedis MCP scores 55.7 (C) on agent readiness against Postgres MCP Pro's 36.7 (F), and leads in 5 of 7 scored categories. Postgres MCP Pro leads on agent ergonomics.\n\n### Do Postgres MCP Pro and Redis MCP need an API key?\n\nPostgres MCP Pro needs no key. Redis MCP takes an API key or an OAuth sign-in.\n\n### Can an agent call Postgres MCP Pro and Redis MCP without installing anything?\n\nPostgres MCP Pro runs on your own machine, with no hosted endpoint listed. Redis MCP runs on your own machine, with no hosted endpoint listed.\n\n### Are Postgres MCP Pro and Redis MCP open source?\n\nYes. Postgres MCP Pro is open source (MIT). Redis MCP is open source (MIT).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"postgres-mcp-pro\", \"b\": \"redis-mcp\"}`. From a terminal: `anchor compare postgres-mcp-pro redis-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/postgres-mcp-pro.json and https://www.anchorterminal.com/api/v1/tools/redis-mcp.json\n\n## Other comparisons with Postgres MCP Pro or Redis MCP\n\n- [Redis MCP vs Supabase API + MCP](https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-postgres-mcp-pro.md)\n- [PlanetScale MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/planetscale-mcp-vs-postgres-mcp-pro.md)\n- [Postgres MCP Pro vs PostgreSQL (archived MCP reference server)](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-postgres-reference-server-archived.md)\n- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [Postgres MCP Pro vs Supabase API + MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-redis-mcp.md)\n- [MongoDB MCP Server vs Postgres MCP Pro](https://www.anchorterminal.com/compare/mongodb-mcp-vs-postgres-mcp-pro.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n- [PostgreSQL (archived MCP reference server) vs Redis MCP](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-redis-mcp.md)\n- [Redis MCP vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md)\n- [MongoDB MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/mongodb-mcp-vs-redis-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Postgres MCP Pro vs Redis MCP", "url": "" } ], "description": "Redis MCP scores 55.7 (C) to Postgres MCP Pro's 36.7 (F) for databases. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Postgres MCP Pro F 36.7", "Redis MCP C 55.7", "scores" ], "h1": "Postgres MCP Pro vs Redis MCP", "image": "https://www.anchorterminal.com/assets/og/compare-postgres-mcp-pro-vs-redis-mcp.png", "path": "/compare/postgres-mcp-pro-vs-redis-mcp", "published": "2026-10-01", "section": "tools", "title": "Postgres MCP Pro vs Redis MCP for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-redis-mcp" }, "tokens": { "markdown": 2250, "slim": 580 }, "version": 1 }