LabscoMCP early access ↗
googleapisMCP SERVER · OFFICIAL PROJECT

Google Cloud MCP

Run gcloud from the conversation, plus purpose-built servers for Cloud Logging and Monitoring, Cloud Storage and Backup and DR.

by googleapis ↗Cloud Resources & Infrastructure as Code✓ Official

LABSCO SUMMARY

One server hands an agent the whole CLI; the other three hand it typed tools. Choose deliberately.

run_gcloud_command is enormously capable and inherits your account's permissions wholesale, which is why the impersonation advice in Google's own documentation matters more here than in most places — plus a config file where you list the command groups you will allow. The observability, storage and backup servers are the opposite shape: named operations with real parameters, which is what you want when an agent is going to run them unattended.

What it is

Google's repository of Cloud MCP servers. The gcloud server executes gcloud CLI commands under your own account, and three focused servers cover observability, storage and backup with typed tools instead of shell commands.

What you get

  • Any gcloud command executed from natural language, minus a fixed denylist of commands that make no sense for an agent — run_gcloud_command
  • Cloud Logging read properly: log entries, log names, buckets, views, sinks and scopes — list_log_entries, list_log_names, list_buckets, list_views, list_sinks, list_log_scopes
  • Cloud Monitoring and error reporting: metric descriptors, time series for a metric, alert policies, and error group statistics — list_metric_descriptors, list_time_series, list_alert_policies, list_group_stats
  • Traces searched and fetched by id — list_traces, get_trace
  • Cloud Storage objects listed, read as content or metadata, written, uploaded, downloaded, copied, moved and deleted — list_objects, read_object_content, read_object_metadata, write_object, upload_object, download_object, copy_object, move_object, delete_object
  • Bucket administration including creation, deletion, labels, location, IAM policy inspection and permission checks — create_bucket, get_bucket_metadata, update_bucket_labels, view_iam_policy, check_iam_permissions
  • Storage Insights queried through BigQuery, when the insights service is enabled — get_metadata_table_schema, execute_insights_query, list_insights_configs
  • Backup and DR end to end: vaults, plans, plan associations, data sources and backups read and created, protectable resources discovered, long-running operations tracked, and restores driven for Compute Engine and Cloud SQL — list_backup_vaults, create_backup_plan, create_backup_plan_association, find_protectable_resources, restore_backup, csql_restore
  • An allowlist or denylist of gcloud command groups supplied as a JSON config file, on top of the built-in denylist that is always enforced

Requirements

Node.js 20 or newer and the gcloud CLI installed and authenticated. Permissions are exactly the active gcloud account's permissions — to narrow them, authorize as a service account through impersonation and give that account a limited role. The gcloud server always enforces a built-in denylist covering commands that run arbitrary input or open interactive sessions, and you can add your own allow or deny list with an absolute path passed as -c or --config. Each server is a separate npm package: gcloud-mcp, observability-mcp, storage-mcp and backupdr-mcp.

Setup effort

One command — npx @google-cloud/gcloud-mcp init --agent=gemini-cli

See installation options