{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"awesome-google-cloud-run","slug":"google-cloud-run","name":"Google Cloud Run","type":"mcp","url":"https://github.com/GoogleCloudPlatform/cloud-run-mcp","page_url":"https://unfragile.ai/google-cloud-run","categories":["mcp-servers","deployment-infra"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"awesome-google-cloud-run__cap_0","uri":"capability://tool.use.integration.mcp.standardized.cloud.run.deployment.tool.exposure","name":"mcp-standardized cloud run deployment tool exposure","description":"Exposes 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.","intents":["Enable AI agents to deploy applications to Cloud Run without direct GCP SDK knowledge","Expose Cloud Run operations as callable functions in MCP-compatible clients","Provide a standardized interface for deployment automation across different AI platforms"],"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"],"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":["Node.js LTS runtime","Google Cloud SDK installed and authenticated","Application Default Credentials (ADC) configured via gcloud auth application-default login","@modelcontextprotocol/sdk package"],"input_types":["tool invocation parameters (JSON)","deployment configuration objects"],"output_types":["deployment status (JSON)","service metadata (JSON)","operation results with error details"],"categories":["tool-use-integration","mcp-protocol"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_1","uri":"capability://automation.workflow.file.content.based.application.deployment.to.cloud.run","name":"file-content-based application deployment to cloud run","description":"Deploys 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.","intents":["Deploy applications to Cloud Run directly from code content without filesystem dependencies","Enable AI agents to build and deploy applications in a single operation","Support deployment workflows where source code is generated or modified in-memory"],"best_for":["AI agents generating code and immediately deploying it","Remote deployment scenarios where local filesystem is unavailable","Containerized application deployment with automated build orchestration"],"limitations":["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","Limited to single-container deployments; multi-service orchestration requires separate tool calls"],"requires":["Google Cloud project with Cloud Run API enabled","Cloud Build API enabled in target project","Artifact Registry API enabled for image storage","Service account with roles: roles/run.admin, roles/cloudbuild.builds.editor, roles/artifactregistry.writer","Valid Dockerfile or buildpack configuration in submitted files"],"input_types":["application source code (string)","Dockerfile (string)","deployment configuration (JSON with service name, region, memory, CPU)"],"output_types":["deployment operation status (JSON)","Cloud Run service URL (string)","container image URI (string)","build logs (text)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_2","uri":"capability://automation.workflow.local.filesystem.based.batch.deployment","name":"local filesystem-based batch deployment","description":"Deploys 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.","intents":["Deploy existing local projects to Cloud Run without manual file preparation","Batch-deploy entire project directories with automatic file discovery","Support traditional development workflows where code exists on local filesystem"],"best_for":["Local development environments with existing project structures","Teams migrating existing applications to Cloud Run","Developers using local IDEs and wanting direct deployment integration"],"limitations":["Local-mode-only — unavailable in remote Cloud Run deployment of the MCP server itself","Requires local filesystem access — cannot be used from remote clients","File discovery may be slow for large directories (>10,000 files)","No built-in .gitignore respect — may include unnecessary files in deployment"],"requires":["Local filesystem access to project directory","Node.js LTS runtime on local machine","Google Cloud authentication configured locally","Valid project structure with Dockerfile or buildpack configuration"],"input_types":["local file path (string)","local directory path (string)","deployment configuration (JSON)"],"output_types":["deployment operation status (JSON)","Cloud Run service URL (string)","file count and size summary (JSON)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_3","uri":"capability://search.retrieval.cloud.run.service.enumeration.and.metadata.retrieval","name":"cloud run service enumeration and metadata retrieval","description":"Lists 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.","intents":["Discover deployed services in a Cloud Run project","Retrieve current configuration and status of specific services","Enable AI agents to make deployment decisions based on existing service state"],"best_for":["AI agents that need to inspect existing deployments before making changes","Deployment automation that requires conditional logic based on service state","Monitoring and observability integrations with Cloud Run"],"limitations":["Returns only service metadata — does not include execution logs or metrics","List operation returns all services; no built-in filtering or pagination","Metadata is point-in-time snapshot; does not reflect real-time traffic or performance","Does not include revision-level details; only current active service configuration"],"requires":["Google Cloud project with Cloud Run API enabled","Service account with roles/run.viewer role minimum","Valid GCP project ID"],"input_types":["project ID (string) — implicit from authentication context","service name (string) — required for get-service only"],"output_types":["service list with summary (JSON array)","detailed service configuration (JSON object)","environment variables (JSON)","resource allocation (CPU, memory, concurrency limits)"],"categories":["search-retrieval","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_4","uri":"capability://automation.workflow.gcp.project.enumeration.and.creation","name":"gcp project enumeration and creation","description":"Manages 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.","intents":["Discover available GCP projects for deployment target selection","Automatically provision new GCP projects for isolated application deployments","Enable AI agents to manage project lifecycle as part of deployment workflows"],"best_for":["AI agents managing multi-project deployments","Automated infrastructure provisioning workflows","Teams with project-per-environment or project-per-customer patterns"],"limitations":["Local-mode-only — unavailable when MCP server runs on Cloud Run","Project creation requires billing account association — fails if no billing account available","No built-in project quota management — may hit organization limits","Project deletion not supported — requires manual cleanup via GCP console","API enablement happens asynchronously; immediate deployment may fail if APIs not yet active"],"requires":["Local mode operation (gcp-metadata.js detects Cloud Run environment and disables these tools)","Google Cloud authentication with project creation permissions","Billing account linked to organization","@google-cloud/resource-manager SDK","@google-cloud/billing SDK","@google-cloud/service-usage SDK"],"input_types":["project ID (string) — for list-projects, implicit from auth context","project name (string) — for create-project","billing account ID (string) — optional for create-project, auto-detected if not provided"],"output_types":["project list with metadata (JSON array)","newly created project ID (string)","project creation status (JSON with operation details)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_5","uri":"capability://automation.workflow.dual.mode.operational.context.detection.and.tool.availability.management","name":"dual-mode operational context detection and tool availability management","description":"Automatically 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.","intents":["Automatically adapt tool availability based on deployment environment","Enforce security boundaries between local development and production deployment","Enable single-binary deployment of MCP server to both local and Cloud Run environments"],"best_for":["Organizations deploying MCP servers to Cloud Run for multi-user access","Development teams using local MCP servers during development","Security-conscious teams requiring environment-based capability restrictions"],"limitations":["Mode detection relies on GCP metadata service availability — may fail in non-GCP environments","No explicit mode override — detection is automatic and cannot be manually overridden","Tool availability changes are not user-visible until tool invocation attempt","Remote mode restrictions are coarse-grained (all project tools disabled) — no fine-grained per-tool policies"],"requires":["gcp-metadata.js module with metadata service detection logic","GCP metadata service accessible (automatic in Cloud Run, requires emulation in local testing)","tools.js tool registration system that respects mode flags"],"input_types":["environment context (implicit from GCP metadata service)"],"output_types":["operational mode determination (local or remote)","tool registry with mode-filtered tools (JSON)"],"categories":["automation-workflow","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_6","uri":"capability://automation.workflow.multi.service.gcp.sdk.orchestration.for.deployment.pipeline","name":"multi-service gcp sdk orchestration for deployment pipeline","description":"Coordinates 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.","intents":["Execute end-to-end deployment from source code to running Cloud Run service","Coordinate container build, image storage, and service deployment in correct sequence","Provide unified error handling and status reporting across multiple GCP services"],"best_for":["Deployment automation requiring multi-service coordination","Teams wanting to abstract GCP service complexity from deployment tools","AI agents that need single-call deployment without intermediate state management"],"limitations":["Pipeline is sequential — cannot parallelize build and service creation steps","No built-in rollback — failed deployments require manual service revision management","Error in any step fails entire pipeline; no partial deployment recovery","Build logs are not streamed — only available after build completion","No caching of build artifacts between deployments — each build is independent"],"requires":["Cloud Build API enabled","Artifact Registry API enabled","Cloud Run API enabled","Service account with permissions across all three services","@google-cloud/cloudbuild, @google-cloud/artifact-registry, @google-cloud/run SDKs"],"input_types":["source code (string or file path)","Dockerfile or buildpack configuration","deployment parameters (service name, region, resource allocation)"],"output_types":["build operation ID (string)","container image URI (string)","Cloud Run service URL (string)","deployment status with timing information (JSON)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"awesome-google-cloud-run__cap_7","uri":"capability://tool.use.integration.express.based.http.transport.for.remote.mcp.server.operation","name":"express-based http transport for remote mcp server operation","description":"Implements 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.","intents":["Enable remote clients to access MCP tools via HTTP without local server installation","Support multi-user access to a centralized MCP server running on Cloud Run","Provide HTTP-based MCP transport for clients that cannot run local servers"],"best_for":["Teams deploying shared MCP servers for multi-user access","Organizations wanting centralized deployment infrastructure","Remote development environments where local server installation is impractical"],"limitations":["HTTP transport adds network latency compared to local stdio transport","Requires authentication/authorization layer (not built-in) for multi-user security","No built-in request rate limiting — vulnerable to resource exhaustion","Express server overhead adds ~50-100ms per request compared to stdio transport","Requires Cloud Run service to remain running (costs money) unlike local stdio servers"],"requires":["Express.js package","@modelcontextprotocol/sdk with HTTP transport support","Cloud Run deployment with appropriate service account permissions","HTTP client capable of MCP protocol communication"],"input_types":["HTTP requests with MCP protocol payloads (JSON)"],"output_types":["HTTP responses with MCP protocol results (JSON)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":27,"verified":false,"data_access_risk":"high","permissions":["Node.js LTS runtime","Google Cloud SDK installed and authenticated","Application Default Credentials (ADC) configured via gcloud auth application-default login","@modelcontextprotocol/sdk package","Google Cloud project with Cloud Run API enabled","Cloud Build API enabled in target project","Artifact Registry API enabled for image storage","Service account with roles: roles/run.admin, roles/cloudbuild.builds.editor, roles/artifactregistry.writer","Valid Dockerfile or buildpack configuration in submitted files","Local filesystem access to project directory"],"failure_modes":["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","Limited to single-container deployments; multi-service orchestration requires separate tool calls","Local-mode-only — unavailable in remote Cloud Run deployment of the MCP server itself","Requires local filesystem access — cannot be used from remote clients","File discovery may be slow for large directories (>10,000 files)","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.26,"ecosystem":0.49999999999999994,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:03.040Z","last_scraped_at":"2026-05-03T14:00:15.503Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=google-cloud-run","compare_url":"https://unfragile.ai/compare?artifact=google-cloud-run"}},"signature":"45gllTFrrXfzBqHTvE7qaZfpc0VxsHTwiWGcyRg04i+bHiuk8x+j0KRPMIwp6nEMmxyeMsC3SAplsAt8dLMcBw==","signedAt":"2026-06-22T02:28:05.395Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/google-cloud-run","artifact":"https://unfragile.ai/google-cloud-run","verify":"https://unfragile.ai/api/v1/verify?slug=google-cloud-run","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}