--- title: "Google Cloud SQL Admin MCP server for AI agents - actionlake" description: "Give Claude 85 Google Cloud SQL Admin actions through one MCP server: instances. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/google-cloud-sql-admin updated: 2026-10-23 --- 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/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 ``` - 85 actions in one signed file - 28 read look, never change - 34 write create and update - 23 wait for a yes destructive, 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_token` Access token from one sign-in with your own OAuth app - `refresh_token` Refresh token from the same sign-in; the access token is renewed from it - `client_id` Google OAuth client id (Google Cloud console > APIs & Services > Credentials; enable the Cloud SQL Admin API on the… - `client_secret` Google 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 call check { 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_token` `refresh_token` `client_id` `client_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 2026[sqladmin.googleapis.com](https://sqladmin.googleapis.com/$discovery/rest?version=v1) [cloud.google.com](https://cloud.google.com/sql/docs/mysql/admin-api/rest) **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. - **28** read look, never change - **34** write create and update - **23** destructive wait 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. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `gcp_cloud_sql.databases.list` Databases: list | Lists databases in the specified Cloud SQL instance. | read | `infra.database.list` 7 connectors | | `gcp_cloud_sql.instances.list` Instances: list | Lists instances under a given project. | read | `infra.database_instance.list` 5 connectors | | `gcp_cloud_sql.backup_runs.list` Backup runs: list | Lists all backup runs associated with the project or a given instance and configuration in the reverse chronological order of the backup initiation time. | read | `infra.snapshot.list` 12 connectors | | `gcp_cloud_sql.backups.list_backups` Backups: list backups | Lists all backups associated with the project. | read | `infra.snapshot.list` 12 connectors | | `gcp_cloud_sql.users.list` Users: list | Lists users in the specified Cloud SQL instance. | read | `infra.database_user.list` 7 connectors | | `gcp_cloud_sql.users.insert` Users: insert | Creates a new user in a Cloud SQL instance. | write | `infra.database_user.create` 7 connectors | | `gcp_cloud_sql.databases.insert` Databases: insert | Inserts a resource containing information about a database inside a Cloud SQL instance. | write | `infra.database.create` 6 connectors | | `gcp_cloud_sql.instances.insert` Instances: insert | Creates a new Cloud SQL instance. | write | `infra.database_instance.create` 4 connectors | | `gcp_cloud_sql.backup_runs.delete` Backup runs: delete | Deletes the backup taken by a backup run. | destructive | `infra.snapshot.delete` 9 connectors | | `gcp_cloud_sql.flags.list` Flags: list | Lists all available database flags for Cloud SQL instances. | read | this connector | | `gcp_cloud_sql.tiers.list` Tiers: list | Lists all available machine types (tiers) for Cloud SQL, for example, `db-custom-1-3840`. | read | this connector | | `gcp_cloud_sql.instances.clone` Instances: clone | Creates a Cloud SQL instance as a clone of the source instance. | write | this 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. Read read Flags: list in Google Cloud SQL Admin and tell me what stands out. calls `gcp_cloud_sql.flags.list` 2. Write write Users: insert in Google Cloud SQL Admin. Show me exactly what you will send before you save it. calls `gcp_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: delete `gcp_cloud_sql.backup_runs.delete` - Backups: delete backup `gcp_cloud_sql.backups.delete_backup` - Users: delete `gcp_cloud_sql.users.delete` - Databases: delete `gcp_cloud_sql.databases.delete` - Instances: delete `gcp_cloud_sql.instances.delete` - Instances: demote `gcp_cloud_sql.instances.demote` - Instances: failover `gcp_cloud_sql.instances.failover` - Instances: switchover `gcp_cloud_sql.instances.switchover` - Instances: execute sql `gcp_cloud_sql.instances.execute_sql` - Instances: stop replica `gcp_cloud_sql.instances.stop_replica` - Instances: truncate log `gcp_cloud_sql.instances.truncate_log` - Instances: demote master `gcp_cloud_sql.instances.demote_master` - Instances: restore backup `gcp_cloud_sql.instances.restore_backup` - Instances: promote replica `gcp_cloud_sql.instances.promote_replica` - Instances: reset ssl config `gcp_cloud_sql.instances.reset_ssl_config` - Instances: rotate server ca `gcp_cloud_sql.instances.rotate_server_ca` - Instances: rotate server certificate `gcp_cloud_sql.instances.rotate_server_certificate` - Instances: rotate entra id certificate `gcp_cloud_sql.instances.rotate_entra_id_certificate` - Operations: cancel `gcp_cloud_sql.operations.cancel` - Ssl certs: delete `gcp_cloud_sql.ssl_certs.delete` - Blue green deployments: delete `gcp_cloud_sql.blue_green_deployments.delete` - Blue green deployments: switchover `gcp_cloud_sql.blue_green_deployments.switchover` - Projects instances: perform disk shrink `gcp_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. do gcp_cloud_sql.backup_runs.delete confirm_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: "lead@example.com" }, { match: "gcp_cloud_sql.backups.delete_backup", approver: "lead@example.com" }, { match: "gcp_cloud_sql.users.delete", approver: "lead@example.com" } ] } ``` 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. - 1 upstream call per action all 85 Google Cloud SQL Admin actions - 5 actions page each page of a long list is one call - 24 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Google Cloud SQL Admin action. 85 actions by area: the id your agent calls, what it does, and its effect. **Instances 35** - `gcp_cloud_sql.instances.acquire_ssrs_lease` Instances: acquire ssrs lease write - `gcp_cloud_sql.instances.add_entra_id_certificate` Instances: add entra id certificate write - `gcp_cloud_sql.instances.add_server_ca` Instances: add server ca write - `gcp_cloud_sql.instances.add_server_certificate` Instances: add server certificate write - `gcp_cloud_sql.instances.clone` Instances: clone write - `gcp_cloud_sql.instances.delete` Instances: delete destructive - `gcp_cloud_sql.instances.demote` Instances: demote destructive - `gcp_cloud_sql.instances.demote_master` Instances: demote master destructive - `gcp_cloud_sql.instances.execute_sql` Instances: execute sql destructive - `gcp_cloud_sql.instances.export` Instances: export write - `gcp_cloud_sql.instances.failover` Instances: failover destructive - `gcp_cloud_sql.instances.get` Instances: get read - `gcp_cloud_sql.instances.import` Instances: import write - `gcp_cloud_sql.instances.insert` Instances: insert write - `gcp_cloud_sql.instances.list` Instances: list read - `gcp_cloud_sql.instances.list_entra_id_certificates` Instances: list entra id certificates read - `gcp_cloud_sql.instances.list_server_cas` Instances: list server cas read - `gcp_cloud_sql.instances.list_server_certificates` Instances: list server certificates read - `gcp_cloud_sql.instances.patch` Instances: patch write - `gcp_cloud_sql.instances.point_in_time_restore` Instances: point in time restore write - `gcp_cloud_sql.instances.pre_check_major_version_upgrade` Instances: pre check major version upgrade read - `gcp_cloud_sql.instances.promote_replica` Instances: promote replica destructive - `gcp_cloud_sql.instances.reencrypt` Instances: reencrypt write - `gcp_cloud_sql.instances.release_ssrs_lease` Instances: release ssrs lease write - `gcp_cloud_sql.instances.reset_ssl_config` Instances: reset ssl config destructive - `gcp_cloud_sql.instances.restart` Instances: restart write - `gcp_cloud_sql.instances.restore_backup` Instances: restore backup destructive - `gcp_cloud_sql.instances.rotate_entra_id_certificate` Instances: rotate entra id certificate destructive - `gcp_cloud_sql.instances.rotate_server_ca` Instances: rotate server ca destructive - `gcp_cloud_sql.instances.rotate_server_certificate` Instances: rotate server certificate destructive - `gcp_cloud_sql.instances.start_replica` Instances: start replica write - `gcp_cloud_sql.instances.stop_replica` Instances: stop replica destructive - `gcp_cloud_sql.instances.switchover` Instances: switchover destructive - `gcp_cloud_sql.instances.truncate_log` Instances: truncate log destructive - `gcp_cloud_sql.instances.update` Instances: update write **Projects instances 7** - `gcp_cloud_sql.projects_instances.get_disk_shrink_config` Projects instances: get disk shrink config read - `gcp_cloud_sql.projects_instances.get_latest_recovery_time` Projects instances: get latest recovery time read - `gcp_cloud_sql.projects_instances.perform_disk_shrink` Projects instances: perform disk shrink destructive - `gcp_cloud_sql.projects_instances.reschedule_maintenance` Projects instances: reschedule maintenance write - `gcp_cloud_sql.projects_instances.reset_replica_size` Projects instances: reset replica size write - `gcp_cloud_sql.projects_instances.start_external_sync` Projects instances: start external sync write - `gcp_cloud_sql.projects_instances.verify_external_sync_settings` Projects instances: verify external sync settings read **Databases 6** - `gcp_cloud_sql.databases.delete` Databases: delete destructive - `gcp_cloud_sql.databases.get` Databases: get read - `gcp_cloud_sql.databases.insert` Databases: insert write - `gcp_cloud_sql.databases.list` Databases: list read - `gcp_cloud_sql.databases.patch` Databases: patch write - `gcp_cloud_sql.databases.update` Databases: update write **Backups 5** - `gcp_cloud_sql.backups.create_backup` Backups: create backup write - `gcp_cloud_sql.backups.delete_backup` Backups: delete backup destructive - `gcp_cloud_sql.backups.get_backup` Backups: get backup read - `gcp_cloud_sql.backups.list_backups` Backups: list backups read - `gcp_cloud_sql.backups.update_backup` Backups: update backup write **Blue green deployments 5** - `gcp_cloud_sql.blue_green_deployments.create` Blue green deployments: create write - `gcp_cloud_sql.blue_green_deployments.delete` Blue green deployments: delete destructive - `gcp_cloud_sql.blue_green_deployments.get` Blue green deployments: get read - `gcp_cloud_sql.blue_green_deployments.list` Blue green deployments: list read - `gcp_cloud_sql.blue_green_deployments.switchover` Blue green deployments: switchover destructive **SSL certs 5** - `gcp_cloud_sql.ssl_certs.create_ephemeral` Ssl certs: create ephemeral write - `gcp_cloud_sql.ssl_certs.delete` Ssl certs: delete destructive - `gcp_cloud_sql.ssl_certs.get` Ssl certs: get read - `gcp_cloud_sql.ssl_certs.insert` Ssl certs: insert write - `gcp_cloud_sql.ssl_certs.list` Ssl certs: list read **Users 5** - `gcp_cloud_sql.users.delete` Users: delete destructive - `gcp_cloud_sql.users.get` Users: get read - `gcp_cloud_sql.users.insert` Users: insert write - `gcp_cloud_sql.users.list` Users: list read - `gcp_cloud_sql.users.update` Users: update write **Workload captures 5** - `gcp_cloud_sql.workload_captures.list` Workload captures: list read - `gcp_cloud_sql.workload_captures.start` Workload captures: start write - `gcp_cloud_sql.workload_captures.start_replay` Workload captures: start replay write - `gcp_cloud_sql.workload_captures.stop` Workload captures: stop write - `gcp_cloud_sql.workload_captures.stop_replay` Workload captures: stop replay write **Backup runs 4** - `gcp_cloud_sql.backup_runs.delete` Backup runs: delete destructive - `gcp_cloud_sql.backup_runs.get` Backup runs: get read - `gcp_cloud_sql.backup_runs.insert` Backup runs: insert write - `gcp_cloud_sql.backup_runs.list` Backup runs: list read **Connect 3** - `gcp_cloud_sql.connect.generate_ephemeral_cert` Connect: generate ephemeral cert write - `gcp_cloud_sql.connect.get` Connect: get read - `gcp_cloud_sql.connect.resolve` Connect: resolve read **Operations 3** - `gcp_cloud_sql.operations.cancel` Operations: cancel destructive - `gcp_cloud_sql.operations.get` Operations: get read - `gcp_cloud_sql.operations.list` Operations: list read **Flags 1** - `gcp_cloud_sql.flags.list` Flags: list read **Tiers 1** - `gcp_cloud_sql.tiers.list` Tiers: list read 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 - [Fly.io Machines 13](https://actionlake.com/connectors/fly-io-machines) - [PlanetScale 10](https://actionlake.com/connectors/planetscale) - [MongoDB Atlas 10](https://actionlake.com/connectors/mongodb-atlas) - [Render 9](https://actionlake.com/connectors/render) - [ClickHouse Cloud 7](https://actionlake.com/connectors/clickhouse-cloud) - [Laravel Forge 4](https://actionlake.com/connectors/laravel-forge) Joins with, on shared entities - [NetBox 1](https://actionlake.com/connectors/netbox) - [DigitalOcean 1](https://actionlake.com/connectors/digitalocean) - [Appwrite Cloud 1](https://actionlake.com/connectors/appwrite-cloud) - [Metabase 1](https://actionlake.com/connectors/metabase) - [Vultr 1](https://actionlake.com/connectors/vultr) - [Azure SQL Database 1](https://actionlake.com/connectors/azure-sql-database) Browse - [All Developer & infrastructure connectors](https://actionlake.com/connectors/category/developer-and-infrastructure) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) 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 free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/google-cloud-sql-admin More: https://actionlake.com/llms.txt