Get started free
All integrations

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.

30 toolsOAuthAPI docs

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

  • POSTclone_instance

    Creates a Cloud SQL instance as a clone of the source instance. Using this operation might cause your instance to restart

  • POSTcreate_instance

    Creates a new Cloud SQL instance

  • DELETEdelete_instance

    Deletes a Cloud SQL instance. Delete instance.

  • POSTexport_instance

    Exports data from a Cloud SQL instance to a Cloud Storage bucket as a SQL dump or CSV file

  • POSTfailover_instance

    Initiates a manual SQL Server Availability Group failover of the primary instance to a standby instance

  • GETget_instance

    Retrieves a resource containing information about a Cloud SQL instance

  • POSTimport_instance

    Imports data into a Cloud SQL instance from a SQL dump or CSV file in Cloud Storage

  • GETlist_instances

    Lists Cloud SQL instances in a Google Cloud project

  • PATCHpatch_instance

    Partially updates settings of a Cloud SQL instance in the request body using patch semantics

  • POSTrestart_instance

    Restarts a Cloud SQL instance. Restart instance.

  • PUTupdate_instance

    Updates settings of a Cloud SQL instance (replaces entire resource)

Backup run, 4 operations

  • POSTcreate_backup_run

    Creates a new backup run on demand

  • DELETEdelete_backup_run

    Deletes the backup taken by a backup run

  • GETget_backup_run

    Retrieves a resource containing information about a backup run

  • GETlist_backup_runs

    Lists 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

  • POSTcreate_database

    Inserts a resource containing information about a database inside a Cloud SQL instance

  • DELETEdelete_database

    Deletes a database from a Cloud SQL instance

  • GETget_database

    Retrieves a resource containing information about a database inside a Cloud SQL instance

  • GETlist_databases

    Lists databases in the specified Cloud SQL instance

User, 4 operations

  • DELETEdelete_user

    Deletes a user from a Cloud SQL instance

  • POSTinsert_user

    Creates a new user in a Cloud SQL instance

  • GETlist_users

    Lists users in the specified Cloud SQL instance

  • PUTupdate_user

    Updates an existing user in a Cloud SQL instance

Operation, 3 operations

  • POSTcancel_operation

    Cancels an instance operation that has not yet started

  • GETget_operation

    Retrieves an instance operation that has been performed on a Cloud SQL instance

  • GETlist_operations

    Lists all instance operations that have been performed on Cloud SQL instances in a project

Replica, 3 operations

  • POSTpromote_replica

    Promotes the read replica instance to be a stand-alone Cloud SQL instance

  • POSTstart_replica

    Starts the replication in the read replica instance

  • POSTstop_replica

    Stops the replication in the read replica instance

Backup, 1 operation

  • POSTrestore_backup

    Restores 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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. 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.

  3. 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.

Popular integrations

Browse the whole catalog