Metabase vs KrystalView Analytics
Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 1 (Docker MCP Catalog). KrystalView Analytics is an MCP server published by KrystalView. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
| Marketplace |   Metabase |  KrystalView Analytics |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02e633ae77a1 Forks (GitHub): 25 Pulls (Docker Hub): 50 709 Stars (Docker Hub): 3 Stars (GitHub): 82 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.6 Downloads/month (PyPI): 252 Downloads/week (PyPI): 50 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Metabase | KrystalView Analytics |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 82 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 50 709 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 25 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/metabase) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/easecloudio/mcp-metabase-server | github.com/krystalview/krystalview-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 27 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
A comprehensive MCP server for Metabase with 70+ tools.
KrystalView Analytics
Read-only MCP access to sessions, funnels, campaigns, errors, live visitors, and anomalies.
How to run each
Metabase As a local MCP server: Docker image
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/metabaseRequires: METABASE_API_KEY (secret), METABASE_PASSWORD (secret)
KrystalView Analytics As a remote MCP server
claude mcp add --transport http krystalview https://krystalview.com/mcpRequires: KRYSTALVIEW_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only KrystalView Analytics has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of KrystalView Analytics publish no list of tools, so we do not compare tools.
Settings each asks for
Only Metabase asks for
METABASE_API_KEY (secret)METABASE_PASSWORD (secret)METABASE_URLMETABASE_USERNAME
Only KrystalView Analytics asks for
KRYSTALVIEW_API_KEY (secret)KRYSTALVIEW_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Metabase · What it can do: KrystalView Analytics · 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.