mcp-migration-advisor 0.2.11 → 0.2.13

package/build/analyzers/data-loss.js

@@ -28,11 +28,12 @@ export function analyzeDataLoss(migration) {
             }
             case "DROP_TABLE": {
                 const cascade = upper.includes("CASCADE");
+                const dropTableName = stmt.tableName ?? "unknown";
                 issues.push({
                     risk: "CERTAIN",
                     statement: truncate(stmt.raw),
                     tableName: stmt.tableName,
-                    description: `Dropping table '${stmt.tableName}' permanently deletes all data.${cascade ? " CASCADE will also drop dependent objects." : ""}`,
+                    description: `Dropping table '${dropTableName}' permanently deletes all data.${cascade ? " CASCADE will also drop dependent objects." : ""}`,
                     mitigation: "Ensure a backup exists. Consider renaming the table first and dropping in a later migration.",
                 });
                 break;

package/build/analyzers/lock-risk.js

@@ -85,11 +85,12 @@ function analyzeStatement(stmt) {
             break;
         }
         case "DROP_TABLE": {
+            const dropTableName = stmt.tableName ?? "unknown";
             risks.push({
                 severity: "HIGH",
                 statement: truncate(stmt.raw),
                 tableName: stmt.tableName,
-                risk: `DROP TABLE '${stmt.tableName}' is irreversible and acquires ACCESS EXCLUSIVE lock.`,
+                risk: `DROP TABLE '${dropTableName}' is irreversible and acquires ACCESS EXCLUSIVE lock.`,
                 recommendation: "Ensure no foreign keys reference this table. Consider renaming first (expand-contract) to allow rollback.",
             });
             if (stmt.details.cascade === "true") {

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

@@ -6,9 +6,12 @@
  *   analyze_migration  — Parse and analyze a SQL migration for risks
  *   score_risk          — Calculate risk score for a migration
  */
+import { createRequire } from "module";
 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
 import { z } from "zod";
+const require = createRequire(import.meta.url);
+const { version: packageVersion } = require("../package.json");
 import { parseMigration } from "./parsers/flyway-sql.js";
 import { parseLiquibaseXml } from "./parsers/liquibase-xml.js";
 import { parseLiquibaseYaml } from "./parsers/liquibase-yaml.js";
@@ -33,7 +36,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 v${packageVersion} — MCP server for database migration risk analysis
 
 Usage:
   mcp-migration-advisor [options]
@@ -52,10 +55,10 @@ Tools provided:
 }
 const server = new McpServer({
     name: "mcp-migration-advisor",
-    version: "0.2.10",
+    version: packageVersion,
 });
 // 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.", {
+server.tool("analyze_migration", "Analyze a SQL migration file for lock risks, data loss potential, and unsafe patterns. Detects: ACCESS EXCLUSIVE locks (DROP TABLE, ADD COLUMN NOT NULL, type changes, CREATE INDEX without CONCURRENTLY), data loss operations (TRUNCATE, DELETE without WHERE, UPDATE without WHERE, DROP COLUMN), and cascade risks. Supports Flyway versioned (V__*.sql) and repeatable (R__*.sql) migrations, as well as plain SQL files.", {
     filename: z.string().describe("Migration filename (e.g., V2__add_user_email.sql)"),
     sql: z.string().describe("The SQL content of the migration file"),
 }, async ({ filename, sql }) => {
@@ -332,7 +335,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.11",
+  "version": "0.2.13",
   "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",