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

ChromaSupabase MCP

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

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedPlaywright MCPMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	ChromaShortlist candidate	Supabase MCPMCP100 Recommended
Task fit
Best for	Teams using Chroma that want MCP-native collection management and retrieval.	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	Users who need a broadly proven, low-risk, fully mature Recommended-grade integration today.	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	Avoid high-impact or sensitive production use unless the documented authentication, permissions, rollback, and data handling match your environment.	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 github:chroma-core · Publisher source ↗	First-party MCP Supabase · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Sep 24, 2026 Package: Sep 21, 2026
Popularity evidence
GitHub stars	601 GitHub stars · checked 2026-10-21	2,919 GitHub stars · checked 2026-09-24T04:16:20.864000Z
Package downloads / 30 days	125,570 package downloads / 30 days · checked 2026-10-21	406,869 package downloads / 30 days · checked 2026-09-24T04:17:50.300000Z
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	Chroma Cloud uses an API key; self-hosted HTTP can use custom authentication credentials; local modes may have no network auth.	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	Open-source server; Chroma Cloud, embedding providers and infrastructure may be billable.	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	Can read and mutate collections/data available to the configured Chroma client.	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	Vector/document content is stored in the configured local, self-hosted, or Chroma Cloud backend and exposed to the connected AI client.	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	Write/index-poisoning risk plus tenant/auth configuration need stronger MCP-specific production 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	Write/index-poisoning risk plus tenant/auth configuration need stronger MCP-specific production evidence.	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-10-21	2026-09-05
Candidate evidence	2026-10-21T00:00:00Z	2026-09-24T04:25:05.554391Z

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

Read the evidence method →