Google Cloud Launches Remote MCP Server for gcloud and BigQuery CLI Access
In short: Google Cloud introduced, in public preview, a remote MCP server that exposes the gcloud and bq command-line tools to AI agents via two tools: run_gcloud_command and run_bq_command. The server runs in an isolated, network-restricted sandbox on Google Cloud infrastructure, removing the need for agents to install or maintain local CLI binaries. It uses Agent Identity, OAuth 2.0, and IAM for authentication, integrates with Model Armor to screen for prompt injection, and supports Cloud Audit Logging for full visibility into tool calls.
This summary was generated automatically by AI from Google Cloud AI's publication. It is our own text, not a copy of the original — facts, figures and quotes belong to the source, linked above and below.
What changed?
- 1New Google Cloud CLI remote MCP server available in public preview
- 2Exposes run_gcloud_command and run_bq_command tools covering hundreds of gcloud/bq operations
- 3Runs in an isolated, network-restricted execution sandbox with no ambient credentials
- 4Authentication via Agent Identity, OAuth 2.0, and IAM; policy enforcement per caller identity
- 5Integrates with Model Armor for prompt injection/malicious input screening
- 6Supports Cloud Audit Logging of tool invocations without exposing sensitive payloads or PII
- 7No additional charge for the MCP server itself; users pay only for GCP resources and data transfer used
Why it matters
This lowers the barrier for building agents that can manage cloud infrastructure and BigQuery workflows through natural language, standardizing tool calling to CLI operations instead of custom API orchestration, with built-in enterprise security and governance.
What it means for AI agents and contact centers
While not voice-specific, this MCP server is relevant if your company's agents need to trigger cloud operations (e.g., logging, data pipeline management, BigQuery analytics for call data) as part of tool calling workflows; worth testing MCP compatibility, latency of tool execution, and audit logging for compliance in contact-center automation setups.
🧪 Worth Testing
If your company already builds agents with tool/function calling and MCP integration, testing this remote MCP server could reveal how easily cloud/BigQuery operations (e.g., call analytics storage, scheduled queries) can be integrated into voice agent workflows without managing local CLI dependencies, and how its security model (IAM, audit logs, Model Armor) fits enterprise requirements.
Sources
- Google Cloud AIOfficialPrimary sourceOriginal article →„Empower your agents with the Google Cloud CLI remote MCP server“30 Sept 2026, 19:00
- Published by source
- 30 Sept 2026, 19:00
- Found by our system
- 2 Oct 2026, 19:51
- Summary generated
- 2 Oct 2026, 19:56
This article was written by AI from the original source. Facts, numbers and prices come from the source; missing values are marked “Not specified”. Legal notice, copyright and privacy