Ext Ops Panel
Open dashboard
Comparison

Metabase vs CustomerDashboard

Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 1 (Docker MCP Catalog). CustomerDashboard is an MCP server published by customerdashboard.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceMetabaseCustomerDashboard
Docker MCP Catalog Listed
Version: sha256:02e633ae77a1
Forks (GitHub): 25
Pulls (Docker Hub): 50 904
Stars (Docker Hub): 3
Stars (GitHub): 82
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Metabase vs CustomerDashboard
FactMetabaseCustomerDashboard
Marketplaces that list it11
Stars (GitHub) (differs)82No figure on GitHub
Pulls (Docker Hub) (differs)50 904No figure on Docker Hub
Forks (GitHub) (differs)25No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/metabase)Remote server (app.customerdashboard.io/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)4, secrets among them: 2Not published
Licence (differs)MITNot stated
Repository (differs)github.com/easecloudio/mcp-metabase-serverNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 19 h ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Metabase

In its own words, on Docker MCP Catalog:

A comprehensive MCP server for Metabase with 70+ tools.

CustomerDashboard

In its own words, on Official MCP Registry:

Build dashboards on your own data, including multi-customer views with per-customer login.

How to run each

Metabase As a local MCP server: Docker image

Claude Code
claude mcp add --env "METABASE_API_KEY=<YOUR_METABASE_API_KEY>" --env "METABASE_PASSWORD=<YOUR_METABASE_PASSWORD>" --transport stdio metabase -- docker run -i --rm -e METABASE_API_KEY -e METABASE_PASSWORD mcp/metabase

Requires: METABASE_API_KEY (secret), METABASE_PASSWORD (secret)

CustomerDashboard As a remote MCP server

Claude Code
claude mcp add --transport http customerdashboard https://app.customerdashboard.io/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only CustomerDashboard has a remote endpoint we check. How we check endpoints

Tools each declares

Only Metabase has

  • add_card_to_dashboard
  • create_card
  • create_collection
  • create_database_connection
  • create_permission_group
  • create_user
  • delete_card
  • execute_card
  • execute_query
  • get_dashboard_cards
  • get_database_schema
  • get_database_sync_status
Show the remaining 12
  • get_database_tables
  • list_cards
  • list_collections
  • list_databases
  • list_permission_groups
  • list_users
  • remove_card_from_dashboard
  • search_content
  • sync_database_schema
  • test_database_connection
  • update_card
  • update_dashboard_card

Only CustomerDashboard has

  • add_customer
  • add_customer_user
  • add_data_source
  • create_view
  • create_widget
  • delete_customer
  • delete_customer_user
  • delete_data_source
  • delete_view
  • delete_widget
  • explain_customer_filtering
  • get_account
Show the remaining 26
  • get_dashboard
  • get_dashboard_share_url
  • get_data_source
  • get_data_source_schema
  • get_platform_overview
  • get_started
  • list_customers
  • list_data_sources
  • list_plans_and_limits
  • list_supported_data_connectors
  • list_views
  • list_widget_types
  • list_widgets
  • publish_dashboard
  • reorder_views
  • run_query_preview
  • set_dashboard_formatting
  • set_dashboard_theme
  • set_widget_layout
  • test_data_source_connection
  • unpublish_dashboard
  • update_customer
  • update_data_source
  • update_view
  • update_widget
  • validate_customer_filtering

Both have

  • create_dashboard
  • delete_dashboard
  • list_dashboards
  • update_dashboard

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (CustomerDashboard as of 2026-10-12). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of CustomerDashboard publish no settings it asks for, so we do not compare settings.

What it can do: Metabase · What it can do: CustomerDashboard · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built