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 MCPclickhouse

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	clickhouseMCP100 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	High-volume analytical database exploration and query workflows for ClickHouse deployments.
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	Teams outside the publisher ecosystem or without least-privilege credentials
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 connected identity is broader than the task requires Tool calls cannot be reviewed before consequential mutations
Provenance
Provenance details	First-party MCP Supabase · Publisher source ↗	First-party MCP ecosystem:clickhouse · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 14, 2026 Package: Not documented	Repo: Aug 5, 2026 Package: Not documented
Popularity evidence
GitHub stars	2,863 GitHub stars · checked 2026-08-14T18:46:26.000Z	851 GitHub stars · 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 ↗	github: repository stars: 851Exact attributable signal.github: repository stars · Admission snapshot · 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.	The official server uses configured ClickHouse connection credentials and supports secure deployment settings.
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 MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
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.	ClickHouse credentials and database grants define accessible schemas and queries; the server defaults to read-only behavior.
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.	Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive data & databases information.
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.	Queries can expose large or sensitive datasets and consume cluster capacity even when writes are disabled.
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.	Queries can expose large or sensitive datasets and consume cluster capacity even when writes are disabled. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.
Evidence date
Editorial review	2026-07-24	2026-07-30
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 →