Migratrix

ClaudeCommunityby Migratrix

Migratrix is change control for production databases: SQL Server, Oracle, PostgreSQL, MySQL and MariaDB. Teams write change scripts, promote them through environments with approvals, and get an automatic, verified rollback for every change. This connector lets an assistant take part in that process with exactly the permissions of the person who connected it, and never more. What the assistant can do: - Understand the workspace: environments and their approval rules, pipelines, who it acts for, what it may do where. - Read change scripts, their risk and reversibility, stage-by-stage progress, execution logs and blockers. - Write a change script (Migratrix generates the rollback; assistants never write one), run it where no approval is required, and ask the approvers to look where approval is required. - Follow GitOps conventions: for repository-driven pipelines it is told the directory, file name and layout to write. - Read the hash-chained audit ledger, verify its integrity, and assemble evidence packs for auditors. What it can never do, whatever the person may: approve a change, change approval rules, roles, environments or pipelines, write a rollback, execute or roll back in an environment that requires approval, read or write database credentials, or write to data. Administrators set a level per environment (nothing / read / propose / execute) and can pause every assistant with one switch. Every call is in the audit ledger, marked as made through an assistant. Schemas and rows stay inside the customer's network: a second, optional endpoint is served by the Migratrix Executor there and is covered by the same consent. This listing is the control-plane endpoint, which any Claude can reach. Read-only tools carry readOnlyHint; tools that run or roll back a change are destructiveHint, so Claude asks first.