Ext Ops Panel
Open dashboard
Comparison

CockroachDB vs MigraFlow - Database Migration AI

CockroachDB is an MCP server published by amineelkouhen. Marketplaces we read that list it: 1 (Docker MCP Catalog). MigraFlow - Database Migration AI is an MCP server published by wmeireles. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceCockroachDBMigraFlow - Database Migration AI
Docker MCP Catalog Listed
Version: sha256:4863594a246c
Forks (GitHub): 10
Pulls (Docker Hub): 11 973
Stars (Docker Hub): 1
Stars (GitHub): 12
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (PyPI): 56
Downloads/week (PyPI): 12
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 MigraFlow - Database Migration AI
FactCockroachDBMigraFlow - Database Migration AI
Marketplaces that list it11
Stars (GitHub) (differs)12No figure on GitHub
Pulls (Docker Hub) (differs)11 973No figure on Docker Hub
Forks (GitHub) (differs)10No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/cockroachdb)On your machine (migraflow-mcp)
Transportstdiostdio
Tools it declares (differs)29Not published
Environment variables it asks for (differs)9, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/amineelkouhen/mcp-cockroachdbgithub.com/wmeireles/api_migraflow
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

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.

MigraFlow - Database Migration AI

In its own words, on Official MCP Registry:

AI-powered database migration. Analyze schemas, generate SQL, calculate risks.

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)

MigraFlow - Database Migration AI As a local MCP server: PyPI package

Claude Code
claude mcp add --env "MIGRAFLOW_API_KEY=<YOUR_MIGRAFLOW_API_KEY>" --transport stdio migraflow-mcp -- uvx migraflow-mcp

Requires: MIGRAFLOW_API_KEY (secret)

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

Tools each declares

The marketplaces of MigraFlow - Database Migration AI publish no list of tools, so we do not compare tools.

Settings each asks for

Only CockroachDB asks for

  • CRDB_DATABASE
  • CRDB_HOST
  • CRDB_PORT
  • CRDB_PWD (secret)
  • CRDB_SSL_CA_PATH
  • CRDB_SSL_CERTFILE
  • CRDB_SSL_KEYFILE
  • CRDB_SSL_MODE
  • CRDB_USERNAME

Only MigraFlow - Database Migration AI asks for

  • MIGRAFLOW_API_KEY (secret)
  • MIGRAFLOW_API_URL

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: CockroachDB · What it can do: MigraFlow - Database Migration AI · 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.

Where the data comes from: how the catalog is built