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

Atlan Data CatalogSupabase 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 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 SelectedExcel MCP ServerMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Atlan Data CatalogWatchlist candidate	Supabase MCPMCP100 Selected
Task fit
Best for	Atlan customers who want governed catalog search, lineage, SQL/context and metadata curation under existing Atlan permissions.	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
Not ideal for	Organizations without clearly governed Atlan roles/personas or that cannot expose catalog metadata to an external AI client.	Production database administration by an unattended agent Users needing only public Supabase documentation Organizations unable to grant Supabase OAuth access to an MCP client
Avoid when	Do not use an over-privileged service-account/persona when a narrower user role can satisfy the workflow.	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
Provenance
Provenance details	First-party MCP endpoint:https: · Publisher source ↗	First-party MCP Supabase · Publisher source ↗
Maintenance
Maintenance details	Stale Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Not documented
Popularity evidence
GitHub stars	Not documented	2,863 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	484,999 package downloads / 30 days · checked 2026-09-08
Client coverage
Client coverage details	Not documented	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Publisher supports authenticated tenant access via OAuth and supported API/service tokens.	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. Enterprise-managed authentication is GA for eligible Team and Enterprise organizations. Access remains scoped to each user's existing Supabase role and permissions.
Cost	Atlan plan/entitlement and AI-provider costs apply.	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.
Permissions	Inherits Atlan persona/role/domain permissions; service-account tokens are tied to a defined persona according to publisher docs.	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.
Data handling	Atlan states MCP retrieval is real-time without an intermediate MCP cache and that MCP itself does not send customer data to an LLM; the connected AI client/provider still receives whatever tool results the user sends into that conversation.	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.
Limitations
Tradeoffs	Promising signal, but it ranks below the current Selected/Watchlist admission cohort on maturity, uniqueness, publisher trust, security clarity, or MCP-native evidence.	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.
Risk context	Sensitive enterprise metadata and any authorized curation writes remain the key governance concerns.	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.
Evidence date
Editorial review	2026-09-13T00:00:00Z	2026-09-05
Candidate evidence	2026-09-13T00:00:00Z	2026-09-05T00:00:00.000Z

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

Read the evidence method →