Wir und ausgewählte Dritte verwenden Cookies oder ähnliche Technologien für technische Zwecke und, mit deiner Einwilligung, um zu analysieren, wie die Website genutzt wird.

Du kannst deine Einwilligung jederzeit frei erteilen, verweigern oder widerrufen.

Google Cloud SQL, verifiziert

MCP-Server von Google Cloud · Verifiziert

Cloud-SQL-Instanzen, Benutzer und Backups erstellen und verwalten sowie SQL-Abfragen darauf ausführen.

OAuth-Anmeldung (Beim ersten Verbinden meldest du dich beim Anbieter an)Streamable HTTP

Mit Google Cloud SQL verbinden

Google Cloud SQL braucht eine Anmeldung. Verbinde dich mit seiner eigenen URL:

https://sqladmin.googleapis.com/mcp

Dein Client öffnet beim ersten Mal die Anmeldung von Google Cloud. Das Token bleibt zwischen deinem Client und Google Cloud.

Diesen Server teilen

Öffnet diese Seite mit der URL und den Einrichtungsschritten.

mcp.tc/i/cloud-sql

Über den Server

Verbindet sich mit der Cloud SQL Admin API für MySQL, PostgreSQL und SQL Server. Du kannst Instanzen auflisten, erstellen, klonen und aktualisieren, Datenbankbenutzer verwalten, Backups erstellen und wiederherstellen, Daten importieren und SQL-Anweisungen ausführen, auch mit einem schreibgeschützten Abfrage-Tool. Lang laufende Operationen werden mit einem Status-Tool verfolgt.

Er läuft als gehosteter Streamable-HTTP-Endpunkt unter https://sqladmin.googleapis.com/mcp. Der Zugriff verwendet Google OAuth 2.0 und IAM-Berechtigungen für dein Projekt. Für die SQL-Ausführung muss bei der Instanz der Data-API-Zugriff aktiviert sein und für IAM-Benutzer die IAM-Datenbankauthentifizierung eingeschaltet sein.

Was du damit machen kannst

  • Cloud-SQL-Instanzen auflisten und prüfen
  • Instanzen erstellen, klonen und aktualisieren
  • Datenbankbenutzer anlegen und aktualisieren
  • SQL-Anweisungen schreibgeschützt oder uneingeschränkt ausführen
  • Backups erstellen und wiederherstellen
  • Daten aus Cloud Storage importieren
  • Status lang laufender Operationen prüfen
  • Vorabprüfungen für PostgreSQL-Hauptversions-Upgrades ausführen

Tools 15

  • list_instancesLiest nur

    Listet alle Cloud-SQL-Instanzen in einem Projekt auf.

  • get_instanceLiest nur

    Ruft die Details einer Cloud-SQL-Instanz ab.

  • create_instanceSchreibt

    Startet die Erstellung einer Cloud-SQL-Instanz als lang laufende Operation.

  • execute_sqlKann löschen

    Führt eine beliebige SQL-Anweisung (DDL, DCL, DQL, DML) auf einer Instanz aus.

  • execute_sql_readonlyLiest nur

    Führt eine schreibgeschützte SQL-Anweisung auf einer Instanz aus.

  • get_operationLiest nur

    Ruft den Status einer lang laufenden Operation ab.

  • create_userSchreibt

    Erstellt auf einer Instanz einen integrierten Datenbankbenutzer oder einen IAM-Datenbankbenutzer.

  • update_userSchreibt

    Aktualisiert die Rollen eines Datenbankbenutzers auf einer Instanz.

  • clone_instanceSchreibt

    Erstellt eine Instanz als Klon einer Quellinstanz.

  • update_instanceKann löschen

    Aktualisiert die Konfigurationseinstellungen einer Instanz teilweise.

  • list_usersLiest nur

    Listet alle Datenbankbenutzer einer Instanz auf.

  • create_backupSchreibt

    Erstellt ein Backup einer Instanz.

3 weitere Tools anzeigen
  • restore_backupKann löschen

    Stellt ein Backup auf einer Cloud-SQL-Instanz wieder her.

  • import_dataSchreibt

    Importiert Daten aus Cloud Storage in eine Instanz.

  • postgres_upgrade_precheckSchreibt

    Prüft, ob eine PostgreSQL-Instanz für ein Hauptversions-Upgrade bereit ist.

Am 17. Nov. 2026 vom laufenden Server gelesen. „Liest nur“, „Schreibt“ und „Kann löschen“ sind Hinweise, die der Server selbst angibt; dein Client entscheidet, ob er vor dem Ausführen eines Tools nachfragt.

Beispiel-Prompts

  • Liste alle Cloud-SQL-Instanzen in meinem Projekt my-project auf

  • Erstelle ein Backup der Instanz orders-db

  • Führe eine schreibgeschützte Abfrage aus, die die Zeilen der Tabelle users auf prod-pg zählt

  • Prüfe, ob prod-pg bereit für das Upgrade auf POSTGRES_15 ist

Einrichtung

Jeder Client verbindet sich mit sqladmin.googleapis.com, und beim ersten Mal fragt Google Cloud nach deiner Anmeldung. Wähl deinen; die Seite merkt sich deine Wahl.

Claude Code

  1. Führe das in einem Terminal in deinem Projektordner aus:
claude mcp add --transport http cloud-sql https://sqladmin.googleapis.com/mcp
  1. Starte Claude Code, tippe /mcp, wähle cloud-sql und dann Authenticate. Ein Browserfenster öffnet sich für die Anmeldung bei Google Cloud.

Ergänze --scope user, damit er in jedem Projekt verfügbar ist, nicht nur in diesem.

Claude Desktop

  1. Öffne Customize → Connectors, klick auf + Add und dann auf Add custom connector.
  2. Nenne ihn Google Cloud SQL und füge diese URL ein:
https://sqladmin.googleapis.com/mcp
  1. Klick auf Add, dann auf Connect, und melde dich an, wenn Google Cloud danach fragt.

Die JSON-Konfigurationsdatei von Claude Desktop startet nur lokale Server. Remote-Server laufen über Connectors, und Connectors, die du auf claude.ai hinzufügst, erscheinen auch hier.

claude.ai

  1. Öffne das Connector-Formular auf claude.ai. Dieser Button füllt Name und URL für dich aus:
  1. Prüfe, dass die URL https://sqladmin.googleapis.com/mcp lautet, und klick auf Add.
  2. Klick auf Connect und melde dich an, wenn Google Cloud danach fragt.

Kostenlose Pläne erlauben einen benutzerdefinierten Connector. In Team- und Enterprise-Plänen fügt ihn ein Owner unter Organization settings → Connectors hinzu.

ChatGPT

  1. Geh auf chatgpt.com zu Plugins, wähle + und dann Add custom MCP server.
  2. Gib einen Namen für den Server ein.
  3. Füge unter Connection https://sqladmin.googleapis.com/mcp als Server-URL ein und wähle als Authentifizierung OAuth. ChatGPT schickt dich zur Anmeldung zu Google Cloud.
  4. Setz den Haken bei I understand and want to continue und wähle dann Create as a plugin.

Ob du einen eigenen MCP-Server hinzufügen kannst, hängt von deinem ChatGPT-Tarif und den Berechtigungen deines Workspace ab (in Business-Workspaces können es Admins und Owner).

Cursor

Oder trag ihn von Hand in ~/.cursor/mcp.json (alle Projekte) oder .cursor/mcp.json (dieses Projekt) ein:

mcp.json
{
  "mcpServers": {
    "cloud-sql": {
      "url": "https://sqladmin.googleapis.com/mcp"
    }
  }
}

Cursor zeigt neben dem Server Needs authentication. Klick auf die Schaltfläche daneben, um dich anzumelden.

VS Code

Oder aus einem Terminal:

code --add-mcp '{"name":"cloud-sql","type":"http","url":"https://sqladmin.googleapis.com/mcp"}'

Oder committe ihn ins Repository in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "cloud-sql": {
      "type": "http",
      "url": "https://sqladmin.googleapis.com/mcp"
    }
  }
}

VS Code bittet dich beim ersten Start des Servers um eine Anmeldung.

Devin Desktop

  1. Füge ihn zu ~/.config/devin/mcp_config.json (macOS und Linux) oder %APPDATA%\devin\mcp_config.json (Windows) hinzu:
mcp_config.json
{
  "mcpServers": {
    "cloud-sql": {
      "serverUrl": "https://sqladmin.googleapis.com/mcp"
    }
  }
}
  1. Aktualisiere die Liste der MCP-Server in Cascade und melde dich an, wenn du gefragt wirst.

Devin Desktop ist der neue Name von Windsurf. Für Remote-Server liest es serverUrl (oder url).

Codex

codex mcp add cloud-sql --url https://sqladmin.googleapis.com/mcp
codex mcp login cloud-sql

Oder bearbeite ~/.codex/config.toml direkt:

config.toml
[mcp_servers.cloud-sql]
url = "https://sqladmin.googleapis.com/mcp"

Gemini CLI

gemini mcp add --transport http cloud-sql https://sqladmin.googleapis.com/mcp

Führe dann in Gemini CLI /mcp auth cloud-sql aus, um dich anzumelden.

Damit fügst du ihn dem aktuellen Projekt hinzu. Ergänze -s user, um ihn überall zu nutzen.

Jeder Client

Die meisten Clients akzeptieren diese Form. Manche nennen das URL-Feld anders: serverUrl in Devin Desktop, httpUrl in der Einstellungsdatei von Gemini CLI.

{
  "mcpServers": {
    "cloud-sql": {
      "type": "http",
      "url": "https://sqladmin.googleapis.com/mcp"
    }
  }
}

Zed legt Server in seinen Einstellungen unter context_servers ab. Cline braucht "type": "streamableHttp", sonst nimmt es SSE an.

Dein Client startet nur lokale Server? Dann binde den Server über npx -y mcp-remote https://sqladmin.googleapis.com/mcp ein.

Einbinden

Zeig Google Cloud SQL in einem README oder auf deiner Website. Jede Einbindung verlinkt auf diese Seite, nutzt die eigene URL des Servers und setzt keine Cookies. So funktionieren Einbindungen

Karte, iframe und JSON sind auf Englisch. Häng ?lang=it, fr, de oder es an ihre Adresse an, um eine andere Sprache zu bekommen.

README-Badge

Badge-Vorschau, hellBadge-Vorschau, dunkel
Markdown
[![Google Cloud SQL on mcp.tc](https://mcp.tc/i/cloud-sql/badge.svg)](https://mcp.tc/i/cloud-sql)
HTML
<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>

Es folgt dem hellen oder dunklen Modus der Lesenden. Hänge ?theme=light oder ?theme=dark an, um ihn festzulegen, oder ?style=compact, um das Zeichen ohne Schriftzug zu zeigen.

Website-Karte

HTML
<script src="https://mcp.tc/w/cloud-sql.js" async></script>

Die Karte erscheint dort, wo das Tag steht. Füge dem Tag data-theme="dark" oder data-size="compact" hinzu, um sie zu ändern. Die Datei enthält alles, was sie braucht, stellt also keine weiteren Anfragen und setzt keine Cookies.

iframe

HTML
<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>

Nutze es auf Seiten, die keine Skripte erlauben. Hänge ?theme=light oder ?theme=dark an die Adresse an, um die Farben festzulegen.

JSON

Der Eintrag als Daten für deine eigenen Seiten und Tools: Name, Kurzbeschreibung, die eigene URL des Servers, Tools und die „Add to“-Links. Jede Website kann ihn lesen (CORS ist offen).

https://mcp.tc/i/cloud-sql.json

Was jedes Feld bedeutet

KI-Prompt

Füg ihn in einen KI-Coding-Assistenten wie Claude Code oder Cursor ein, und er baut die Karte von Google Cloud SQL in deine Website ein.

Markdown
Füge meiner Website die mcp.tc-Karte für den MCP-Server Google Cloud SQL hinzu. Es ist ein einziges statisches Skript: kein Build-Schritt, kein Paket zu installieren, keine Cookies.

Setz dieses Tag dorthin, wo die Karte erscheinen soll. Die Karte erscheint direkt davor:

```html
<script src="https://mcp.tc/w/cloud-sql.js" async></script>
```

Um sie woanders zu zeigen, setz dort diesen Platzhalter ein und lade dasselbe Skript nur einmal, zum Beispiel vor `</body>`. Lass den Link darin stehen: Besucher ohne JavaScript sehen ihn.

```html
<div data-mcptc="cloud-sql"><a href="https://mcp.tc/i/cloud-sql">Google Cloud SQL on mcp.tc</a></div>
```

Optionen:
- `data-theme="light"` oder `"dark"` am Tag oder Platzhalter legt die Farben fest. Ohne das Attribut folgt die Karte dem hellen oder dunklen Modus der Besucher.
- `data-size="compact"` ergibt eine kleinere Karte ohne Kurzbeschreibung.
- Die CSS-Variable `--mcptc-max-width` am Platzhalter oder einem Elternelement legt die Breite fest (Standard `520px`).
- `?lang=` in der Skript-URL legt die Sprache der Karte fest: `en`, `it`, `fr`, `de` oder `es`.

Wenn die Website eine Content Security Policy hat, erlaube `script-src https://mcp.tc` und `img-src data:` (das Icon ist eingebettet).

Für ein README oder andere Markdown-Dokumentation nimm stattdessen das Badge:

```markdown
[![Google Cloud SQL on mcp.tc](https://mcp.tc/i/cloud-sql/badge.svg)](https://mcp.tc/i/cloud-sql)
```

Referenz: https://mcp.tc/de/embed

Änderungsverlauf

Wir lesen die Tool-Liste dieses Servers alle 3 Stunden und halten fest, was sich ändert. Zuletzt gelesen: 18. Nov. 2026, 05:33 UTC.

Folge Google Cloud SQL, und wir schicken dir eine E-Mail, wenn sich etwas ändert.

  1. , Automatische Prüfung

    3 Tools geändert.

    Details, 4. Nov. 2026, 17:54 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

      Nachher

      Execute 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_readonlyBeschreibung
      Vorher

      Execute 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&nbsp;MB, t…

      Nachher

      Execute 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…

  2. , Automatische Prüfung

    3 Tools geändert.

    Details, 4. Nov. 2026, 02:47 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

    • execute_sql_readonlyBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, t…

  3. , Automatische Prüfung

    3 Tools geändert.

    Details, 3. Nov. 2026, 17:49 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

      Nachher

      Execute 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_readonlyBeschreibung
      Vorher

      Execute 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&nbsp;MB, t…

      Nachher

      Execute 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…

  4. , Automatische Prüfung

    3 Tools geändert.

    Details, 3. Nov. 2026, 05:42 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

    • execute_sql_readonlyBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, t…

  5. , Automatische Prüfung

    3 Tools geändert.

    Details, 2. Nov. 2026, 23:39 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

      Nachher

      Execute 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_readonlyBeschreibung
      Vorher

      Execute 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&nbsp;MB, t…

      Nachher

      Execute 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…

  6. , Automatische Prüfung

    3 Tools geändert.

    Details, 2. Nov. 2026, 08:44 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

    • execute_sql_readonlyBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, t…

  7. , Automatische Prüfung

    3 Tools geändert.

    Details, 1. Nov. 2026, 11:50 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

      Nachher

      Execute 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_readonlyBeschreibung
      Vorher

      Execute 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&nbsp;MB, t…

      Nachher

      Execute 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…

  8. , Automatische Prüfung

    3 Tools geändert.

    Details, 1. Nov. 2026, 05:42 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sqlBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, then the response will be truncated. * The `execute_sql` tool ha…

    • execute_sql_readonlyBeschreibung
      Vorher

      Execute 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…

      Nachher

      Execute 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&nbsp;MB, t…

  9. , Automatische Prüfung

    3 Tools geändert.

    Details, 31. Okt. 2026, 20:47 UTC

    Geändert 3

    • create_instanceBeschreibung
      Vorher

      Initiates 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…

      Nachher

      Initiates 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_sql execute_sql_readonly

    Ein Teil dieser Änderung wird nicht angezeigt, damit die Seite schlank bleibt.

  10. , Automatische Prüfung

    10 Tools geändert.

    Details, 24. Okt. 2026, 10:37 UTC

    Geändert 10

    clone_instance create_backup create_instance create_user get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Ein Teil dieser Änderung wird nicht angezeigt, damit die Seite schlank bleibt.

  11. , Automatische Prüfung

    10 Tools geändert.

    Details, 24. Okt. 2026, 04:41 UTC

    Geändert 10

    clone_instance create_backup create_instance create_user get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  12. , Automatische Prüfung

    10 Tools geändert.

    Details, 24. Okt. 2026, 01:38 UTC

    Geändert 10

    clone_instance create_backup create_instance create_user get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  13. , Automatische Prüfung

    10 Tools geändert.

    Details, 23. Okt. 2026, 07:39 UTC

    Geändert 10

    clone_instance create_backup create_instance create_user get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  14. , Automatische Prüfung

    10 Tools geändert.

    Details, 22. Okt. 2026, 16:43 UTC

    Geändert 10

    clone_instance create_backup create_instance create_user get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  15. , Automatische Prüfung

    13 Tools geändert.

    Details, 15. Okt. 2026, 01:30 UTC

    Geändert 13

    clone_instance create_backup create_instance create_user execute_sql execute_sql_readonly get_instance get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  16. , Automatische Prüfung

    13 Tools geändert.

    Details, 14. Okt. 2026, 22:32 UTC

    Geändert 13

    clone_instance create_backup create_instance create_user execute_sql execute_sql_readonly get_instance get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  17. , Automatische Prüfung

    13 Tools geändert.

    Details, 13. Okt. 2026, 10:33 UTC

    Geändert 13

    clone_instance create_backup create_instance create_user execute_sql execute_sql_readonly get_instance get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  18. , Automatische Prüfung

    13 Tools geändert.

    Details, 13. Okt. 2026, 04:39 UTC

    Geändert 13

    clone_instance create_backup create_instance create_user execute_sql execute_sql_readonly get_instance get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  19. , Automatische Prüfung

    13 Tools geändert.

    Details, 13. Okt. 2026, 01:37 UTC

    Geändert 13

    clone_instance create_backup create_instance create_user execute_sql execute_sql_readonly get_instance get_operation import_data postgres_upgrade_precheck restore_backup update_instance update_user

    Die neuesten 10 Änderungen zeigen alle Details, ältere nur die Namen.

  20. , Automatische Prüfung

    Beginn der Beobachtung: 15 Tools.

Häufige Fragen

Kann ich mcp.tc/i/cloud-sql in meinen MCP-Client einfügen?

Nein. mcp.tc-Links sind Seiten, keine Server-Adressen. Verbinde dich mit https://sqladmin.googleapis.com/mcp, damit dein Client direkt mit Google Cloud SQL spricht. Das Anmelde-Token funktioniert ohnehin nur dort. Der Quick-Link ist zum Teilen da: Er öffnet diese Seite, mit Einrichtungsschritten für jeden Client.

Braucht Google Cloud SQL einen API-Schlüssel oder eine Anmeldung?

Ja, du brauchst ein Konto bei Google Cloud. Wenn sich dein Client zum ersten Mal verbindet, öffnet er die Anmeldeseite von Google Cloud. Das Token geht direkt an die eigene URL des Servers, nie über mcp.tc.

Ist Google Cloud SQL ein Remote- oder ein lokaler Server?

Remote. Google Cloud hostet ihn unter https://sqladmin.googleapis.com/mcp, und er spricht Streamable HTTP. Es gibt nichts zu installieren.

Was kann Google Cloud SQL?

Er hat 15 Tools, darunter list_instances, get_instance und create_instance. Du kannst damit Cloud-SQL-Instanzen auflisten und prüfen, Instanzen erstellen, klonen und aktualisieren, und Datenbankbenutzer anlegen und aktualisieren.

Welche Clients können ihn nutzen?

Jeder Client, der Remote-MCP-Server unterstützt: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed und andere. Die Einrichtungsschritte decken jeden davon ab.

Verfolgt mcp.tc Änderungen an Google Cloud SQL?

Ja. Der Tab Verlauf von Google Cloud SQL zeigt jede Änderung, die wir an seinen Tools finden, bis hin zu Beschreibungen und Parametern, dazu neue Versionen und Änderungen seines Betreibers. Folge dem Eintrag, um eine E-Mail zu bekommen, wenn er sich ändert.

Wer hat diese Seite geschrieben?

Der Roboter von mcp.tc hat die eigenen Metadaten von Google Cloud SQL (seinen MCP-Handshake, seine Tool-Liste und öffentliche Seiten) gelesen, und ein KI-Modell hat daraus den Text entworfen. Ein Mensch prüft alles, was die Prüfungen nicht bestätigen können. Der Text kann trotzdem falsch sein; wenn dir ein Fehler auffällt, nutze Eintrag melden auf dieser Seite. Diese Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.

mcp.tc steht in keiner Verbindung zu Google Cloud. Diese Seite entstand aus den öffentlichen Metadaten von Google Cloud SQL, zuletzt geprüft am 17. Nov. 2026, und ein KI-Modell hat die Beschreibung geschrieben, sie kann also Fehler enthalten. Namen und Marken gehören ihren Inhabern. Stimmt etwas nicht? Eintrag melden. Die Übersetzung hat ein KI-Modell aus dem englischen Text erstellt.