Integration

Google Cloud SQL integration

Google Cloud SQL Admin API for managing MySQL, PostgreSQL, and SQL Server instances. Create and manage instances, databases, users, backups, and replication.

Connect Google Cloud SQL How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Google Cloud SQL.Built from the 30 Google Cloud SQL tools below, on the connection you add once.

Common Google Cloud SQL use cases

automate instance management
automate user management
automate database management
automate backup run management
automate replica management
automate operation management
list user programmatically
create user programmatically
delete user programmatically
update user programmatically

What you can do with Google Cloud SQL

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Instance, 11 operations

clone_instanceClone instancePOSTCreates a Cloud SQL instance as a clone of the source instance. Using this operation might cause your instance to restart
create_instanceCreate instancePOSTCreates a new Cloud SQL instance
delete_instanceDelete instanceDELETEDeletes a Cloud SQL instance. Delete instance.
export_instanceExport instancePOSTExports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file
failover_instanceFailover instancePOSTInitiates a manual SQL Server Availability Group failover of the primary instance to a standby instance
get_instanceGet instanceGETRetrieves a resource containing information about a Cloud SQL instance
import_instanceImport instancePOSTImports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage
list_instancesList instancesGETLists Cloud SQL instances in a Google Cloud project
patch_instancePatch instancePATCHPartially updates settings of a Cloud SQL instance in the request body using patch semantics
restart_instanceRestart instancePOSTRestarts a Cloud SQL instance. Restart instance.
update_instanceUpdate instancePUTUpdates settings of a Cloud SQL instance (replaces entire resource)

Backup run, 4 operations

create_backup_runCreate backup runPOSTCreates a new backup run on demand
delete_backup_runDelete backup runDELETEDeletes the backup taken by a backup run
get_backup_runGet backup runGETRetrieves a resource containing information about a backup run
list_backup_runsList backup runsGETLists all backup runs associated with the project or a given instance and configuration in the reverse chronological order of the backup initiation time

Database, 4 operations

create_databaseCreate databasePOSTInserts a resource containing information about a database inside a Cloud SQL instance
delete_databaseDelete databaseDELETEDeletes a database from a Cloud SQL instance
get_databaseGet databaseGETRetrieves a resource containing information about a database inside a Cloud SQL instance
list_databasesList databasesGETLists databases in the specified Cloud SQL instance

User, 4 operations

delete_userDelete userDELETEDeletes a user from a Cloud SQL instance
insert_userInsert userPOSTCreates a new user in a Cloud SQL instance
list_usersList usersGETLists users in the specified Cloud SQL instance
update_userUpdate userPUTUpdates an existing user in a Cloud SQL instance

Operation, 3 operations

cancel_operationCancel operationPOSTCancels an instance operation that has not yet started
get_operationGet operationGETRetrieves an instance operation that has been performed on a Cloud SQL instance
list_operationsList operationsGETLists all instance operations that have been performed on Cloud SQL instances in a project

Replica, 3 operations

promote_replicaPromote replicaPOSTPromotes the read replica instance to be a stand-alone Cloud SQL instance
start_replicaStart replicaPOSTStarts the replication in the read replica instance
stop_replicaStop replicaPOSTStops the replication in the read replica instance

Backup, 1 operation

restore_backupRestore backupPOSTRestores a backup of a Cloud SQL instance. Using this operation might cause your instance to restart

OAuth scopes Google Cloud SQL requires

Each operation declares the scopes Google Cloud SQL requires for it.

https://www.googleapis.com/auth/sqlservice.adminneeded by cancel_operation, clone_instance, create_backup_run and 27 more

Use Google Cloud SQL from Claude Code, Cursor or Codex

Connect Google Cloud SQL in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Google Cloud SQL operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Google Cloud SQL

Create your workspace
Sign up free. Nothing to install.
Connect Google Cloud SQL once
Add your Google Cloud SQL connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Google Cloud SQL integration FAQ

What can you do with the Google Cloud SQL integration?

LiveContext exposes 30 operations on Google Cloud SQL, covering instance, backup run, database and user. Common uses include automate instance management, automate user management and automate database management.

Which OAuth scopes does Google Cloud SQL require?

The operations that declare a scope all need https://www.googleapis.com/auth/sqlservice.admin.