relational-database-mcp-cloudbase

Use querySqlDatabase with action="runQuery" and a read-only SELECT statement, including LIMIT and filters. For writes or DDL, use manageSqlDatabase with action="runStatement" after confirming the MySQL instance is ready.

Call manageSqlDatabase with action="provisionMySQL" and confirm=true, then poll querySqlDatabase with action="describeCreateResult" until the lifecycle status is READY before running any SQL.

Use MCP tools for agent-driven database management such as provisioning, ad-hoc SQL, and permission changes. Use SDKs only inside application code, such as Web or Node.js apps, and never mix SDK initialization into an MCP flow.

CloudBase uses _openid for per-user access control on SQL tables. New tables must include _openid VARCHAR(64) DEFAULT '' NOT NULL, and the server populates it automatically from the authenticated session during inserts.

Call managePermissions with action="updateResourcePermission", resourceType="sqlDatabase", the table name as resourceId, and a permission such as READONLY. Use queryPermissions with action="getResourcePermission" to audit current rules first.

manageSqlDatabase with action="destroyMySQL" removes the environment's SQL instance after explicit confirmation. Poll querySqlDatabase with action="describeTaskStatus" until the destroy task completes, then verify with getInstanceInfo.