Introducing Agent Safe Governance for the AI Era

Configure the Liquibase AI Changelog Generator in Claude Desktop

Last updated: May 15, 2026

Both Liquibase XML changesets and formatted SQL come with their own complexity: XML requires precise syntax and schema expertise, while formatted SQL demands learning specific rules and conventions. The Liquibase AI Changelog Generator solves this by letting you describe database changes in natural language and automatically converting them into valid, tested Liquibase changesets. This Model Context Protocol (MCP) server runs locally and integrates with Claude Desktop, turning conversational requests like “add an email column to the users table” into production-ready changesets.

Powered by Liquibase’s native Java APIs, the server offers nineteen specialized tools that handle everything from basic table operations to complex procedures and sequences. Each generated changeset is automatically validated against an H2 database to catch errors before they reach your production environment, with configurable validation and rollback options to match your workflow. As a standalone executable with 322 comprehensive tests, you can generate validated changesets immediately with no external Liquibase CLI installation required.

Before you begin

  • Download the liquibase-mcp-changelog-server-0.1.0.jar file and note its full path.

  • Java 17 or higher is installed and available in the PATH.

  • Liquibase Secure is installed. Note the full path to the folder that contains the liquibase executable.

  • Claude Desktop is installed.

Procedure

1

Confirm the Server Starts

From your terminal, run the following command.

Be sure to:

  • Replace your_jar_path with the full path to the JAR file on your machine. For example, /Users/yourname/liquibase-mcp-changelog-server-0.1.0.jar

java -jar your_jar_path

The output will state the server has started successfully:

Liquibase Changelog MCP Server v0.1.0
Starting Liquibase MCP Server...
Liquibase MCP Server started successfully with 19 tools

If you see an error, confirm that java -version returns 17 or higher.

2

Open the Configuration File

Open the terminal and run the following command to open the Claude Desktop configuration directory in Finder.

open "/Users/$(whoami)/Library/Application Support/Claude/"

Open claude_desktop_config.json in a text editor. If the file does not exist, create it first:

touch "/Users/$(whoami)/Library/Application Support/Claude/claude_desktop_config.json"
3

Add the MCP Server Configuration

Replace the entire contents of claude_desktop_config.json with the following.

Be sure to:

  • Replace your_jar_path with the full path to the JAR file. For example, /Users/yourname/liquibase-mcp-changelog-server-0.1.0.jar

  • Replace your_liquibase_home_path with the path to the folder that contains the liquibase executable. For example, /usr/local/bin

  • Replace your_liquibase_license_key with your Liquibase Secure license key.

loading
4

Restart Claude Desktop

Fully quit Claude Desktop — do not just close the window. Then reopen Claude Desktop.

macOS

Press Command+Q while Claude Desktop is in focus, or right-click the Claude icon in the Dock and choose Quit. Reopen Claude Desktop from your Applications folder.

Windows

Right-click the Claude icon in the system tray and choose Quit, or open Task Manager, find Claude Desktop under the Processes tab, and select End Task. Reopen Claude Desktop from the Start menu or your taskbar.

Linux

Right-click the Claude icon in the system tray and choose Quit. If no tray icon is available, run pkill -f claude in the terminal. Reopen Claude Desktop from your application launcher.

5

Verify the Connection

Open a new chat in Claude Desktop. Look for an icon labeled Ask Liquibase at the bottom of the chat input area. If it is visible, the AI Changelog Generator is running successfully.

6

Test the Connection

In the chat, type:

Create a table called products with id INTEGER and name VARCHAR(255)

Claude calls the create_table tool and returns a Liquibase XML changelog. You do not need to mention MCP or tools, describe what you want in plain English.