MCP server for database migration risk analysis. Version 0.2.14, released under MIT. Supports Flyway (V__*.sql, R__*.sql) and Liquibase XML/YAML changelogs with native parsing. Detects destructive operations, lock risks (ACCESS EXCLUSIVE, SHARE), data loss patterns (column drops, type changes), duplicate changeSet IDs, and rollback incompleteness. Unlike MigrationPilot (PG-only raw SQL), this tool parses Liquibase changelogs natively and works across databases. Requires Node >=20.0.0. Pro tier ($9/month) adds HTML+PDF reports.
npm install mcp-migration-advisorNo compatibility data collected yet for this library.
Verified import paths — ran on the pinned version, not inferred.
Claude Desktop configuration to enable MCP Migration Advisor for database migration risk analysis.
Upgrade Node.js to v20 or later.
Always provide both filename (e.g., 'V2__add_user_email.sql') and the full SQL content.
Remove DOCTYPE declarations from Liquibase changelogs before analysis.
Pass content under key 'yaml' for now; watch changelog for renaming.
Set PRO_LICENSE_KEY environment variable before starting the MCP server.
Run 'npm install @modelcontextprotocol/sdk' in the project directory.
Use exactly 'analyze_migration' (case-sensitive). Check MCP server configuration in Claude Desktop.
Validate YAML with a YAML linter; ensure indentation is correct and changeSets are properly structured.
Add a <rollback> block for each changeSet in Liquibase XML/YAML, or use generate_rollback tool to auto-create rollback SQL.