Ext Ops Panel
Open dashboard
Comparison

dbt-toolkit vs io.github.us-all/dbt

dbt-toolkit is a plugin bundle for AI coding tools published by rishav1305. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.us-all/dbt is an MCP server published by us-all. 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

Where each is published
Marketplacedbt-toolkitio.github.us-all/dbt
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.7
Downloads/month (npm): 199
Downloads/week (npm): 28
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

dbt-toolkit vs io.github.us-all/dbt
Factdbt-toolkitio.github.us-all/dbt
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@us-all/dbt-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published27, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)19Not a bundle
Licence (differs)BUSL-1.1Not stated
Repository (differs)github.com/rishav1305/dbt-toolkitgithub.com/us-all/dbt-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

dbt-toolkit

In its own words, on Claude Code: claude-plugins-community:

Workflow-oriented dbt project management for Claude Code

io.github.us-all/dbt

In its own words, on Official MCP Registry:

dbt MCP — manifest/run_results/sources/catalog parsing + DQ result tables (BigQuery/Postgres)

How to run each

dbt-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dbt-toolkit@claude-community

io.github.us-all/dbt As a local MCP server: npm package

Claude Code
claude mcp add --env "DBT_PROJECT_DIR=<YOUR_DBT_PROJECT_DIR>" --env "PG_CONNECTION_STRING=<YOUR_PG_CONNECTION_STRING>" --transport stdio dbt -- npx -y @us-all/dbt-mcp

Requires: DBT_PROJECT_DIR, PG_CONNECTION_STRING (secret)

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

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 dbt-toolkit publish no settings it asks for, so we do not compare settings.

What it can do: dbt-toolkit · What it can do: io.github.us-all/dbt · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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