Metabase vs coupler-capability
Metabase is an MCP server published by easecloudio. Marketplaces we read that list it: 2 (Docker MCP Catalog, npm registry (MCP servers)). coupler-capability is a plugin bundle for AI coding tools published by coupler-io. Marketplaces we read that list it: 1 (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
| Marketplace |   Metabase |  coupler-capability |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:02e633ae77a1 Forks (GitHub): 25 Pulls (Docker Hub): 51 995 Stars (Docker Hub): 3 Stars (GitHub): 83 Not marked · First seen |
Not listed |
| 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 |
| Community marketplace coupler-io/skills | Not listed | Listed Version: not stated Forks (GitHub): 11 Stars (GitHub): 39 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 | coupler-capability |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 83 (better) | 39 (worse) |
| Pulls (Docker Hub) (differs) | 51 995 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 25 (better) | 11 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/metabase) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/easecloudio/mcp-metabase-server | github.com/coupler-io/skills |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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.
coupler-capability
Core Coupler.io MCP capabilities — create dataflows, build Custom GAQL sources, generate dataset context, refine prompts, generate reports.
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)
coupler-capability As a Claude Code plugin
/plugin marketplace add coupler-io/skills
/plugin install coupler-capability@coupler-io-skillsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of coupler-capability publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of coupler-capability publish no settings it asks for, so we do not compare settings.
What it can do: Metabase · What it can do: coupler-capability · 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 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.