migrate-mcp
Provides migration framework detection, CLI-backed migration status and schema drift checks, migration generation, risk review, plain-English explanations, and rollback guidance for Prisma projects.
Provides migration framework detection, CLI-backed migration status, migration skeleton generation, risk review, plain-English explanations, and rollback guidance for Sequelize projects.
Provides migration framework detection, CLI-backed migration status and schema drift checks, CLI-backed migration generation, risk review, plain-English explanations, and rollback guidance for TypeORM projects.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@migrate-mcp Detect the migration framework in this repo and review the pending migration."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
migrate-mcp
Inspect, explain, and prepare database migrations without giving an agent permission to run them.
migrate-mcp is an open-source MCP server for Alembic, golang-migrate, TypeORM, Sequelize, and Prisma. It detects frameworks from repository evidence, inspects migration state and drift through framework-native commands, reviews risk, generates files with explicit approval, explains changes, and gives rollback guidance.
It deliberately exposes no tool that applies a migration or executes a rollback.
30-second setup
Add this server to your MCP client:
{
"mcpServers": {
"migrate": {
"command": "npx",
"args": ["-y", "migrate-mcp"]
}
}
}Then ask: Detect the migration framework in this repo and review the pending migration.

Related MCP server: DBM MCP Server
Tools
Tool | Purpose | Writes files |
| Detect supported frameworks with evidence | No |
| Inventory migrations and query status where configured | No |
| Run verified framework-native drift checks | No |
| Find destructive, availability, data, and rollback risk | No |
| Generate through the framework CLI after approval | Yes |
| Explain recognized operations in plain English | No |
| Describe rollback steps and uncertainty | No |
Safety model
No apply, upgrade, deploy, rollback, or downgrade execution tools.
Generation requires
approved: true, validates the name, and blocks production-like targets.Commands use argument arrays with
shell: false, bounded output, timeouts, and a small environment allowlist.Paths are resolved against a real repository root and symlink escapes are rejected.
Credentials are redacted from diagnostics.
Unsupported capabilities return an explicit unsupported or partial result instead of guessed output.
Generation can still execute project-owned framework configuration, so review repositories before granting an agent access.
Framework support
Framework | Detect | Status | Drift | Generate | Review and explain |
Alembic | Yes | CLI-backed | CLI-backed | Autogenerate | Yes |
golang-migrate | Yes | Version-backed | Partial | Skeleton | Yes |
TypeORM | Yes | CLI-backed | CLI-backed | CLI-backed | Yes |
Sequelize | Yes | CLI-backed | Unsupported | Skeleton | Yes |
Prisma | Yes | CLI-backed | CLI-backed | CLI-backed | Yes |
Database-backed operations require the same framework configuration and credentials that the project CLI requires. Offline inventory remains available when those are absent.
Programmatic API
import { detectMigrationFrameworks, reviewMigrations } from "migrate-mcp";
const frameworks = await detectMigrationFrameworks(process.cwd());
const review = await reviewMigrations({
repository: process.cwd(),
paths: ["migrations/20260923_add_accounts.sql"],
});Development
Requires Node.js 22 or newer.
npm ci
npm run checkSee CONTRIBUTING.md for fixture and adapter guidelines. Security concerns belong in SECURITY.md.
License
MIT
Available Tools
7 toolsdetect_migration_frameworksARead-only
Detect Alembic, golang-migrate, TypeORM, Sequelize, and Prisma from repository evidence.
Inputs: repository (required).
detect_schema_driftCRead-only
Use verified framework-native commands to inspect schema drift and report unsupported dimensions honestly.
Inputs: repository (required), options, framework.
explain_migrationCRead-only
Explain migration operations in plain English without executing them.
Inputs: paths (required), repository (required), options, framework.
generate_migrationB
Generate a migration through the detected framework. Requires explicit approval and blocks production-like targets.
Inputs: name (required), approved (required), repository (required), options, +1 more.
get_rollback_guidanceBRead-only
Provide rollback guidance and caveats. This tool never runs a rollback.
Inputs: paths (required), repository (required), options, framework.
list_migration_statusARead-only
List migration inventory and database-backed status when framework configuration is available.
Inputs: repository (required), options, framework.
review_migrationsARead-only
Statically review migration files for destructive, availability, data, and rollback risks without executing them.
Inputs: paths (required), repository (required), options, framework.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of migration management: generation, explanation, rollback guidance, framework detection, status listing, drift detection, and risk review. There is no overlap or ambiguity in their purposes.
All tool names follow a consistent verb_noun snake_case pattern (e.g., generate_migration, detect_schema_drift, list_migration_status). This uniform convention makes the set predictable and easy to navigate.
Seven tools is well-scoped for a migration-focused server. Each tool covers a necessary part of the migration workflow without redundancy, fitting the typical 3-15 tool range.
The set covers framework detection, generation, explanation, review, status, drift detection, and rollback guidance. A minor gap is the lack of explicit apply or rollback execution tools, though generate_migration may partially cover apply, and the server may intentionally focus on planning and analysis.
Maintenance
Related MCP Connectors
Review your AI agent's database changes on your schema, with plain-language risk, before they run.
Detects database migration table locks, terraform cost leaks, and OWASP API flaws.
Scans schema metadata to classify PHI, score HIPAA readiness, and generate compliant migrations.
Database change control: schemas, change scripts, approvals, rollback, drift and audit
Related MCP Servers
- AlicenseAqualityDmaintenanceAnalyzes database migrations for risks like lock contention and data loss before they run. Supports Flyway and Liquibase formats, providing risk scores and rollback generation.694 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables developers and coding agents to submit structured database schema changes to a shared coordinator, compare them against accepted migration history and other active work, and receive reports on safe changes, stale bases, dependencies, and conflicts before migrations are finalized. It supports CI-controlled deployment coordination without exposing application database credentials.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI coding agents to perform deterministic database architecture audits and performance engineering for PostgreSQL and MySQL, covering migration analysis with schema health scoring, ESR-based composite index recommendations, N+1 query detection, EXPLAIN plan diagnosis, transaction and deadlock analysis, partitioning and archival design, and capacity or configuration tuning. It also generates phased Expand & Contract runbooks that turn blocking DDL into zero-downtime production migrations.8MIT
- AlicenseNot gradedqualityCmaintenanceEnables assessing database change risk, estimating impact, generating rollback plans, prechecking change windows, and orchestrating dry-run, canary, apply, and rollback with approval gates and auditable state transitions.MIT