Databases
Manage MSSQL, MySQL, and PostgreSQL databases available to an existing hosting plan. Passwords are supplied only when creating or rotating credentials and are never returned by read tools.
Create a database
Call database_get_capacity first. Then call database_create with planId, engine, database name, matching password fields, quota, and an idempotency key. The default application login is created as part of the operation.
Connection settings
database_get_connection_settings returns sanitized host, port, database, username, TLS guidance, and a password-placeholder template. It never returns the current password. Store the password in your application’s secret system.
Users and credentials
database_list_userslists default and additional logins without passwords.database_create_usercreates an additional scoped user when the plan supports it.database_rotate_credentialrotates the default login password.database_rotate_user_credentialrotates an additional user password.database_delete_usercannot delete a protected default user.
Резервне копіювання та відновлення
database_create_backup queues an engine-appropriate backup into the hosting account's owned /db folder. database_restore_backup accepts only a safe owned /db path and requires the exact databaseId plus explicit overwrite acknowledgement. Use operation_get_status to follow queued work.
Advanced Custom Backup, backup upload targets, and database import are not exposed through MCP. Upload or place the correctly formatted backup in the account's /db folder through the normal hosting workflow before requesting a restore.