Ext Ops Panel
Open dashboard
Comparison

CockroachDB vs dbt-cloud-webhooks

CockroachDB is an MCP server published by amineelkouhen. Marketplaces we read that list it: 1 (Docker MCP Catalog). dbt-cloud-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-06. 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
MarketplaceCockroachDBdbt-cloud-webhooks
Docker MCP Catalog Listed
Version: sha256:4863594a246c
Forks (GitHub): 10
Pulls (Docker Hub): 12 326
Stars (Docker Hub): 1
Stars (GitHub): 12
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
No figure published
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

CockroachDB vs dbt-cloud-webhooks
FactCockroachDBdbt-cloud-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)12No figure on GitHub
Pulls (Docker Hub) (differs)12 326No figure on Docker Hub
Forks (GitHub) (differs)10No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cockroachdb)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)29Not published
Environment variables it asks for (differs)9, secrets among them: 1Not published
LicenceMITMIT
Repository (differs)github.com/amineelkouhen/mcp-cockroachdbgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-06

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

CockroachDB

In its own words, on Docker MCP Catalog:

Enable AI agents to manage, monitor, and query CockroachDB using natural language. Perform complex database operations, cluster management, and query execution seamlessly through AI-driven workflows. Integrate effortlessly with MCP clients for scalable and high-performance data operations.

dbt-cloud-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify dbt Cloud webhooks. Use when setting up dbt Cloud webhook handlers, debugging dbt Cloud Authorization header signature verification, or handling job run events like job.run.started, job.run.completed, and job.run.errored.

How to run each

CockroachDB As a local MCP server: Docker image

Claude Code
claude mcp add --env "CRDB_PWD=<YOUR_CRDB_PWD>" --transport stdio cockroachdb -- docker run -i --rm -e CRDB_PWD mcp/cockroachdb

Requires: CRDB_PWD (secret)

dbt-cloud-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install dbt-cloud-webhooks@webhook-skills

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

Tools each declares

The marketplaces of dbt-cloud-webhooks publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of dbt-cloud-webhooks publish no settings it asks for, so we do not compare settings.

What it can do: CockroachDB · What it can do: dbt-cloud-webhooks · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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