Skip to content
actionlake
Start free

Connectors · Developer & infrastructure

Google Cloud SQL Admin MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Google Cloud SQL Admin and the rest of your systems. It gives your agent 85 Google Cloud SQL Admin actions (28 reads, 34 writes and 23 that wait for a confirmation) and holds the Google Cloud SQL Admin credential itself, so the agent never does. It paces Google Cloud SQL Admin's limits and records every call. Connecting Google Cloud SQL Admin needs your own Google Cloud SQL Admin OAuth app and one admin sign-in.

Connect Google Cloud SQL Admin freeSee pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp
the first call
do {  action: "gcp_cloud_sql.flags.list",  intent: "check which Google Cloud SQL Admin account is connected"}# Flags: list · read · 1 upstream call
  • 85actionsin one signed file
  • 28readlook, never change
  • 34writecreate and update
  • 23wait for a yesdestructive, confirmed first

Set up

Connect Google Cloud SQL Admin in three steps.

  1. 01

    Add actionlake to Claude.

    Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.

    https://connect.actionlake.com/mcp
  2. 02

    Connect Google Cloud SQL Admin.

    OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud SQL Admin, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.

    Before the first sign-in, Google Cloud SQL Admin needs an OAuth app of your own, registered in its developer portal. actionlake has no Google Cloud SQL Admin app to lend you.

    • access_tokenAccess token from one sign-in with your own OAuth app
    • refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
    • client_idGoogle OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud SQL Admin API on the…
    • client_secretGoogle OAuth client secret
    account { op: "connections.requirements", service: "gcp_cloud_sql" }
# free: exactly what to paste, and what is found for you
  3. 03

    Make the first call. Check before a write.

    Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

    do    { action: "gcp_cloud_sql.flags.list" }# flags: list · read · 1 upstream callcheck { action: "gcp_cloud_sql.users.insert", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Google Cloud SQL Admin at a glance

Sign-in
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Google Cloud SQL Admin, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide
access_tokenrefresh_tokenclient_idclient_secret
Limits we pace to
600 calls a minute, per connection
API covered
Google Cloud SQL Admin (instances, databases, users, backups, replicas, certificates, operations) API sqladmin v1 (Discovery revision 20260929)sqladmin.googleapis.com
Built from
Google Cloud SQL Admin's documentation, read 23 October 2026sqladmin.googleapis.comcloud.google.com
Service file
Version 1.0.0, signed (Ed25519)
Cached reads
24 of 28 reads, for up to 5 minutes; a write clears what it affects
Shared entities
2, so ask can line Google Cloud SQL Admin up with your other systems
Data
Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Google Cloud SQL Admin.

85 actions in 13 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

  • 28readlook, never change
  • 34writecreate and update
  • 23destructivewait for a confirmation

  1. Instances

    35

    6 read · 15 write · 14 destructive

    Instances: list · Instances: insert · Instances: get · Instances: patch

  2. Projects instances

    7

    3 read · 3 write · 1 destructive

    Projects instances: verify external sync settings · Projects instances: get disk shrink config · Projects instances: get latest recovery time · Projects instances: reschedule maintenance

  3. Databases

    6

    2 read · 3 write · 1 destructive

    Databases: list · Databases: insert · Databases: get · Databases: patch

  4. Backups

    5

    2 read · 2 write · 1 destructive

    Backups: list backups · Backups: create backup · Backups: get backup · Backups: delete backup

  5. Blue green deployments

    5

    2 read · 1 write · 2 destructive

    Blue green deployments: create · Blue green deployments: list · Blue green deployments: get · Blue green deployments: delete

  6. SSL certs

    5

    2 read · 2 write · 1 destructive

    Ssl certs: create ephemeral · Ssl certs: insert · Ssl certs: list · Ssl certs: get

  7. Users

    5

    2 read · 2 write · 1 destructive

    Users: insert · Users: list · Users: get · Users: delete

  8. Workload captures

    5

    1 read · 4 write · 0 destructive

    Workload captures: list · Workload captures: start · Workload captures: start replay · Workload captures: stop

5 more areas · 12 actions
  • Backup runs 4
  • Connect 3
  • Operations 3
  • Flags 1
  • Tiers 1

Top actions

The Google Cloud SQL Admin API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 20 of Google Cloud SQL Admin's 21 action names are shared with at least one other connector, so an agent learns them once.

ActionWhat it doesEffectSame name in
gcp_cloud_sql.databases.listDatabases: listLists databases in the specified Cloud SQL instance.readinfra.database.list7 connectors
gcp_cloud_sql.instances.listInstances: listLists instances under a given project.readinfra.database_instance.list5 connectors
gcp_cloud_sql.backup_runs.listBackup runs: listLists all backup runs associated with the project or a given instance and configuration in the reverse chronological order of the backup initiation time.readinfra.snapshot.list12 connectors
gcp_cloud_sql.backups.list_backupsBackups: list backupsLists all backups associated with the project.readinfra.snapshot.list12 connectors
gcp_cloud_sql.users.listUsers: listLists users in the specified Cloud SQL instance.readinfra.database_user.list7 connectors
gcp_cloud_sql.users.insertUsers: insertCreates a new user in a Cloud SQL instance.writeinfra.database_user.create7 connectors
gcp_cloud_sql.databases.insertDatabases: insertInserts a resource containing information about a database inside a Cloud SQL instance.writeinfra.database.create6 connectors
gcp_cloud_sql.instances.insertInstances: insertCreates a new Cloud SQL instance.writeinfra.database_instance.create4 connectors
gcp_cloud_sql.backup_runs.deleteBackup runs: deleteDeletes the backup taken by a backup run.destructiveinfra.snapshot.delete9 connectors
gcp_cloud_sql.flags.listFlags: listLists all available database flags for Cloud SQL instances.readthis connector
gcp_cloud_sql.tiers.listTiers: listLists all available machine types (tiers) for Cloud SQL, for example, `db-custom-1-3840`.readthis connector
gcp_cloud_sql.instances.cloneInstances: cloneCreates a Cloud SQL instance as a clone of the source instance.writethis connector

Try it

Prompts to paste into Claude.

Each one names the Google Cloud SQL Admin actions it will call, so you know what it reads and what it changes before you send it.

  1. Readread

    Flags: list in Google Cloud SQL Admin and tell me what stands out.

    callsgcp_cloud_sql.flags.list

  2. Writewrite

    Users: insert in Google Cloud SQL Admin. Show me exactly what you will send before you save it.

    callsgcp_cloud_sql.users.insert

Governance for Google Cloud SQL Admin

Destructive actions wait for a yes.

23 Google Cloud SQL Admin actions are destructive. These are all of them:

  • Backup runs: deletegcp_cloud_sql.backup_runs.delete
  • Backups: delete backupgcp_cloud_sql.backups.delete_backup
  • Users: deletegcp_cloud_sql.users.delete
  • Databases: deletegcp_cloud_sql.databases.delete
  • Instances: deletegcp_cloud_sql.instances.delete
  • Instances: demotegcp_cloud_sql.instances.demote
  • Instances: failovergcp_cloud_sql.instances.failover
  • Instances: switchovergcp_cloud_sql.instances.switchover
  • Instances: execute sqlgcp_cloud_sql.instances.execute_sql
  • Instances: stop replicagcp_cloud_sql.instances.stop_replica
  • Instances: truncate loggcp_cloud_sql.instances.truncate_log
  • Instances: demote mastergcp_cloud_sql.instances.demote_master
  • Instances: restore backupgcp_cloud_sql.instances.restore_backup
  • Instances: promote replicagcp_cloud_sql.instances.promote_replica
  • Instances: reset ssl configgcp_cloud_sql.instances.reset_ssl_config
  • Instances: rotate server cagcp_cloud_sql.instances.rotate_server_ca
  • Instances: rotate server certificategcp_cloud_sql.instances.rotate_server_certificate
  • Instances: rotate entra id certificategcp_cloud_sql.instances.rotate_entra_id_certificate
  • Operations: cancelgcp_cloud_sql.operations.cancel
  • Ssl certs: deletegcp_cloud_sql.ssl_certs.delete
  • Blue green deployments: deletegcp_cloud_sql.blue_green_deployments.delete
  • Blue green deployments: switchovergcp_cloud_sql.blue_green_deployments.switchover
  • Projects instances: perform disk shrinkgcp_cloud_sql.projects_instances.perform_disk_shrink

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

dogcp_cloud_sql.backup_runs.deleteconfirm_policy: human

Backup runs: delete?

intent: the user asked me to backup runs: delete

run suspended · waiting for a named person · key gcp-cloud-sql-agent cannot confirm itself
In the console, or from an emailed signed link.
a key for this connector
account {  op: "keys.create", name: "gcp-cloud-sql-agent",  allowed_actions: ["gcp_cloud_sql.*"], cap_calls: 2000,  confirm_policy: "human_for_writes",  approval_rules: [    { match: "gcp_cloud_sql.backup_runs.delete", approver: "[email protected]" },    { match: "gcp_cloud_sql.backups.delete_backup", approver: "[email protected]" },    { match: "gcp_cloud_sql.users.delete", approver: "[email protected]" }  ]}
Illustrative. Scoped to Google Cloud SQL Admin only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

What Google Cloud SQL Admin costs on actionlake.

Every Google Cloud SQL Admin action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Google Cloud SQL Admin refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

  • 1upstream call per actionall 85 Google Cloud SQL Admin actions
  • 5actions pageeach page of a long list is one call
  • 24reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Google Cloud SQL Admin action.

85 actions by area: the id your agent calls, what it does, and its effect.

Instances35
  • gcp_cloud_sql.instances.acquire_ssrs_leaseInstances: acquire ssrs leasewrite
  • gcp_cloud_sql.instances.add_entra_id_certificateInstances: add entra id certificatewrite
  • gcp_cloud_sql.instances.add_server_caInstances: add server cawrite
  • gcp_cloud_sql.instances.add_server_certificateInstances: add server certificatewrite
  • gcp_cloud_sql.instances.cloneInstances: clonewrite
  • gcp_cloud_sql.instances.deleteInstances: deletedestructive
  • gcp_cloud_sql.instances.demoteInstances: demotedestructive
  • gcp_cloud_sql.instances.demote_masterInstances: demote masterdestructive
  • gcp_cloud_sql.instances.execute_sqlInstances: execute sqldestructive
  • gcp_cloud_sql.instances.exportInstances: exportwrite
  • gcp_cloud_sql.instances.failoverInstances: failoverdestructive
  • gcp_cloud_sql.instances.getInstances: getread
  • gcp_cloud_sql.instances.importInstances: importwrite
  • gcp_cloud_sql.instances.insertInstances: insertwrite
  • gcp_cloud_sql.instances.listInstances: listread
  • gcp_cloud_sql.instances.list_entra_id_certificatesInstances: list entra id certificatesread
  • gcp_cloud_sql.instances.list_server_casInstances: list server casread
  • gcp_cloud_sql.instances.list_server_certificatesInstances: list server certificatesread
  • gcp_cloud_sql.instances.patchInstances: patchwrite
  • gcp_cloud_sql.instances.point_in_time_restoreInstances: point in time restorewrite
  • gcp_cloud_sql.instances.pre_check_major_version_upgradeInstances: pre check major version upgraderead
  • gcp_cloud_sql.instances.promote_replicaInstances: promote replicadestructive
  • gcp_cloud_sql.instances.reencryptInstances: reencryptwrite
  • gcp_cloud_sql.instances.release_ssrs_leaseInstances: release ssrs leasewrite
  • gcp_cloud_sql.instances.reset_ssl_configInstances: reset ssl configdestructive
  • gcp_cloud_sql.instances.restartInstances: restartwrite
  • gcp_cloud_sql.instances.restore_backupInstances: restore backupdestructive
  • gcp_cloud_sql.instances.rotate_entra_id_certificateInstances: rotate entra id certificatedestructive
  • gcp_cloud_sql.instances.rotate_server_caInstances: rotate server cadestructive
  • gcp_cloud_sql.instances.rotate_server_certificateInstances: rotate server certificatedestructive
  • gcp_cloud_sql.instances.start_replicaInstances: start replicawrite
  • gcp_cloud_sql.instances.stop_replicaInstances: stop replicadestructive
  • gcp_cloud_sql.instances.switchoverInstances: switchoverdestructive
  • gcp_cloud_sql.instances.truncate_logInstances: truncate logdestructive
  • gcp_cloud_sql.instances.updateInstances: updatewrite
Projects instances7
  • gcp_cloud_sql.projects_instances.get_disk_shrink_configProjects instances: get disk shrink configread
  • gcp_cloud_sql.projects_instances.get_latest_recovery_timeProjects instances: get latest recovery timeread
  • gcp_cloud_sql.projects_instances.perform_disk_shrinkProjects instances: perform disk shrinkdestructive
  • gcp_cloud_sql.projects_instances.reschedule_maintenanceProjects instances: reschedule maintenancewrite
  • gcp_cloud_sql.projects_instances.reset_replica_sizeProjects instances: reset replica sizewrite
  • gcp_cloud_sql.projects_instances.start_external_syncProjects instances: start external syncwrite
  • gcp_cloud_sql.projects_instances.verify_external_sync_settingsProjects instances: verify external sync settingsread
Databases6
  • gcp_cloud_sql.databases.deleteDatabases: deletedestructive
  • gcp_cloud_sql.databases.getDatabases: getread
  • gcp_cloud_sql.databases.insertDatabases: insertwrite
  • gcp_cloud_sql.databases.listDatabases: listread
  • gcp_cloud_sql.databases.patchDatabases: patchwrite
  • gcp_cloud_sql.databases.updateDatabases: updatewrite
Backups5
  • gcp_cloud_sql.backups.create_backupBackups: create backupwrite
  • gcp_cloud_sql.backups.delete_backupBackups: delete backupdestructive
  • gcp_cloud_sql.backups.get_backupBackups: get backupread
  • gcp_cloud_sql.backups.list_backupsBackups: list backupsread
  • gcp_cloud_sql.backups.update_backupBackups: update backupwrite
Blue green deployments5
  • gcp_cloud_sql.blue_green_deployments.createBlue green deployments: createwrite
  • gcp_cloud_sql.blue_green_deployments.deleteBlue green deployments: deletedestructive
  • gcp_cloud_sql.blue_green_deployments.getBlue green deployments: getread
  • gcp_cloud_sql.blue_green_deployments.listBlue green deployments: listread
  • gcp_cloud_sql.blue_green_deployments.switchoverBlue green deployments: switchoverdestructive
SSL certs5
  • gcp_cloud_sql.ssl_certs.create_ephemeralSsl certs: create ephemeralwrite
  • gcp_cloud_sql.ssl_certs.deleteSsl certs: deletedestructive
  • gcp_cloud_sql.ssl_certs.getSsl certs: getread
  • gcp_cloud_sql.ssl_certs.insertSsl certs: insertwrite
  • gcp_cloud_sql.ssl_certs.listSsl certs: listread
Users5
  • gcp_cloud_sql.users.deleteUsers: deletedestructive
  • gcp_cloud_sql.users.getUsers: getread
  • gcp_cloud_sql.users.insertUsers: insertwrite
  • gcp_cloud_sql.users.listUsers: listread
  • gcp_cloud_sql.users.updateUsers: updatewrite
Workload captures5
  • gcp_cloud_sql.workload_captures.listWorkload captures: listread
  • gcp_cloud_sql.workload_captures.startWorkload captures: startwrite
  • gcp_cloud_sql.workload_captures.start_replayWorkload captures: start replaywrite
  • gcp_cloud_sql.workload_captures.stopWorkload captures: stopwrite
  • gcp_cloud_sql.workload_captures.stop_replayWorkload captures: stop replaywrite
Backup runs4
  • gcp_cloud_sql.backup_runs.deleteBackup runs: deletedestructive
  • gcp_cloud_sql.backup_runs.getBackup runs: getread
  • gcp_cloud_sql.backup_runs.insertBackup runs: insertwrite
  • gcp_cloud_sql.backup_runs.listBackup runs: listread
Connect3
  • gcp_cloud_sql.connect.generate_ephemeral_certConnect: generate ephemeral certwrite
  • gcp_cloud_sql.connect.getConnect: getread
  • gcp_cloud_sql.connect.resolveConnect: resolveread
Operations3
  • gcp_cloud_sql.operations.cancelOperations: canceldestructive
  • gcp_cloud_sql.operations.getOperations: getread
  • gcp_cloud_sql.operations.listOperations: listread
Flags1
  • gcp_cloud_sql.flags.listFlags: listread
Tiers1
  • gcp_cloud_sql.tiers.listTiers: listread

Questions

The Google Cloud SQL Admin MCP server, answered.

Is there a Google Cloud SQL Admin MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 85 Google Cloud SQL Admin actions across instances, projects instances, databases and backups, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Google Cloud SQL Admin.

What do I need to connect Google Cloud SQL Admin?

Your own Google Cloud SQL Admin OAuth app, registered with Google Cloud SQL Admin (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Google Cloud SQL Admin app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. The free call account { op: "connections.requirements", service: "gcp_cloud_sql" } lists exactly what to paste.

Can an AI agent delete or change things in Google Cloud SQL Admin?

Only if its key allows it, and only with an explicit confirmation. 23 Google Cloud SQL Admin actions are destructive, including backup runs: delete, backups: delete backup and users: delete. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

Will an AI agent use up my Google Cloud SQL Admin API limit?

actionlake paces every call to the limits in the Google Cloud SQL Admin service file: 600 calls a minute per connection. Repeated reads are answered from cache (24 Google Cloud SQL Admin actions can be), which never reaches Google Cloud SQL Admin.

What does a Google Cloud SQL Admin action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (5 Google Cloud SQL Admin actions page). Cache hits, searches, dry runs and calls Google Cloud SQL Admin refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Google Cloud SQL Admin API does it cover?

The Google Cloud SQL Admin (instances, databases, users, backups, replicas, certificates, operations) API sqladmin v1 (Discovery revision 20260929) at sqladmin.googleapis.com. It is built from Google Cloud SQL Admin's documentation as read on 23 October 2026. 85 actions in 13 areas, each one in the signed service file (version 1.0.0).

Does actionlake keep my Google Cloud SQL Admin data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Google Cloud SQL Admin credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

More connectors like Google Cloud SQL Admin

Shares the most action names with

Joins with, on shared entities

Browse

actionlake is independent. It is not made or endorsed by Google Cloud SQL Admin; the name is the vendor's own. Counts are from the Google Cloud SQL Admin service file, version 1.0.0.

Give your agent Google Cloud SQL Admin today.

Connect Google Cloud SQL Admin freeSee pricing

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.