mcp-migration-advisor 0.2.10 → 0.2.12

package/README.md

@@ -31,7 +31,7 @@ Unlike MigrationPilot (PG-only, raw SQL analysis), this tool **parses Liquibase
 - Priority support
 
 <!-- TODO: replace placeholder Stripe Payment Link once STRIPE_SECRET_KEY is configured -->
-**$9.99/month** — [Get Pro License](https://buy.stripe.com/PLACEHOLDER)
+**$9.00/month** — [Get Pro License](https://buy.stripe.com/PLACEHOLDER)
 
 Pro license key activates the `generate_report` MCP tool in mcp-jvm-diagnostics.
 

package/build/analyzers/data-loss.js

@@ -101,8 +101,12 @@ export function analyzeDataLoss(migration) {
                         mitigation: "Add a WHERE clause to limit the delete, or use TRUNCATE if intentional.",
                     });
                 }
-                // Detect UPDATE without WHERE
-                if (upper.match(/^UPDATE\b/) && !upper.includes("WHERE")) {
+                // Detect UPDATE without WHERE.
+                // Match UPDATE at the start of the string or after a statement separator
+                // (semicolon or newline), allowing leading whitespace on the line.
+                // This ensures detection works in multi-statement <sql> Liquibase blocks
+                // where UPDATE is not the very first statement.
+                if (upper.match(/(?:^|[;\n])\s*UPDATE\b/) && !upper.includes("WHERE")) {
                     const tableMatch = stmt.raw.match(/UPDATE\s+(?:`|"|)?(?:\w+\.)?(\w+)/i);
                     issues.push({
                         risk: "LIKELY",

package/build/generators/rollback.js

@@ -47,8 +47,9 @@ export function generateRollback(migration) {
     }
     // Add Flyway schema_version cleanup
     if (migration.version) {
+        const escapedVersion = migration.version.replace(/'/g, "''");
         rollbackLines.push("-- Remove migration record from Flyway history:");
-        rollbackLines.push(`DELETE FROM flyway_schema_history WHERE version = '${migration.version}';`);
+        rollbackLines.push(`DELETE FROM flyway_schema_history WHERE version = '${escapedVersion}';`);
     }
     return {
         statements: rollbackStatements,

package/build/index.js

@@ -33,7 +33,7 @@ function formatParserWarnings(migration) {
 }
 // Handle --help
 if (process.argv.includes("--help") || process.argv.includes("-h")) {
-    console.log(`mcp-migration-advisor v0.2.10 — MCP server for database migration risk analysis
+    console.log(`mcp-migration-advisor v0.2.12 — MCP server for database migration risk analysis
 
 Usage:
   mcp-migration-advisor [options]
@@ -52,7 +52,7 @@ Tools provided:
 }
 const server = new McpServer({
     name: "mcp-migration-advisor",
-    version: "0.2.10",
+    version: "0.2.12",
 });
 // Tool 1: analyze_migration
 server.tool("analyze_migration", "Analyze a SQL migration file for lock risks, data loss potential, and unsafe patterns. Supports Flyway (V__*.sql) and plain SQL.", {
@@ -141,7 +141,7 @@ server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock ris
         let output = `## Liquibase Changelog Analysis\n\n`;
         output += `**ChangeSets**: ${migration.description}\n`;
         output += `**Statements**: ${migration.statements.length}\n`;
-        output += `**Risk Score**: ${riskScore}/100${riskScore >= 60 ? " HIGH RISK" : riskScore >= 30 ? " MODERATE RISK" : " LOW RISK"}\n\n`;
+        output += `**Risk Score**: ${riskScore}/100${riskScore >= 60 ? " ⚠️ HIGH RISK" : riskScore >= 30 ? " ⚡ MODERATE RISK" : " ✅ LOW RISK"}\n\n`;
         const typeCounts = {};
         for (const stmt of migration.statements) {
             typeCounts[stmt.type] = (typeCounts[stmt.type] || 0) + 1;
@@ -154,13 +154,17 @@ server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock ris
         if (lockRisks.length > 0) {
             output += "### Lock Risks\n\n";
             for (const risk of lockRisks) {
-                output += `**${risk.severity}**: ${risk.risk}\n> **Recommendation**: ${risk.recommendation}\n\n`;
+                output += `**${risk.severity}**: ${risk.risk}\n`;
+                output += `> \`${risk.statement}\`\n`;
+                output += `> **Recommendation**: ${risk.recommendation}\n\n`;
             }
         }
         if (dataLossIssues.length > 0) {
             output += "### Data Loss Analysis\n\n";
             for (const issue of dataLossIssues) {
-                output += `**${issue.risk}**: ${issue.description}\n> **Mitigation**: ${issue.mitigation}\n\n`;
+                output += `**${issue.risk}**: ${issue.description}\n`;
+                output += `> \`${issue.statement}\`\n`;
+                output += `> **Mitigation**: ${issue.mitigation}\n\n`;
             }
         }
         if (lockRisks.length === 0 && dataLossIssues.length === 0) {
@@ -179,7 +183,7 @@ server.tool("analyze_liquibase", "Analyze a Liquibase XML changelog for lock ris
     }
 });
 // Tool 3: analyze_liquibase_yaml
-server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lock risks, data loss potential, and unsafe patterns. Supports createTable, dropTable, addColumn, dropColumn, modifyDataType, createIndex, renameTable, renameColumn, and more.", {
+server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lock risks, data loss potential, and unsafe patterns. Supports createTable, dropTable, addColumn, dropColumn, modifyDataType, createIndex, addForeignKeyConstraint, renameTable, renameColumn, and more.", {
     yaml: z.string().describe("The Liquibase YAML changelog content"),
 }, async ({ yaml }) => {
     try {
@@ -194,7 +198,7 @@ server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lo
         let output = `## Liquibase YAML Changelog Analysis\n\n`;
         output += `**ChangeSets**: ${migration.description}\n`;
         output += `**Statements**: ${migration.statements.length}\n`;
-        output += `**Risk Score**: ${riskScore}/100${riskScore >= 60 ? " HIGH RISK" : riskScore >= 30 ? " MODERATE RISK" : " LOW RISK"}\n\n`;
+        output += `**Risk Score**: ${riskScore}/100${riskScore >= 60 ? " ⚠️ HIGH RISK" : riskScore >= 30 ? " ⚡ MODERATE RISK" : " ✅ LOW RISK"}\n\n`;
         const typeCounts = {};
         for (const stmt of migration.statements) {
             typeCounts[stmt.type] = (typeCounts[stmt.type] || 0) + 1;
@@ -207,13 +211,17 @@ server.tool("analyze_liquibase_yaml", "Analyze a Liquibase YAML changelog for lo
         if (lockRisks.length > 0) {
             output += "### Lock Risks\n\n";
             for (const risk of lockRisks) {
-                output += `**${risk.severity}**: ${risk.risk}\n> **Recommendation**: ${risk.recommendation}\n\n`;
+                output += `**${risk.severity}**: ${risk.risk}\n`;
+                output += `> \`${risk.statement}\`\n`;
+                output += `> **Recommendation**: ${risk.recommendation}\n\n`;
             }
         }
         if (dataLossIssues.length > 0) {
             output += "### Data Loss Analysis\n\n";
             for (const issue of dataLossIssues) {
-                output += `**${issue.risk}**: ${issue.description}\n> **Mitigation**: ${issue.mitigation}\n\n`;
+                output += `**${issue.risk}**: ${issue.description}\n`;
+                output += `> \`${issue.statement}\`\n`;
+                output += `> **Mitigation**: ${issue.mitigation}\n\n`;
             }
         }
         if (lockRisks.length === 0 && dataLossIssues.length === 0) {
@@ -324,7 +332,7 @@ server.tool("generate_rollback", "Generate reverse DDL to undo a SQL migration.
     }
 });
 // Tool 6: detect_conflicts
-server.tool("detect_conflicts", "Detect conflicts between two SQL migration files. Identifies same-table modifications, same-column changes, lock contention risks, and drop dependencies that could cause failures if applied concurrently or in the wrong order.", {
+server.tool("detect_conflicts", "Detect structural conflicts between two SQL migration files — same-table modifications, same-column changes, lock contention, and drop dependencies. Use this when two migrations touch the same schema objects and you need to know if ordering or concurrent execution matters. Note: only structural conflicts are detected (same table/column); semantic conflicts such as two migrations adding different indexes on the same column are not reported.", {
     filename_a: z.string().describe("First migration filename (e.g., V3__add_email.sql)"),
     sql_a: z.string().describe("SQL content of the first migration"),
     filename_b: z.string().describe("Second migration filename (e.g., V4__modify_users.sql)"),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-migration-advisor",
-  "version": "0.2.10",
+  "version": "0.2.12",
   "description": "MCP server for database migration risk analysis — Flyway and Liquibase XML/YAML/SQL support with lock detection and conflict analysis",
   "mcpName": "io.github.dmitriusan/mcp-migration-advisor",
   "main": "build/index.js",