PlanetScale Connector for AI agents.

Yes. This Connector gives your agent the ability to provision, branch, and manage your distributed MySQL clusters using natural language commands.

It allows you to fork your production schema into a new, isolated branch. This is perfect for testing migrations without affecting your live data.

Yes, it can use the delete capability to remove a cluster. It is best practice to list your databases first to ensure you are targeting the correct environment.

Yes. Your agent can identify all the physical cloud availability zones supported by the backend, helping you choose the best spot for low latency.

It is excellent for DevOps. It automates the tedious parts of infrastructure management, like purging stale branches and auditing distribution footprints.

Just tell your agent to create a new database. It will handle the provisioning of a managed MySQL cluster in your preferred region.

Yes. The integration provides delete_branch and delete_database. They map directly to infrastructure teardowns. You should scope the Service Token carefully inside the PlanetScale dashboard to avoid catastrophic misinterpretations if your explicit intent is just testing. Deletions via delete_database are absolute and irretrievable.

No. PlanetScale branches solely duplicate the static underlying DDL structure (schema), exactly like taking a snapshot of empty tables. The new branch boots up free of rows. This design lets your agent freely run ALTER TABLE operations independently without crashing the master tables.

All queries essentially require the foundational string parameters known as the org_name. If unknown, a simple list_organizations query reveals the UUID scope dictating your authorized account parameter bounds securely.