Liquibase MCP Server Environment Variable configurations

Last updated: October 30, 2025

The MCP Server is currently in early access, and we're actively seeking customer feedback to help shape its development. If you would like to learn more about this feature, please contact us here.

The MCP server supports runtime configuration through two environment variables, allowing you to optimize the tool for your specific workflow. All generated changesets are automatically validated against an H2 database to catch syntax errors before they reach your actual database. You can disable this validation by setting LIQUIBASE_MCP_DISABLE_VALIDATION=true if you need faster response times while iterating or prototyping. Additionally, you can control whether the server generates explicit rollback blocks by settingLIQUIBASE_MCP_INCLUDE_ROLLBACK=true.By default, rollback blocks are not included, relying instead on Liquibase's automatic rollback capabilities, but explicit rollback blocks give you more precise control over how changes are reversed if needed. These variables can be set independently or combined to customize the server's behavior, prioritizing speed, safety, or control as needed.

Configuration settings

You can set these two environment variables in your shell or environment and control how the server behaves by configuring them during runtime.

Environment Variable Examples:

• LIQUIBASE_MCP_DISABLE_VALIDATION=true- Disables validation for faster responses.

• LIQUIBASE_MCP_DISABLE_VALIDATION=false- Explicitly enables validation.

• LIQUIBASE_MCP_INCLUDE_ROLLBACK=true- Includes explicit rollback blocks for supported change types.

• Unset or any other value - Default behavior (validation enabled, rollbacks disabled)