Google Cloud SQL, verified
MCP server by Google Cloud · Verified
Create and manage Cloud SQL instances, users and backups, and run SQL queries against them.
Connect to Google Cloud SQL
Google Cloud SQL needs sign-in. Connect with its own URL:
Your client opens Google Cloud’s sign-in the first time you use it. The token stays between your client and Google Cloud.
Share this server
Opens this page, with the URL and setup steps.
mcp.tc/i/cloud-sqlAbout
Connects to the Cloud SQL Admin API for MySQL, PostgreSQL and SQL Server. You can list, create, clone and update instances, manage database users, take and restore backups, import data, and run SQL statements, including a read-only query tool. Long-running operations are tracked with a status tool.
Runs as a hosted streamable HTTP endpoint at https://sqladmin.googleapis.com/mcp. Access uses Google OAuth 2.0 and IAM permissions on your project. SQL execution requires the instance to have Data API access enabled and, for IAM users, IAM database authentication turned on.
What you can do
- List and inspect Cloud SQL instances
- Create, clone and update instances
- Create and update database users
- Run read-only or full SQL statements
- Take and restore backups
- Import data from Cloud Storage
- Check long-running operation status
- Run PostgreSQL major version upgrade prechecks
Tools 15
list_instancesRead-onlyList all Cloud SQL instances in a project.
get_instanceRead-onlyGet the details of a Cloud SQL instance.
create_instanceWritesStart creating a Cloud SQL instance as a long-running operation.
execute_sqlCan deleteRun any SQL statement (DDL, DCL, DQL, DML) on an instance.
execute_sql_readonlyRead-onlyRun a read-only SQL statement on an instance.
get_operationRead-onlyGet the status of a long-running operation.
create_userWritesCreate a built-in or IAM database user on an instance.
update_userWritesUpdate a database user's roles on an instance.
clone_instanceWritesCreate an instance as a clone of a source instance.
update_instanceCan deletePartially update an instance's configuration settings.
list_usersRead-onlyList all database users for an instance.
create_backupWritesTake a backup of an instance.
Show 3 more tools
restore_backupCan deleteRestore a backup to a Cloud SQL instance.
import_dataWritesImport data from Cloud Storage into an instance.
postgres_upgrade_precheckWritesCheck if a PostgreSQL instance is ready for a major version upgrade.
Read from the live server on 17 Nov 2026. Read-only, Writes and Can delete are hints the server declares; your client decides whether to ask before running a tool.
Example prompts
List all Cloud SQL instances in my project my-project
Create a backup of the orders-db instance
Run a read-only query to count rows in the users table on prod-pg
Check whether prod-pg is ready to upgrade to POSTGRES_15
Set up
Every client connects to sqladmin.googleapis.com, and Google Cloud asks you to sign in the first time. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport http cloud-sql https://sqladmin.googleapis.com/mcp- Start Claude Code, type
/mcp, pick cloud-sql and choose Authenticate. A browser window opens for the Google Cloud sign-in.
Add --scope user to make it available in every project, not just this one.
Claude Desktop
- Open Customize → Connectors, click + Add, then Add custom connector.
- Name it Google Cloud SQL and paste this URL:
https://sqladmin.googleapis.com/mcp- Click Add, then Connect, and sign in when Google Cloud asks.
Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.
claude.ai
- Open the connector form on claude.ai. This button fills in the name and URL for you:
Add to claude.ai (opens in a new tab)
- Check that the URL reads
https://sqladmin.googleapis.com/mcpand click Add. - Click Connect and sign in when Google Cloud asks.
Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.
ChatGPT
- On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
- Enter a name for the server.
- Under Connection, paste
https://sqladmin.googleapis.com/mcpas the server URL, then for authentication choose OAuth. ChatGPT sends you to Google Cloud to sign in. - Check I understand and want to continue, then select Create as a plugin.
Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"cloud-sql": {
"url": "https://sqladmin.googleapis.com/mcp"
}
}
}Cursor shows Needs authentication next to the server. Click the button beside it to sign in.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"cloud-sql","type":"http","url":"https://sqladmin.googleapis.com/mcp"}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"cloud-sql": {
"type": "http",
"url": "https://sqladmin.googleapis.com/mcp"
}
}
}VS Code asks you to sign in the first time the server starts.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"cloud-sql": {
"serverUrl": "https://sqladmin.googleapis.com/mcp"
}
}
}- Refresh the MCP server list in Cascade and sign in when asked.
Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.
Codex
codex mcp add cloud-sql --url https://sqladmin.googleapis.com/mcp
codex mcp login cloud-sqlOr edit ~/.codex/config.toml directly:
[mcp_servers.cloud-sql]
url = "https://sqladmin.googleapis.com/mcp"Gemini CLI
gemini mcp add --transport http cloud-sql https://sqladmin.googleapis.com/mcpThen, inside Gemini CLI, run /mcp auth cloud-sql to sign in.
This adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.
{
"mcpServers": {
"cloud-sql": {
"type": "http",
"url": "https://sqladmin.googleapis.com/mcp"
}
}
}Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.
Client only starts local servers? Bridge it with npx -y mcp-remote https://sqladmin.googleapis.com/mcp.
Embed
Show Google Cloud SQL in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/cloud-sql)<a href="https://mcp.tc/i/cloud-sql"><img src="https://mcp.tc/i/cloud-sql/badge.svg" alt="Google Cloud SQL on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/cloud-sql.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/cloud-sql" title="Google Cloud SQL on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/cloud-sql.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Google Cloud SQL card to your site.
Add the mcp.tc card for Google Cloud SQL, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/cloud-sql.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="cloud-sql"><a href="https://mcp.tc/i/cloud-sql">Google Cloud SQL on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/cloud-sql)
```
Reference: https://mcp.tc/embedChange history
We read this server’s tool list every 3 hours and record what changes. Last read 18 Nov 2026, 05:33 UTC.
-
3 tools changed.
Details, 4 Nov 2026, 17:54 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. *
Afteryou use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the`execute_sql` tool and the `executeSql` API. Un…AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For
built_inuserspassword_secret_version must be set. * Otherwise,for IAMusers, for a MySQL instance,thedatabase flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance,thedatabase flag `cloudsql.iam_authentication`must beset to `on`. * After you usethe`create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently loggedintotheproject. The `execute_sql` tool hasthefollowing limitations: * If aSQLstatement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
execute_sql_readonlydescriptionBeforeExecute any valid
read onlySQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * ForaMySQLinstance,thedatabase flag `cloudsql_iam_authentication` must be set to `on`.Fora PostgreSQL instance, thedatabaseflag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) isrequiredto call the `execute_sql_readonly` tool. The tool executes theSQLstatements using the privileges of the database user logged withIAM databaseauthentication. After you usethe`create_instance` tool to create an instance, you can usethe`create_user` tool to create an IAM user account fortheuser currently loggedintotheproject. The `execute_sql_readonly` tool hasthefollowing limitations: * If aSQLstatement returns a response larger than 10 MB, t…AfterExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
-
3 tools changed.
Details, 4 Nov 2026, 02:47 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. *
For MySQL and PostgreSQL instances, afteryou use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the`execute_sq…AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL
for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Serverinstance. To support the `execute_sql` tool, a Cloud SQL instanceand requestmust meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * ForPostgreSQL and SQL Server instances,the`database` field is required.ForMySQL instances,the`database` field is optional. * For built-indatabaseusers (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication):*Specifythe`user` field andthe`password_secret_version` field. * The value of `password_secret_version` must betheresource name of a regional secret versioninSecret Manager stored inthesame region astheCloudSQLinstance, such…AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
execute_sql_readonlydescriptionBeforeExecute any valid
read-onlySQL statement on a Cloud SQLfor MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Serverinstance. To support the `execute_sql_readonly` tool, a Cloud SQL instanceand requestmust meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * ForPostgreSQL and SQL Server instances,the`database` field is required.ForMySQL instances,the`database` fieldisoptional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, andrequiredforSQLServer because Cloud SQL for SQL Server doesn't supportIAM databaseauthentication): * Specifythe`user` field andthe`password_secret_version` field. * The value of `password_secret_version` must betheresource name of a regional secret versioninSecret Manager stored inthesame region astheCloudSQLinstance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…AfterExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
-
3 tools changed.
Details, 3 Nov 2026, 17:49 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. *
Afteryou use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the`execute_sql` tool and the `executeSql` API. Un…AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For
built_inuserspassword_secret_version must be set. * Otherwise,for IAMusers, for a MySQL instance,thedatabase flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance,thedatabase flag `cloudsql.iam_authentication`must beset to `on`. * After you usethe`create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently loggedintotheproject. The `execute_sql` tool hasthefollowing limitations: * If aSQLstatement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
execute_sql_readonlydescriptionBeforeExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
AfterExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
-
3 tools changed.
Details, 3 Nov 2026, 05:42 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
execute_sql_readonlydescriptionBeforeExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
AfterExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
-
3 tools changed.
Details, 2 Nov 2026, 23:39 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
execute_sql_readonlydescriptionBeforeExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
AfterExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
-
3 tools changed.
Details, 2 Nov 2026, 08:44 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
execute_sql_readonlydescriptionBeforeExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
AfterExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
-
3 tools changed.
Details, 1 Nov 2026, 11:50 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
execute_sql_readonlydescriptionBeforeExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
AfterExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
-
3 tools changed.
Details, 1 Nov 2026, 05:42 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
execute_sqldescriptionBeforeExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such…
AfterExecute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool ha…
execute_sql_readonlydescriptionBeforeExecute any valid read-only SQL statement on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secret…
AfterExecute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, t…
-
3 tools changed.
Details, 31 Oct 2026, 20:47 UTC
Changed 3
create_instancedescriptionBeforeInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sql` tool and the `executeSql` API. Un…
AfterInitiates the creation of a Cloud SQL instance. * The tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * The instance creation operation can take several minutes. Use a command line tool to pause for 30 seconds before rechecking the status. * For MySQL and PostgreSQL instances, after you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. * IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect or a Private Service Access instance. * Set `free_trial` to 'true' to create a free trial instance. Free trial instances let you test majority of Cloud SQL features for up to 30 days without financial commitment. Subject to eligibility and availability. * The value of `data_api_access` is set to `ALLOW_DATA_API` by default. This setting lets you execute SQL statements using the `execute_sq…
execute_sqlexecute_sql_readonlyPart of this entry is left out to keep the page short.
-
10 tools changed.
Details, 24 Oct 2026, 10:37 UTC
Changed 10
clone_instancecreate_backupcreate_instancecreate_userget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userPart of this entry is left out to keep the page short.
-
10 tools changed.
Details, 24 Oct 2026, 04:41 UTC
Changed 10
clone_instancecreate_backupcreate_instancecreate_userget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
10 tools changed.
Details, 24 Oct 2026, 01:38 UTC
Changed 10
clone_instancecreate_backupcreate_instancecreate_userget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
10 tools changed.
Details, 23 Oct 2026, 07:39 UTC
Changed 10
clone_instancecreate_backupcreate_instancecreate_userget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
10 tools changed.
Details, 22 Oct 2026, 16:43 UTC
Changed 10
clone_instancecreate_backupcreate_instancecreate_userget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
13 tools changed.
Details, 15 Oct 2026, 01:30 UTC
Changed 13
clone_instancecreate_backupcreate_instancecreate_userexecute_sqlexecute_sql_readonlyget_instanceget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
13 tools changed.
Details, 14 Oct 2026, 22:32 UTC
Changed 13
clone_instancecreate_backupcreate_instancecreate_userexecute_sqlexecute_sql_readonlyget_instanceget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
13 tools changed.
Details, 13 Oct 2026, 10:33 UTC
Changed 13
clone_instancecreate_backupcreate_instancecreate_userexecute_sqlexecute_sql_readonlyget_instanceget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
13 tools changed.
Details, 13 Oct 2026, 04:39 UTC
Changed 13
clone_instancecreate_backupcreate_instancecreate_userexecute_sqlexecute_sql_readonlyget_instanceget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
13 tools changed.
Details, 13 Oct 2026, 01:37 UTC
Changed 13
clone_instancecreate_backupcreate_instancecreate_userexecute_sqlexecute_sql_readonlyget_instanceget_operationimport_datapostgres_upgrade_precheckrestore_backupupdate_instanceupdate_userThe 10 newest entries show every detail; older ones show names only.
-
Tracking started: 15 tools.
FAQ
Can I paste mcp.tc/i/cloud-sql into my MCP client?
No. mcp.tc links are pages, not server addresses. Connect with https://sqladmin.googleapis.com/mcp, so your client talks to Google Cloud SQL directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.
Does Google Cloud SQL need an API key or a sign-in?
Yes, you need a Google Cloud account. The first time your client connects, it opens Google Cloud’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.
Is Google Cloud SQL a remote or a local server?
Remote. Google Cloud hosts it at https://sqladmin.googleapis.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.
What can Google Cloud SQL do?
It has 15 tools, including list_instances, get_instance and create_instance. You can list and inspect Cloud SQL instances, create, clone and update instances and create and update database users.
Which clients can use it?
Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.
Does mcp.tc track changes to Google Cloud SQL?
Yes. Google Cloud SQL’s History tab shows each change we find to its tools, down to descriptions and parameters, plus new versions and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read Google Cloud SQL’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Google Cloud. This page was built from Google Cloud SQL’s public metadata, last checked on 17 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.