mcp

{
  "id": "aix_6adca733f8",
  "name": "mcp",
  "operator": "(unclaimed - source: registry-official · publisher: com.googleapis.sqladmin)",
  "description": "Create, manage, and query your Google Cloud SQL resources.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "object-storage",
    "sql-database"
  ],
  "protocols": {
    "mcp": "https://sqladmin.googleapis.com/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 602,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 66,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T20:01:29.141Z"
  },
  "pricing_model": "unknown",
  "profile": {
    "mcp_server": "StatelessServer",
    "mcp_version": "ESF",
    "tool_count": 15,
    "tools": [
      {
        "name": "list_instances",
        "description": "List all Cloud SQL instances in the project."
      },
      {
        "name": "get_instance",
        "description": "Get the details of a Cloud SQL instance."
      },
      {
        "name": "create_instance",
        "description": "Initiates the creation of a Cloud SQL instance.\n\n* The tool returns a long-running operation. Use the `get_operation` tool to poll its status\n  until the operation completes.\n* The instance creation operation can take several minutes. Use a command line tool to pause\n  for 30 seconds before rechecking the status.\n* After you use the `create_instance` tool to create an instance,\n  you can use the `create_user` tool to create an\n  IAM user account for the user currently logged in to the project.\n* IMPORTANT: Set `ipv4_enabled` to 'false' if creating a Private Service Connect\n  or a Private Servi"
      },
      {
        "name": "execute_sql",
        "description": "Execute any valid SQL statement, including data definition language (DDL),\ndata control language (DCL), data query language (DQL), or\ndata manipulation language (DML) statements, on a Cloud SQL instance.\n\nTo support the `execute_sql` tool, a Cloud SQL instance must meet\nthe following requirements:\n\n* The value of `data_api_access` must be set to `ALLOW_DATA_API`.\n* For built_in users password_secret_version must be set.\n* Otherwise, for IAM users, for a MySQL instance, the database flag\n  `cloudsql_iam_authentication` must be set to `on`.\n  For a PostgreSQL instance, the database flag `cloudsq"
      },
      {
        "name": "execute_sql_readonly",
        "description": "Execute any valid read only SQL statement on a Cloud SQL instance.\n\nTo support the `execute_sql_readonly` tool, a Cloud SQL instance must meet\nthe following requirements:\n\n* The value of `data_api_access` must be set to `ALLOW_DATA_API`.\n* For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`.\n  For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set\n  to `on`.\n* An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`)\n  is required to call the `execute_sql_readonly` tool.\n  The tool executes"
      },
      {
        "name": "get_operation",
        "description": "Get the status of a long-running operation. A long-running operation can take several\nminutes to complete. If an operation takes an extended amount of time, then use a command\nline tool to pause for 30 seconds before rechecking the status of the operation.\n"
      },
      {
        "name": "create_user",
        "description": "Create a database user for a Cloud SQL instance.\n\n* This tool returns a long-running operation. Use the `get_operation` tool to poll\n  its status until the operation completes.\n* When you use the `create_user` tool, specify the type of user:\n `CLOUD_IAM_USER`, `CLOUD_IAM_SERVICE_ACCOUNT`, or `BUILT_IN`.\n* By default the newly created user is assigned the `cloudsqlsuperuser` role, unless\n  you specify other database roles explicitly in the request.\n* You can use a newly created user with the `execute_sql` tool if the user is a\n  currently logged in IAM user. The `execute_sql` tool executes the "
      },
      {
        "name": "update_user",
        "description": "Update a database user for a Cloud SQL instance. A common use case for\nthe `update_user` is to grant a user the `cloudsqlsuperuser` role,\nwhich can provide a user with many required permissions.\n\nThis tool only supports updating users to assign database roles.\n\n* This tool returns a long-running operation. Use the `get_operation` tool to poll its status\n  until the operation completes.\n* Before calling the `update_user` tool, always check the existing configuration of the user\n  such as the user type with `list_users` tool.\n* As a special case for MySQL,  if the `list_users` tool returns a ful"
      },
      {
        "name": "clone_instance",
        "description": "Create a Cloud SQL instance as a clone of a source instance.\n\n* This tool returns a long-running operation. Use the `get_operation` tool to poll its\n  status until the operation completes.\n* The clone operation can take several minutes. Use a command line tool to pause for 30\n  seconds before rechecking the status.\n"
      },
      {
        "name": "update_instance",
        "description": "Partially updates the configuration settings of a Cloud SQL instance.\n\n* This tool returns a long-running operation. Use the `get_operation` tool to poll\n  its status until the operation completes.\n* Some update operations, such as changing the edition upgrade or instance tier, etc might\n  cause the instance to restart, resulting in downtime. Before you proceed with such\n  operations, get confirmation from the user.\n"
      },
      {
        "name": "list_users",
        "description": "List all database users for a Cloud SQL instance."
      },
      {
        "name": "create_backup",
        "description": "Takes a backup on a Cloud SQL instance. Always populate the project and instance fields on\nthe request. The location (region) and description of the backup may also be optionally\nprovided, in which case the corresponding request fields should also be populated.\n"
      },
      {
        "name": "restore_backup",
        "description": "Restores a backup to a Cloud SQL instance.\n\nThe target_instance and target_project must be provided and populated in the request.\n\nThe backup identifier can be provided in several ways:\n\n1. A backup_run_id (which is an integer).\n2. A backup URI of the format `projects/{project-id}/backups/{backup-uid}`.\n3. A backup URI of the format `projects/{project-id}/locations/{location}/backupVaults/{backupvault}/dataSources/{datasource}/backups/{backup-uid}`.\n\nUse the identifier to populate the `backup_id` field in the request.\n\nThe source_project must be populated in the request. If the identifier is a"
      },
      {
        "name": "import_data",
        "description": "Import data into a Cloud SQL instance.\n\nIf the file doesn't start with `gs://`, then the assumption is that the file is stored\nlocally. If the file is local, then the file must be uploaded to Cloud Storage\nbefore you can make the actual `import_data` call. To upload the file to Cloud Storage,\nyou can use the `gcloud` or `gsutil` commands.\n\nBefore you upload the file to Cloud Storage, consider whether you want to use an existing\nbucket or create a new bucket in the provided project.\n\nAfter the file is uploaded to Cloud Storage, the instance service account must have\nsufficient permissions to re"
      },
      {
        "name": "postgres_upgrade_precheck",
        "description": "Checks if a Cloud SQL for PostgreSQL instance is ready for a major version upgrade to the\nspecified target version.\n\nThe `target_database_version` MUST be provided in the request (e.g., `POSTGRES_15`).\n\nThis tool helps identify potential issues *before*\nattempting the actual upgrade, reducing the risk of failure or downtime.\n\nThis tool is only supported for PostgreSQL primary instances and does not run on read replicas.\n\nThe precheck typically evaluates:\n\n- Database schema compatibility with the target version.\n- Cloud SQL limitations and unsupported features.\n- Instance resource constraints ("
      }
    ],
    "profiled_at": "2026-09-24T20:01:29.141Z"
  },
  "unreachable": false
}