
Liquibase Changelog MCP Server
io.github.liquibasePublished by GitHub account liquibasev1.0.0Updated Oct 24, 2026
Convert natural language into validated Liquibase XML or SQL changesets. 19 tools, 12 databases.
Overview
Turns natural-language requests into validated Liquibase XML or SQL changesets, with 19 tools covering 12 databases.
- What you can do
- Generate Liquibase changesets from natural-language descriptions, in XML or formatted SQL.
- Validate generated changesets against an in-memory H2 database before use.
- Optionally emit explicit rollback blocks in XML changesets.
- Target a chosen database dialect for formatted SQL output, such as postgresql, mysql, oracle, mssql or sqlite.
- When to use it
- Useful when you maintain Liquibase database migrations and want an assistant to draft changesets from plain-language change requests, with validation and optional rollback blocks, instead of writing them by hand.
- Requirements
- Runs locally as a stdio process from an OCI container image. Requires a Liquibase Pro license key supplied in LIQUIBASE_LICENSE_KEY. Optional settings: LIQUIBASE_MCP_DISABLE_VALIDATION, LIQUIBASE_MCP_INCLUDE_ROLLBACK, LIQUIBASE_MCP_OUTPUT_FORMAT and LIQUIBASE_MCP_SQL_DATABASE.
Installation
In SourceWeft
- Open Liquibase Changelog MCP Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.