Ext Ops Panel
Open dashboard
Comparison

Neon vs Liquibase Changelog MCP Server

Neon is an MCP server published by neondatabase. Marketplaces we read that list it: 1 (Docker MCP Catalog). Liquibase Changelog MCP Server is an MCP server published by liquibase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceNeonLiquibase Changelog MCP Server
Docker MCP Catalog Listed
Version: sha256:fab32eb73fb0
Forks (GitHub): 133
Pulls (Docker Hub): 23 842
Stars (Docker Hub): 3
Stars (GitHub): 656
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

Neon vs Liquibase Changelog MCP Server
FactNeonLiquibase Changelog MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)656No figure on GitHub
Pulls (Docker Hub) (differs)23 842No figure on Docker Hub
Forks (GitHub) (differs)133No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/neon)On your machine (ghcr.io/liquibase/liquibase-mcp-changelog-server:1.0.0)
Transportstdiostdio
Tools it declares (differs)19Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/neondatabase-labs/mcp-server-neongithub.com/liquibase/liquibase-mcp-changelog-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

Neon

In its own words, on Docker MCP Catalog:

MCP server for interacting with Neon Management API and databases.

Liquibase Changelog MCP Server

In its own words, on Official MCP Registry:

Convert natural language into validated Liquibase XML or SQL changesets. 19 tools, 12 databases.

How to run each

Neon As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEON_API_KEY=<YOUR_NEON_API_KEY>" --transport stdio neon -- docker run -i --rm -e NEON_API_KEY mcp/neon

Requires: NEON_API_KEY (secret)

Liquibase Changelog MCP Server As a local MCP server: Docker image

Claude Code
claude mcp add --env "LIQUIBASE_LICENSE_KEY=<YOUR_LIQUIBASE_LICENSE_KEY>" --transport stdio changelog-mcp-server -- docker run -i --rm -e LIQUIBASE_LICENSE_KEY ghcr.io/liquibase/liquibase-mcp-changelog-server:1.0.0

Requires: LIQUIBASE_LICENSE_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 Liquibase Changelog MCP Server publish no list of tools, so we do not compare tools.

Settings each asks for

Only Neon asks for

  • NEON_API_KEY (secret)

Only Liquibase Changelog MCP Server asks for

  • LIQUIBASE_LICENSE_KEY (secret)
  • LIQUIBASE_MCP_DISABLE_VALIDATION
  • LIQUIBASE_MCP_INCLUDE_ROLLBACK
  • LIQUIBASE_MCP_OUTPUT_FORMAT
  • LIQUIBASE_MCP_SQL_DATABASE

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

What it can do: Neon · What it can do: Liquibase Changelog MCP Server · 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