Database Migration

Database migrations on a Postgres MCP server are executed transactionally using BEGIN/COMMIT blocks to ensure atomic schema updates. This Skill verifies the database connection and migrations directory, then records applied versions in schema_migrations to prevent drift.

Before applying versioned schema changes, you need a configured Postgres MCP server in .mcp.json, a migrations directory containing scripts, and a verified database connection. The process tracks applied migrations in a schema_migrations table.

Transaction-safe database migration handles schema updates by wrapping each versioned migration in a database transaction. This ensures atomic application across development, staging, and production environments, updating migration state and prompting for model adjustments.

Applied migrations are tracked to avoid schema drift in Postgres by recording their versions in a dedicated schema_migrations table. The Skill verifies the database connection and updates this migration state after successfully committing transactional schema changes.

Yes, you can use this to apply pending migrations to staging and production databases. It automates safe execution of database migrations on a Postgres MCP server across development, staging, and production environments using transaction-safe versioned scripts.