Google Cloud Run

Connect to Google’s managed Cloud Run MCP server to list and inspect services or deploy applications from container images, source archives, and inline source files.

See Google’s official Cloud Run MCP documentation for setup instructions, authentication requirements, and current capabilities.

What you’ll need to connect

Ask your Google Cloud administrator to:

1. Select or create a billing-enabled Google Cloud project and enable the Cloud Run Admin API.
2. Grant your Google identity the MCP Tool User, Cloud Run Developer, Service Account User, and Artifact Registry Reader roles, or equivalent permissions appropriate for the operations you need. Cross-project service accounts also require Service Account Token Creator.
3. Ensure your Obot administrator has configured a Google Web OAuth client for this catalog entry.

When you connect, Google asks you to authorize Obot. Tool calls use your Google identity and its IAM permissions.

See Google’s MCP authentication guide for complete authentication instructions.

Important differences

This managed server does not provide tools to list or create Google Cloud projects or retrieve service logs. It adds source archive deployment. Inline source requests are limited to 50 MiB, and source archives are limited to 250 MiB.

⚠️ Upgrade notice

If you’re upgrading this server, note that this replaces the Obot-hosted Cloud Run server with Google’s managed Cloud Run MCP server.

• Reconnect required: Connect with Google OAuth. The previous service-account credentials and default-region setting are no longer used.
• Tool changes: Tool names and parameters change. Project listing, project creation, and service-log retrieval are no longer available.
• New capability: Source-archive deployment is now available.