migrate-mcp
Related Servers
Alternatives to migrate-mcp
No user-submitted related servers found.
Related 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.626 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceExposes read-only tools that let AI assistants detect schema drift, analyze lock impact, verify data with checksums, and plan safe PostgreSQL migrations that are validated by deterministic checks and shadow runs.1,075 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables database governance for Drizzle ORM projects by inspecting schemas, linting migrations for unsafe operations, detecting schema drift, and explaining query plans with performance checks.-

terrabaseofficial
AlicenseNot gradedqualityFmaintenanceLLM-assisted, safety-gated Postgres migrations exposed as an MCP server, using a deterministic rule engine over Postgres's own parser AST for safety enforcement, with two-phase approval and append-only audit ledger.Apache 2.0- AlicenseNot gradedqualityBmaintenanceGives AI coding assistants, IDEs, and CI full PostgreSQL schema intelligence from an offline snapshot, enabling linting, query validation, migration safety analysis, and foreign key graph exploration without ever exposing database credentials.36BSD 2-Clause "Simplified"
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.