{ "data": { "a": { "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": "mcp-registry", "name": "io.github.redis/mcp-redis", "version": "0.5.1", "seenAt": "2026-10-10T03:11:32.438759038Z" }, { "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-10T03:11:32.438759038Z" } }, "answer": "Snowflake-managed MCP server and Redis MCP score within a point of each other on agent readiness, 56.4 (C) and 55.7 (C). Redis MCP leads on reliability and payments \u0026 pricing.", "b": { "slug": "snowflake-managed", "name": "Snowflake-managed MCP server", "vendor": "Snowflake Inc.", "vendorUrl": "https://www.snowflake.com", "kind": "mcp", "category": "data", "summary": "Snowflake's managed MCP server is an object created in a Snowflake account that exposes Cortex Agents, Cortex Search, Cortex Analyst, SQL execution and custom functions, each as an MCP tool, over HTTP, with OAuth and role-based access control.", "url": "https://www.anchorterminal.com/tools/snowflake-managed", "markdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/snowflake-managed.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json", "license": "Proprietary service under Snowflake's terms of service", "transports": [ "streamable-http" ], "packages": [], "auth": "mixed", "authNotes": "OAuth 2.0 is the documented default. An administrator creates a Snowflake OAuth security integration (confidential, or public with PKCE) and gives its client ID and secret to the MCP client, because dynamic client registration is not supported. Since 22 July 2026 a schema, database or account can bind its MCP servers to an External OAuth integration such as Okta or Microsoft Entra ID. Scopes of the form `session:role:\u003crole_name\u003e` pick the session's primary role. Programmatic access tokens are also accepted, expire after 15 days by default and 365 at most, and Snowflake recommends OAuth over them. There is no self-serve key an agent can mint for itself.", "pricing": "usage", "pricingNotes": "No charge is listed for the MCP server itself. Tools bill at the rates of what they call. SQL and custom tools use warehouse compute in Platform Credits, from $2.00 a credit on demand for Standard edition in US regions. Cortex Agents and Cortex Search bill in AI Credits at $2.00 each with global routing. A 30-day trial needs only an email address, with Cortex tools disabled until a card is added (checked 2026-10-09).", "priceSummary": "$2 / credit", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP server docs, the AI pricing page or the Service Consumption Table (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.snowflake.com/en/user-guide/snowflake-cortex/cortex-agents-mcp", "llmsTxt": "https://docs.snowflake.com/llms.txt", "capabilities": [ "db.sql", "knowledge.search", "analytics.query" ], "tags": [ "official", "hosted", "mcp", "oauth", "read-only-mode", "database", "enterprise", "llms-txt", "status-page", "soc2", "usage-priced", "free-trial" ], "lastRelease": "2026-08-20", "graded": true, "anchor": { "graded": true, "score": 56.4, "grade": "C", "agentReady": false, "rank": 633, "ranked": true, "rankOf": 950, "categoryRank": 8, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 46, "maintenance": 55, "payments": 35, "reliability": 55, "schema": 61, "security": 77, "transparency": 84 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": -2, "negativeNotes": [ "20 August 2026. `tools/call` responses changed from a single JSON body to an SSE stream as an unbundled behaviour change that accounts could not disable, outside the eight-week bundle process. Clients reading one JSON body broke. The change is documented with migration steps and clients that follow the MCP specification were unaffected, so the deduction is small. Whether notice was given before the release date was not established (https://docs.snowflake.com/en/release-notes/bcr-bundles/un-bundled/bcr-2405)." ], "verdict": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.", "bestFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "strengths": [ "Each tool needs its own grant. `USAGE` on the MCP server does not give access to the agent, search service, semantic view, function or procedure behind a tool", "The SQL execution tool defaults to `read_only: true` and takes a `query_timeout` and a named warehouse", "OAuth with PKCE for public clients, role scopes, an allowed-roles list and, since 22 July 2026, binding to an external identity provider with RFC 9728 metadata", "Generally available since 4 November 2025, under a 99.9 per cent monthly availability SLA with service credits", "Per-credit prices by region and edition are public in the Service Consumption Table, and the docs publish llms.txt and Markdown copies of every page" ], "weaknesses": [ "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation", "No dynamic client registration. An administrator creates a security integration and hands the client ID and secret to each MCP client", "On 20 August 2026 `tools/call` responses changed from one JSON body to an SSE stream, outside a behaviour change bundle and with no way to disable it", "Resources, prompts, roots, notifications, sampling, version negotiation and lifecycle phases are unsupported, and SQL and custom tool responses are cut at 250 KB", "status.snowflake.com shows two incidents marked critical (25 and 27 September 2026) and one marked major (6 October) in the 15 days its front page lists", "Cortex tools stay disabled on a trial account until a credit card is added" ], "agentNotes": [ "Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`", "Write the account hostname with hyphens, not underscores, or some clients fail to connect", "Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting", "Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB", "Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential" ], "metrics": { "kind": "remote", "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": 56.4 } ], "editorialScores": { "ergonomics": 46, "maintenance": 55, "payments": 35, "reliability": 55, "schema": 61, "security": 77, "transparency": 68 }, "provenanceScore": 99 }, "connect": { "config": { "mcpServers": { "snowflake": { "auth": { "CLIENT_ID": "${env:MCP_CLIENT_ID}", "CLIENT_SECRET": "${env:MCP_CLIENT_SECRET}" }, "url": "https://\u003caccount_url\u003e/api/v2/databases/\u003cdatabase\u003e/schemas/\u003cschema\u003e/mcp-servers/\u003cname\u003e" } } } }, "letme": { "capability": "https://letme.dev/db.sql", "tool": "https://letme.dev/snowflake-managed" }, "area": "developer", "unitPrices": [ { "item": "Platform Credit, Standard edition, on demand", "unit": "credit", "usd": 2, "note": "AWS US East. $3.00 on Enterprise. Higher in other regions. Used by SQL and custom tools through a warehouse" }, { "item": "AI Credit, global routing", "unit": "credit", "usd": 2, "note": "$2.20 with regional routing. Used by Cortex Agents and Cortex Search" } ], "provenance": { "legalEntity": "Snowflake Inc.", "domain": "snowflake.com", "domainRegistered": "1995-07-08", "endpointOnVendorDomain": true, "terms": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "privacy": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "statusPage": "https://status.snowflake.com", "changelog": "https://docs.snowflake.com/en/release-notes/new-features", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Privacy Notice (updated 1 July 2026) names Snowflake Inc., Suite 3A, 106 East Babcock Street, Bozeman, Montana 59715, and says it does not apply to Customer Data, which the customer agreement and the DPA govern.", "The terms link is the Self-Service On Demand Terms of Service (updated 16 April 2026), which a self-serve account accepts. Contract customers sign the Master Terms at https://www.snowflake.com/en/legal/terms-of-service/.", "Each MCP server answers on the customer's account URL, which the docs give as https://\u003corgname\u003e-\u003caccount_name\u003e.snowflakecomputing.com, a second Snowflake domain.", "security.txt at www.snowflake.com/.well-known/security.txt names security@snowflake.com and a HackerOne policy, and expires on 17 August 2027.", "RDAP for snowflake.com gives a registration date of 1995-07-08." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/snowflake-managed.json", "live": { "slug": "snowflake-managed", "vendorStatus": { "page": "https://status.snowflake.com", "indicator": "minor", "summary": "Partially Degraded Service", "checkedAt": "2026-10-10T03:58:47.197623919Z" }, "pages": [ { "url": "https://docs.snowflake.com/en/release-notes/new-features", "kind": "changelog", "status": 200, "checkedAt": "2026-10-09T18:38:22.182288094Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e4104fceb66c" }, { "url": "https://www.snowflake.com/en/legal/privacy/privacy-policy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:54:26.035718718Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "baf8ac1c3f70" }, { "url": "https://www.snowflake.com/en/legal/terms-of-service/self-service-on-demand-terms-of-service/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:54:28.152417291Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5b6b42771109" } ], "updatedAt": "2026-10-10T03:58:47.197623919Z" } }, "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Redis", "b": "Snowflake Inc.", "name": "Vendor" }, { "a": "no (local only)", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Free", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "Proprietary service under Snowflake's terms of service", "name": "Licence" }, { "a": "53", "b": "none", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.redis/mcp-redis", "b": "not listed", "name": "MCP registry" }, { "a": "2026-08-04", "b": "2026-08-20", "name": "Last release" }, { "a": "no document linked", "b": "2026-04-16", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-07-01", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "633 stars, 3.6k PyPI/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Snowflake-managed MCP server and Redis MCP score within a point of each other on agent readiness, 56.4 (C) and 55.7 (C). Redis MCP leads on reliability and payments \u0026 pricing.", "question": "Which is better for AI agents, Redis MCP or Snowflake-managed MCP server?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Redis MCP and Snowflake-managed MCP server need an API key?" }, { "answer": "Redis MCP runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Snowflake-managed MCP server.", "question": "Can an agent call Redis MCP and Snowflake-managed MCP server without installing anything?" }, { "answer": "Redis MCP is open source (MIT). No open-source release is listed for Snowflake-managed MCP server.", "question": "Are Redis MCP and Snowflake-managed MCP server open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 62 against 55", "Payments \u0026 pricing, 60 against 35" ], "also": [ "Runs on your own machine", "Open source" ], "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" }, { "aheadOn": [ "Agent ergonomics, 46 against 39", "Security \u0026 auth, 77 against 54", "Transparency \u0026 trust, 84 against 76" ], "also": null, "goodFor": "A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.", "slug": "snowflake-managed", "watchFor": "No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation" } ], "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-snowflake-managed.json", "title": "ClickHouse MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.json", "title": "PlanetScale MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed" }, { "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-reference-server-archived-vs-snowflake-managed.json", "title": "PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed" }, { "json": "https://www.anchorterminal.com/compare/snowflake-managed-vs-supabase-mcp.json", "title": "Snowflake-managed MCP server vs Supabase API + MCP", "url": "https://www.anchorterminal.com/compare/snowflake-managed-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-snowflake-managed.json", "title": "MongoDB MCP Server vs Snowflake-managed MCP server", "url": "https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed" }, { "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-mcp-pro-vs-redis-mcp.json", "title": "Postgres MCP Pro vs Redis MCP", "url": "https://www.anchorterminal.com/compare/postgres-mcp-pro-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/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": 7, "edge": "redis-mcp", "key": "reliability", "name": "Reliability", "redis-mcp": 62, "snowflake-managed": 55, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 3, "edge": "redis-mcp", "key": "schema", "name": "Schema \u0026 documentation", "redis-mcp": 64, "snowflake-managed": 61, "weight": 13 }, { "by": 7, "edge": "snowflake-managed", "key": "ergonomics", "name": "Agent ergonomics", "redis-mcp": 39, "snowflake-managed": 46, "weight": 13 }, { "by": 23, "edge": "snowflake-managed", "key": "security", "name": "Security \u0026 auth", "redis-mcp": 54, "snowflake-managed": 77, "weight": 14 }, { "by": 25, "edge": "redis-mcp", "key": "payments", "name": "Payments \u0026 pricing", "redis-mcp": 60, "snowflake-managed": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "redis-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "redis-mcp": 57, "snowflake-managed": 55, "weight": 7 }, { "by": 8, "edge": "snowflake-managed", "key": "transparency", "name": "Transparency \u0026 trust", "redis-mcp": 76, "snowflake-managed": 84, "weight": 7 } ], "summary": "Snowflake-managed MCP server and Redis MCP score within a point of each other on agent readiness, 56.4 (C) and 55.7 (C). Redis MCP leads on reliability and payments \u0026 pricing. Both do databases.", "verdicts": { "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.", "snowflake-managed": "Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed", "json": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.md", "slim": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.min.md" }, "markdown": "Snowflake-managed MCP server and Redis MCP score within a point of each other on agent readiness, 56.4 (C) and 55.7 (C). Redis MCP leads on reliability and payments \u0026 pricing. Both do databases.\n\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- Snowflake-managed MCP server: grade C, 56.4/100, rank #633 of 950. Markdown https://www.anchorterminal.com/tools/snowflake-managed.md · JSON https://www.anchorterminal.com/api/v1/tools/snowflake-managed.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### 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 55\n- Payments \u0026 pricing, 60 against 35\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\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### Snowflake-managed MCP server (C)\n\nGood for: A company that already keeps its data in Snowflake and wants outside MCP clients to query it under existing roles, best through one Cortex Agent tool.\n\nAhead on:\n- Agent ergonomics, 46 against 39\n- Security \u0026 auth, 77 against 54\n- Transparency \u0026 trust, 84 against 76\n\nWatch for: No rate limits for the MCP endpoint and no JSON-RPC error codes were found in the reviewed documentation\n\n\n## Score by category\n\n| Category | Weight | Redis MCP | Snowflake-managed MCP server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 62 | 55 | Redis MCP +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 64 | 61 | Redis MCP +3 |\n| Agent ergonomics | 13% (16.2 this run) | 39 | 46 | Snowflake-managed MCP server +7 |\n| Security \u0026 auth | 14% (17.5 this run) | 54 | 77 | Snowflake-managed MCP server +23 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 35 | Redis MCP +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 57 | 55 | Redis MCP +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 76 | 84 | Snowflake-managed MCP server +8 |\n| Negative events | ≤15 | -2 | -2 | |\n| **Total** | | **55.7 · C** | **56.4 · C** | |\n\n## Facts side by side\n\n| Fact | Redis MCP | Snowflake-managed MCP server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Redis | Snowflake Inc. |\n| Hosted endpoint | no (local only) | no (local only) |\n| Transports | stdio | Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Pay per use |\n| x402 | no | no |\n| Licence | MIT | Proprietary service under Snowflake's terms of service |\n| Tools exposed | 53 | none |\n| Read-only variant documented | yes | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.redis/mcp-redis` | not listed |\n| Last release | 2026-08-04 | 2026-08-20 |\n| Terms last updated | no document linked | 2026-04-16 |\n| Privacy policy last updated | no document linked | 2026-07-01 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | not found in the text |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | yes |\n| Popularity | 633 stars, 3.6k PyPI/wk | none |\n\n## Verdicts\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**Snowflake-managed MCP server.** Tools are governed by Snowflake roles, the SQL tool is read-only by default, and sign-in runs through Snowflake OAuth or a company identity provider. No rate limits or tool-call error codes were found in the reviewed documentation, and a person must create the account, the server object and the OAuth integration before an agent can connect.\n\n## Before you call either\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### Snowflake-managed MCP server\n\n1. Send `Accept: application/json, text/event-stream` and read `tools/call` results as an SSE stream that ends with `data: [DONE]`\n2. Write the account hostname with hyphens, not underscores, or some clients fail to connect\n3. Check the user's `DEFAULT_ROLE` and `DEFAULT_WAREHOUSE` first. Clients that request `session:role:all` get the default role, and a missing warehouse stops the session starting\n4. Keep SQL results narrow. Responses over 250 KB are truncated with no paging, and agent tool responses can pass 200 KB\n5. Treat `invalid_client` from `/oauth/token-request` as a possible network policy block as well as a wrong credential\n\n## Questions\n\n### Which is better for AI agents, Redis MCP or Snowflake-managed MCP server?\n\nSnowflake-managed MCP server and Redis MCP score within a point of each other on agent readiness, 56.4 (C) and 55.7 (C). Redis MCP leads on reliability and payments \u0026 pricing.\n\n### Do Redis MCP and Snowflake-managed MCP server need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Redis MCP and Snowflake-managed MCP server without installing anything?\n\nRedis MCP runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Snowflake-managed MCP server.\n\n### Are Redis MCP and Snowflake-managed MCP server open source?\n\nRedis MCP is open source (MIT). No open-source release is listed for Snowflake-managed MCP server.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.json, and with the fewest tokens: https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"redis-mcp\", \"b\": \"snowflake-managed\"}`. From a terminal: `anchor compare redis-mcp snowflake-managed`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/redis-mcp.json and https://www.anchorterminal.com/api/v1/tools/snowflake-managed.json\n\n## Other comparisons with Redis MCP or Snowflake-managed MCP server\n\n- [Redis MCP vs Supabase API + MCP](https://www.anchorterminal.com/compare/redis-mcp-vs-supabase-mcp.md)\n- [ClickHouse MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/clickhouse-mcp-server-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/planetscale-mcp-vs-snowflake-managed.md)\n- [Postgres MCP Pro vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-mcp-pro-vs-snowflake-managed.md)\n- [PostgreSQL (archived MCP reference server) vs Snowflake-managed MCP server](https://www.anchorterminal.com/compare/postgres-reference-server-archived-vs-snowflake-managed.md)\n- [Snowflake-managed MCP server vs Supabase API + MCP](https://www.anchorterminal.com/compare/snowflake-managed-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 Snowflake-managed MCP server](https://www.anchorterminal.com/compare/mongodb-mcp-vs-snowflake-managed.md)\n- [PlanetScale MCP Server vs Redis MCP](https://www.anchorterminal.com/compare/planetscale-mcp-vs-redis-mcp.md)\n- [Postgres MCP Pro vs Redis MCP](https://www.anchorterminal.com/compare/postgres-mcp-pro-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- [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": "Redis MCP vs Snowflake-managed MCP server", "url": "" } ], "description": "Snowflake-managed and Redis MCP score within a point of each other for databases, 56.4 and 55.7 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Redis MCP C 55.7", "Snowflake-managed MCP server C 56.4", "scores" ], "h1": "Redis MCP vs Snowflake-managed MCP server", "image": "https://www.anchorterminal.com/assets/og/compare-redis-mcp-vs-snowflake-managed.png", "path": "/compare/redis-mcp-vs-snowflake-managed", "published": "2026-10-01", "section": "tools", "title": "Redis MCP vs Snowflake-managed for AI agents (2026) | Anchor Terminal", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/redis-mcp-vs-snowflake-managed" }, "tokens": { "markdown": 2400, "slim": 680 }, "version": 1 }