Skip to content
Sunday, 4 October 2026
enltpl
Tenesys AI News
Subscribe

All News

TENESYS AI NEWS tracks the most important AI news and explains what changed, why it matters and whether a technology is worth testing.

All NewsModelsAgentsVoice AIAutomationBusinessResearchCyber Security
Any timeTodayThis WeekThis Month🔴 Breaking🟠 Important🧪 Worth Testing

“Google” — 3 articles ✕

Agents· Important· 🧪 Worth Testing

Google Cloud Launches Remote MCP Server for gcloud and BigQuery CLI Access

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.

Google Cloud AI
Agents· Important· 🧪 Worth Testing

Google's Antigravity SDK Adds Local Offline Model Support with Gemma 4 26B

Google announced that its Antigravity SDK now supports running agentic workflows locally and offline, with initial support for Gemma 4 26B A4B running via Google AI Edge's LiteRT. Developers can build agents that run entirely on-device, without cloud API costs or internet dependency. Google also demonstrated a hybrid 'Architect-Builder' pattern where a cloud model (Gemini 3.8 Flash) plans tasks and a local swarm of Gemma 4 26B instances does the heavy execution, keeping source code off the cloud.

Google Developers
Agents· Important· 🧪 Worth Testing

Google Cloud API Gateway can now turn REST APIs into MCP tools

Google Cloud API Gateway now supports acting as a remote MCP server in Public Preview. By annotating an existing OpenAPI spec (x-google-api-management.mcp and x-google-mcp-tool), teams can expose their current REST operations as agent-ready MCP tools without building or hosting a separate MCP server. Existing authentication (JWT/API key), quotas, and logging continue to apply unchanged since MCP and REST traffic share one policy path.

Google Developers