Ext Ops Panel
Open dashboard
Comparison

Metabase vs io.github.grafana/mcp-grafana

Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 2 (Docker MCP Catalog, npm registry (MCP servers)). io.github.grafana/mcp-grafana is an MCP server published by grafana. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-30. 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
MarketplaceMetabaseio.github.grafana/mcp-grafana
Docker MCP Catalog Listed
Version: sha256:02e633ae77a1
Forks (GitHub): 25
Pulls (Docker Hub): 51 958
Stars (Docker Hub): 3
Stars (GitHub): 83
Not marked · First seen 		Listed
Version: sha256:9362bcf6aa0e
Forks (GitHub): 482
Pulls (Docker Hub): 1 122 985
Stars (Docker Hub): 22
Stars (GitHub): 3 627
Not marked · First seen
npm registry (MCP servers) Listed
Version: 1.3.0
Downloads/month (npm): 3 272
Downloads/week (npm): 1 313
Forks (GitHub): 25
Stars (GitHub): 83
Not marked · First seen 		Not listed
Official MCP Registry Not listed Listed
Version: v2.1.1
Forks (GitHub): 482
Stars (GitHub): 3 627
Not marked · First seen
Claude Code: claude-plugins-official Not listed Listed
Version: 0.2.0
Forks (GitHub): 5
Stars (GitHub): 19
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.2.0
Forks (GitHub): 5
Stars (GitHub): 19
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 io.github.grafana/mcp-grafana
FactMetabaseio.github.grafana/mcp-grafana
Marketplaces that list it (differs)2 (worse)5 (better)
Stars (GitHub) (differs)83 (worse)3 627 (better)
Pulls (Docker Hub) (differs)51 958 (worse)1 122 985 (better)
Forks (GitHub) (differs)25 (worse)482 (better)
Last release (differs)Not published2026-10-29
Where it runs (differs)On your machine (mcp/metabase)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)2865
Environment variables it asks for (differs)4, secrets among them: 27, secrets among them: 2
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITApache-2.0
Repository (differs)github.com/easecloudio/mcp-metabase-servergithub.com/grafana/mcp-grafana
Changes in the last 7 days (differs)04
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago, requires a key

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.

io.github.grafana/mcp-grafana

In its own words, on Official MCP Registry:

An MCP server giving access to Grafana dashboards, data and more.

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)

io.github.grafana/mcp-grafana As a remote MCP server

Claude Code
claude mcp add --transport http mcp-grafana https://mcp.grafana.com/mcp

Requires: GRAFANA_PASSWORD (secret), GRAFANA_SERVICE_ACCOUNT_TOKEN (secret), GRAFANA_URL

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

Only io.github.grafana/mcp-grafana has a remote endpoint we check. How we check endpoints

Tools each declares

Only Metabase declares

  • add_card_to_dashboard
  • create_card
  • create_collection
  • create_dashboard
  • create_database_connection
  • create_permission_group
  • create_user
  • delete_card
  • delete_dashboard
  • execute_card
  • execute_query
  • get_dashboard_cards
Show the remaining 15
  • get_database_schema
  • get_database_sync_status
  • get_database_tables
  • list_cards
  • list_collections
  • list_dashboards
  • 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 io.github.grafana/mcp-grafana declares

  • add_activity_to_incident
  • alerting_manage_routing
  • alerting_manage_rules
  • analyze_loki_labels
  • check_datasources_health
  • create_annotation
  • create_datasource
  • create_folder
  • create_incident
  • create_snapshot
  • delete_snapshot
  • find_error_pattern_logs
Show the remaining 52
  • find_slow_requests
  • generate_deeplink
  • get_alert_group
  • get_annotation_tags
  • get_annotations
  • get_assertions
  • get_current_oncall_users
  • get_dashboard_by_uid
  • get_dashboard_panel_queries
  • get_dashboard_property
  • get_dashboard_summary
  • get_datasource
  • get_incident
  • get_oncall_shift
  • get_panel_image
  • get_plugin
  • get_sift_analysis
  • get_sift_investigation
  • get_snapshot
  • grafana_api_request
  • install_plugin
  • list_alert_groups
  • list_datasources
  • list_incidents
  • list_loki_label_names
  • list_loki_label_values
  • list_oncall_schedules
  • list_oncall_teams
  • list_oncall_users
  • list_prometheus_label_names
  • list_prometheus_label_values
  • list_prometheus_metric_metadata
  • list_prometheus_metric_names
  • list_provisioning_repositories
  • list_pyroscope_label_names
  • list_pyroscope_label_values
  • list_pyroscope_profile_types
  • list_sift_investigations
  • list_snapshots
  • query_loki_logs
  • query_loki_patterns
  • query_loki_stats
  • query_prometheus
  • query_prometheus_histogram
  • query_pyroscope
  • search_dashboards
  • search_folders
  • search_plugin_information
  • suggest_loki_alloy_label_config
  • update_annotation
  • update_datasource
  • validate_provisioning_file

Both declare

  • update_dashboard

Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Metabase asks for

  • METABASE_API_KEY (secret)
  • METABASE_PASSWORD (secret)
  • METABASE_URL
  • METABASE_USERNAME

Only io.github.grafana/mcp-grafana asks for

  • GRAFANA_API_KEY (secret)
  • GRAFANA_EXTRA_HEADERS
  • GRAFANA_FORWARD_HEADERS
  • GRAFANA_ORG_ID
  • GRAFANA_PASSWORD (secret)
  • GRAFANA_SERVICE_ACCOUNT_TOKEN (secret)
  • GRAFANA_URL
  • GRAFANA_USERNAME

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Metabase · What it can do: io.github.grafana/mcp-grafana · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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