Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Supabase MCPRedis MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedFirecrawl MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Supabase MCPMCP100 Selected	Redis MCPMCP100 Selected
Task fit
Best for	Inspecting one Supabase project's schema, logs, advisors, and docs Development environments using project-scoped read-only access Teams that understand database and deployment consequences	Inspecting and manipulating Redis strings, hashes, lists, sets, sorted sets, streams, JSON, and search indexes Development workflows using a dedicated local or test Redis database Redis documentation search and operational investigation
Not ideal for	Production database administration by an unattended agent Users needing only public Supabase documentation Organizations unable to grant Supabase OAuth access to an MCP client	Read-only analytics when write-capable Redis tools cannot be disabled or constrained by ACL Production databases shared with latency-sensitive applications
Avoid when	The server would be left organization-wide rather than project-scoped Write-capable SQL, migrations, functions, branches, or storage changes cannot be human-approved Production secrets or customer records could be returned to the model	The Redis credential grants unrestricted access to production keys TLS certificate verification is disabled for a remote Redis connection The agent must not read, overwrite, publish, expire, or delete Redis data
Provenance
Provenance details	First-party MCP Supabase · Publisher source ↗	First-party MCP Redis · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 14, 2026 Package: Not documented	Repo: Aug 5, 2026 Package: Aug 5, 2026
Popularity evidence
GitHub stars	2,863 GitHub stars · checked 2026-08-14T18:46:26.000Z	568 GitHub stars · checked 2026-08-14T18:46:26.000Z
30-day package downloads	No reliable download data	22,058 PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z
External adoption evidence	github: repository stars: 2,863Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗	npm: package downloads: 12,402Exact attributable signal.npm: package downloads · Admission snapshot · checked 2026-07-29T17:30:00.000ZEvidence source ↗ github: repository stars: 568Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗ PyPI Stats: package downloads: 22,058Non-comparable contextual signal.PyPI Stats: package downloads · Provider last month · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Hosted MCP uses browser OAuth and grants organization access to the MCP client. Project scope, read-only mode, and feature groups are encoded in URL query parameters.	Supports Redis username/password URLs, individual credential options, TLS through `rediss://`, CA certificate verification, cluster mode, and Microsoft Entra ID authentication for Azure Managed Redis.
Cost	The MCP server is open source; normal Supabase plan, database, branch, Edge Function, storage, and usage charges apply. Branching and some storage operations require a paid plan.	The first-party server is open source and the PyPI package documents no MCP usage fee. Redis Cloud, infrastructure, network, container, and AI-client costs remain separate.
Permissions	Without project_ref the hosted server can access all projects in the authorized organization. With project_ref it is limited to one project. read_only=true uses a read-only Postgres user for SQL and disables listed mutation tools. Feature groups can further narrow exposed tools.	The server can read and write Redis keys and data structures, operate streams and pub/sub, manage search indexes, and inspect server information according to the connected Redis user's ACL. Redis ACL configuration is the effective permission boundary.
Data handling	Enabled tools may return schemas, table data from executed queries, logs, security/performance advisors, project metadata, publishable keys, types, and Edge Function source. Hosted mode sends tool requests through Supabase's MCP service.	The stdio server runs locally and sends Redis query inputs and returned key values to the connected MCP client. It connects directly to the configured Redis deployment. Credentials can be supplied in a URI, CLI arguments, or environment variables; avoid embedding them in shareable config and logs.
Limitations
Tradeoffs	Project scoping removes account-level tools but materially reduces blast radius. Read-only mode disables mutations but also removes migration, deployment, branch, and storage configuration workflows. Branching and some storage capabilities require paid plans; the server is pre-1.0 and may change.	The server supports a wide Redis data surface, which is useful but makes the database credential the primary security boundary. Running through uvx is simple but `@latest` is mutable; pin a reviewed release for repeatable deployments. Connection URLs are convenient but can expose usernames and passwords in process arguments or client configuration.
Risk context	Unscoped or write-enabled access can affect every project in an organization, execute SQL, apply migrations, deploy functions, or manage branches. Always set project_ref and read_only=true first, minimize feature groups, and avoid production data.	A broad Redis tool set can expose or mutate application state, sessions, queues, cached records, and vector data. Use a dedicated database, a narrowly scoped ACL user, verified TLS, pinned releases, and backups. This review does not claim MCP100 execution testing.
Evidence date
Editorial review	2026-07-24	2026-07-24
Candidate evidence	2026-08-14T18:46:26.000Z	2026-08-14T18:46:26.000Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →