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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldMetabase MCPShortlist candidateSupabase MCPMCP100 Recommended
Task fit
Best for
  • Let AI clients query and build against a user's own Metabase instance under existing permissions
  • Metabase users who need to let ai clients query and build against a user's own metabase instance under existing 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
  • The endpoint is instance-specific: https://{your-metabase.example.com}/api/metabase-mcp. Query, SQL, write, and delivery scopes can expose or mutate sensitive analytics content; OAuth never grants more than the connecting user's Metabase permissions.
  • 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 endpoint is instance-specific: https://{your-metabase.example.com}/api/metabase-mcp. Query, SQL, write, and delivery scopes can expose or mutate sensitive analytics content; OAuth never grants more than the connecting user's Metabase permissions.
  • 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

Metabase · 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 starsNot documented

2,919

GitHub stars · checked 2026-09-24T04:16:20.864000Z

Package downloads / 30 daysNo reliable download data

406,869

package downloads / 30 days · checked 2026-09-24T04:17:50.300000Z

Shared repository stars

49,767

Shared repository stars (not MCP-specific) · checked 2026-10-20

Not documented
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth 2.0 through the Metabase instance's embedded OAuth 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.
CostThe built-in MCP has no separately documented fee. Metabase has free Open Source and paid hosted/commercial plans; certain AI/usage features have separate usage pricing.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.
PermissionsThe MCP is scoped to the connecting user's Metabase permissions. Capability scopes include content read/write, query execution, SQL execution and delivery writes depending on authorization.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 handlingNot documented in the reviewed sources. The reviewed Metabase MCP page does not provide an MCP-specific retention or training statement. Queries can expose data accessible through the user's Metabase permissions.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
  • Official Metabase documentation establishes the built-in MCP server and distinguishes it from community implementations. Exact runtime tool inventory/context footprint remains instance/version dependent.
  • 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 contextDepending on granted scopes, the MCP can run queries/SQL and create, edit or trash Metabase content, potentially exposing sensitive analytics or modifying shared dashboards/questions.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 review2026-10-192026-09-05
Candidate evidence2026-10-202026-09-24T04:25:05.554391Z

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

Read the evidence method →