Ext Ops Panel
Open dashboard
Comparison

Agent-Native Analytics vs io.github.enessari/metabase-ai-assistant

Agent-Native Analytics is an MCP server published by BuilderIO. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.enessari/metabase-ai-assistant is an MCP server published by enessari. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-13. 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
MarketplaceAgent-Native Analyticsio.github.enessari/metabase-ai-assistant
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 707
Stars (GitHub): 7 691
Not marked · First seen
Listed
Version: 3.2.0
Downloads/month (npm): 186
Downloads/week (npm): 71
Forks (GitHub): 11
Stars (GitHub): 47
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

Agent-Native Analytics vs io.github.enessari/metabase-ai-assistant
FactAgent-Native Analyticsio.github.enessari/metabase-ai-assistant
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 691 (better)47 (worse)
Forks (GitHub) (differs)707 (better)11 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (analytics.agent-native.com/mcp)On your machine (metabase-ai-assistant)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published9, secrets among them: 3
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/builderio/agent-nativegithub.com/enessari/metabase-ai-assistant
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 14 h ago, requires authenticationno remote endpoint we check

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

Agent-Native Analytics

In its own words, on Official MCP Registry:

Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts

io.github.enessari/metabase-ai-assistant

In its own words, on Official MCP Registry:

MCP Server for Metabase - 111 tools for SQL generation, dashboards & PostgreSQL

How to run each

Agent-Native Analytics As a remote MCP server

Claude Code
claude mcp add --transport http agent-native-analytics https://analytics.agent-native.com/mcp

io.github.enessari/metabase-ai-assistant As a local MCP server: npm package

Claude Code
claude mcp add --env "DATABASE_PASSWORD=<YOUR_DATABASE_PASSWORD>" --env "METABASE_API_KEY=<YOUR_METABASE_API_KEY>" --env "METABASE_PASSWORD=<YOUR_METABASE_PASSWORD>" --env "METABASE_URL=<YOUR_METABASE_URL>" --transport stdio metabase-ai-assistant -- npx -y metabase-ai-assistant

Requires: DATABASE_PASSWORD (secret), METABASE_API_KEY (secret), METABASE_PASSWORD (secret), METABASE_URL

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

Only Agent-Native Analytics has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Agent-Native Analytics publish no settings it asks for, so we do not compare settings.

What it can do: Agent-Native Analytics · What it can do: io.github.enessari/metabase-ai-assistant · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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