Liquibase Changelog MCP Server
Turn natural-language schema change requests into validated Liquibase XML or formatted SQL changesets for twelve database dialects from your coding agent.
Overview
Liquibase Changelog MCP Server is a MCP server for the Build phase that converts natural language into validated Liquibase XML or SQL changesets across 19 tools and 12 database dialects.
What is this MCP server?
- 19 MCP tools for changelog authoring and Liquibase-oriented database workflows
- 12 target database dialects for formatted SQL output (PostgreSQL, MySQL, Oracle, MSSQL, SQLite, and others)
- Natural language to validated Liquibase XML or formatted-sql via LIQUIBASE_MCP_OUTPUT_FORMAT
- Optional H2 in-memory validation unless LIQUIBASE_MCP_DISABLE_VALIDATION is true
- OCI package ghcr.io/liquibase/liquibase-mcp-changelog-server:1.0.0 with stdio transport
- 19 MCP tools documented in registry description
- 12 database dialects for formatted SQL output
- Server version 1.0.0 OCI stdio package
What problem does it solve?
Solo developers lose hours translating verbal schema tweaks into correct, dialect-specific Liquibase changesets without copy-paste errors.
Who is it for?
Indie SaaS builders already on Liquibase Pro who want agent-assisted migrations with multi-database SQL formatting and validation.
Skip if: Hobby projects avoiding paid Liquibase licenses or teams that do not use Liquibase changelogs in CI.
What do I get? / Deliverables
After you run the OCI stdio server with a Pro license, your agent can produce validated changelog XML or formatted SQL you drop into your Liquibase pipeline.
- Validated Liquibase XML or formatted-sql changesets from agent prompts
- Dialect-aware SQL for one of twelve supported databases
- Repeatable migration snippets ready for review and CI apply
Recommended MCP Servers
Journey fit
Primary shelf is Build backend because migrations are authored alongside application work, before repeatable Ship and Operate deployment. backend matches changelog generation, dialect-specific SQL, and H2 validation of changesets rather than frontend or generic PM docs.
How it compares
Database migration MCP with 19 tools, not a generic SQL chat skill or ORM-only codegen plugin.
Common Questions / FAQ
Who is Liquibase Changelog MCP Server for?
Backend-focused solo builders and small teams using Liquibase Pro who want MCP-driven changelog generation from natural language inside Claude Code or similar hosts.
When should I use Liquibase Changelog MCP Server?
Use it while designing or altering schemas in Build, and when preparing migration artifacts before Ship, especially when you need dialect-correct formatted SQL or XML.
How do I add Liquibase Changelog MCP Server to my agent?
Configure stdio MCP to run the OCI image ghcr.io/liquibase/liquibase-mcp-changelog-server:1.0.0, set LIQUIBASE_LICENSE_KEY, and optional LIQUIBASE_MCP_OUTPUT_FORMAT and LIQUIBASE_MCP_SQL_DATABASE variables.