Google Cloud Run
MCP ServerFree** - Official MCP Server to deploy to [Google Cloud Run](https://cloud.google.com/run).
Capabilities8 decomposed
mcp-standardized cloud run deployment tool exposure
Medium confidenceExposes Google Cloud Run deployment operations as callable MCP tools through a centralized tool registry (tools.js) that coordinates with specialized deployment modules. The system implements the Model Context Protocol specification to enable AI agents and assistants to invoke deployment operations via a standardized interface, with tools dynamically registered based on operational mode (local vs. remote) determined by gcp-metadata.js environment detection.
Implements dual-mode tool registration (local vs. remote) with environment-aware security boundaries through gcp-metadata.js detection, rather than static tool sets. Tools are registered conditionally based on deployment context, enabling the same MCP server to operate securely in both local development and Cloud Run production environments.
Provides MCP-native tool exposure for Cloud Run operations, enabling direct integration with MCP clients like Claude Desktop and Cline, whereas direct GCP SDK usage requires custom wrapper code in each client application.
file-content-based application deployment to cloud run
Medium confidenceDeploys containerized applications to Cloud Run by accepting application source code as file contents (not file paths), orchestrating a multi-step pipeline through cloud-run-deploy.js that coordinates Cloud Build for container compilation, Artifact Registry for image storage, and Cloud Run service creation. This approach enables deployment without requiring local filesystem access, supporting both inline code submission and remote deployment scenarios.
Accepts application code as inline file contents rather than filesystem paths, enabling deployment from generated or in-memory code without requiring local file I/O. The deployment pipeline (cloud-run-deploy.js) orchestrates Cloud Build, Artifact Registry, and Cloud Run APIs in sequence, abstracting the multi-service coordination required for containerized deployment.
Enables code-to-deployment in a single MCP tool call without intermediate file writes, whereas gcloud CLI requires local Dockerfile and manual build/push/deploy steps. Faster for AI-driven workflows that generate code in-memory.
local filesystem-based batch deployment
Medium confidenceDeploys applications from local filesystem sources through two specialized tools (deploy-local-files and deploy-local-folder) that read source code directly from disk and submit to the Cloud Run deployment pipeline. These tools are local-mode-only and integrate with cloud-run-deploy.js to handle file discovery, validation, and submission to Cloud Build, enabling developers to deploy existing local projects without manual file content extraction.
Provides two separate tools for file-level (deploy-local-files) and directory-level (deploy-local-folder) deployment, with automatic file discovery and aggregation before submission to the deployment pipeline. This dual-tool approach allows granular control over what gets deployed while maintaining simplicity for directory-based workflows.
Eliminates manual file content extraction required by deploy-file-contents tool, enabling one-command deployment of existing projects. More convenient than gcloud CLI for AI agent workflows that need to deploy local projects discovered at runtime.
cloud run service enumeration and metadata retrieval
Medium confidenceLists and retrieves detailed metadata about deployed Cloud Run services through cloud-run-services.js, providing two complementary tools: list-services returns all services in a project with summary information, while get-service retrieves detailed configuration for a specific service including environment variables, resource allocation, and traffic routing. Both tools query the @google-cloud/run SDK and are available in both local and remote modes.
Provides both list and detail operations through separate tools, allowing AI agents to first discover services (list-services) and then retrieve detailed configuration for specific services (get-service) without requiring multiple API calls or filtering logic. Integrates directly with @google-cloud/run SDK for authoritative service state.
Exposes service metadata as callable MCP tools, enabling AI agents to inspect deployments without learning gcloud CLI syntax. More efficient than shell command execution for programmatic service discovery and configuration inspection.
gcp project enumeration and creation
Medium confidenceManages GCP project lifecycle through two local-mode-only tools (list-projects and create-project) that integrate with gcp-projects.js and the @google-cloud/resource-manager SDK. list-projects enumerates all projects accessible to the authenticated user, while create-project provisions new GCP projects with automatic billing account association and API enablement through @google-cloud/service-usage. These tools enable AI agents to discover or provision projects without manual GCP console interaction.
Implements local-mode-only restriction for project creation via gcp-metadata.js environment detection, preventing remote Cloud Run instances from provisioning new projects (security boundary). Automatically associates billing accounts and enables required APIs during project creation, abstracting multi-step GCP setup into a single tool call.
Enables programmatic project provisioning without gcloud CLI or GCP console access, allowing AI agents to create isolated environments for deployments. Automatic API enablement reduces setup friction compared to manual gcloud commands.
dual-mode operational context detection and tool availability management
Medium confidenceAutomatically detects deployment context (local development vs. Cloud Run production) through gcp-metadata.js by querying GCP metadata service, and conditionally registers tools based on detected mode. Local mode enables all tools including project management and filesystem access; remote mode (when running on Cloud Run) restricts to deployment and service query tools only. This pattern implements security boundaries without requiring manual configuration, enabling the same MCP server binary to operate safely in both contexts.
Implements automatic context detection via GCP metadata service queries rather than explicit configuration, enabling zero-config deployment of the same MCP server to both local and Cloud Run environments with appropriate security boundaries. The gcp-metadata.js module encapsulates detection logic, allowing tools.js to conditionally register capabilities without hardcoded environment checks.
Eliminates need for separate local and remote server builds or configuration files. Provides automatic security enforcement (project tools disabled in remote mode) without requiring manual policy configuration, reducing misconfiguration risk compared to environment variable-based mode selection.
multi-service gcp sdk orchestration for deployment pipeline
Medium confidenceCoordinates multiple Google Cloud service SDKs (@google-cloud/cloudbuild, @google-cloud/storage, @google-cloud/artifact-registry, @google-cloud/run) through cloud-run-deploy.js to implement a complete deployment pipeline: submits source code to Cloud Build for container compilation, stores build artifacts in Artifact Registry, and creates/updates Cloud Run services. The orchestration handles sequencing, error propagation, and result aggregation across services, abstracting the complexity of multi-service coordination from MCP tool callers.
Encapsulates multi-service orchestration logic in cloud-run-deploy.js, allowing MCP tools to invoke deployment as a single operation without exposing Cloud Build, Artifact Registry, or Cloud Run APIs separately. The module handles service sequencing, credential passing, and result aggregation, reducing complexity for MCP tool implementations.
Provides unified deployment pipeline through single MCP tool call, whereas manual gcloud commands require separate build, push, and deploy steps. Abstracts service coordination details, making deployment accessible to AI agents without GCP service knowledge.
express-based http transport for remote mcp server operation
Medium confidenceImplements HTTP server transport for MCP protocol using Express.js, enabling the MCP server to run on Cloud Run and accept remote MCP client connections over HTTP. The mcp-server.js entry point conditionally initializes Express server when running in remote mode (detected via gcp-metadata.js), exposing MCP protocol endpoints for tool invocation and resource access. This transport mechanism enables multi-user access to a single MCP server instance running on Cloud Run.
Conditionally initializes Express HTTP server only in remote mode (Cloud Run environment), determined by gcp-metadata.js detection. This dual-transport approach (stdio for local, HTTP for remote) enables the same mcp-server.js entry point to serve both local development and remote production scenarios without code branching.
Enables remote MCP server deployment without separate HTTP wrapper code. Provides HTTP transport natively through Express, whereas alternative approaches might require additional reverse proxy or API gateway configuration.
Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.
Related Artifactssharing capabilities
Artifacts that share capabilities with Google Cloud Run, ranked by overlap. Discovered automatically through the match graph.
mcp.run
** - A hosted registry and control plane to install & run secure + portable MCP Servers.
ModelFetch
** (TypeScript) - Runtime-agnostic SDK to create and deploy MCP servers anywhere TypeScript/JavaScript runs
@mcp-use/cli
The mcp-use CLI is a tool for building and deploying MCP servers with support for ChatGPT Apps, Code Mode, OAuth, Notifications, Sampling, Observability and more.
arcade-mcp
The best way to create, deploy, and share MCP Servers
@anthropic-ai/mcpb
Tools for building MCP Bundles
ToolHive
Find the right MCP server for your task and deploy with one...
Best For
- ✓AI-powered development tools and IDEs integrating with GCP
- ✓Teams building AI agents that need infrastructure deployment capabilities
- ✓Organizations standardizing on MCP for cloud operations
- ✓AI agents generating code and immediately deploying it
- ✓Remote deployment scenarios where local filesystem is unavailable
- ✓Containerized application deployment with automated build orchestration
- ✓Local development environments with existing project structures
- ✓Teams migrating existing applications to Cloud Run
Known Limitations
- ⚠Tool availability is mode-dependent — local mode has full access, remote mode restricts project creation and listing for security
- ⚠Requires MCP client implementation to consume exposed tools
- ⚠No built-in tool result caching — each invocation calls GCP APIs directly
- ⚠Requires Dockerfile or buildpack configuration to be included in file contents
- ⚠Cloud Build compilation adds 2-5 minute latency per deployment
- ⚠No incremental builds — each deployment triggers full container rebuild
Requirements
Input / Output
UnfragileRank
UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.
About
** - Official MCP Server to deploy to [Google Cloud Run](https://cloud.google.com/run).
Categories
Alternatives to Google Cloud Run
Are you the builder of Google Cloud Run?
Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.
Get the weekly brief
New tools, rising stars, and what's actually worth your time. No spam.
Data Sources
Looking for something else?
Search →