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

GreptimeDB MCPSupabase MCP

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

Comparable alternatives

AWS Documentation MCPMCP100 SelectedAsana MCPMCP100 SelectedAtlassian Remote MCPMCP100 SelectedAzure MCP ServerMCP100 SelectedCanva Dev MCPMCP100 SelectedChrome DevTools MCPMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	GreptimeDB MCPWatchlist candidate	Supabase MCPMCP100 Selected
Task fit
Best for	Read-oriented observability/database exploration with GreptimeDB Teams that value masking/audit controls and can keep the server narrowly scoped	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 looking for a mature broadly adopted MCP ecosystem Deployments that need extensive write/admin capabilities	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	The deployment disables documented read-only/masking safeguards Sensitive data masking and audit settings have not been validated	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 GreptimeDB / GreptimeTeam · Publisher source ↗	First-party MCP Supabase · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Aug 14, 2026 Package: Not documented
Popularity evidence
GitHub stars	27 GitHub stars · checked 2026-09-11	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	Uses GreptimeDB connection/auth credentials supplied to the server.	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; GreptimeDB service/infrastructure 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	Database queries are read-only by default through an application security gate; pipeline/dashboard management tools can write through the HTTP API. GREPTIMEDB_ALLOW_WRITE can bypass the SQL gate and must remain false for production.	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	Queries can expose GreptimeDB observability/time-series data; masking/audit configuration should be validated for sensitive fields.	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	Safer defaults reduce database risk Smaller ecosystem means less production evidence and fewer independent deployments to learn from	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	Medium to high. Default SQL controls, masking, and audit are strong, but pipeline/dashboard management is mutating and enabling write mode allows destructive SQL. A current SDK 2.x migration issue also needs compatibility monitoring.	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-11	2026-09-05
Candidate evidence	2026-09-11T00:00:00.000Z	2026-09-05T00:00:00.000Z

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

Read the evidence method →