Deploy applications to Cloud Run
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://run.googleapis.com/mcp5 tools · 851msget_serviceGet info about a Cloud Run service, such as its URI and whether the deploy succeeded.Get info about a Cloud Run service, such as its URI and whether the deploy succeeded.
No input schema was published for this tool.
list_servicesList Cloud Run services in a given Google Cloud project and region.List Cloud Run services in a given Google Cloud project and region.
No input schema was published for this tool.
deploy_service_from_imageDeploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.Deploy a container image from Artifact Registry or Docker Hub as a Cloud Run service.
No input schema was published for this tool.
deploy_service_from_archiveDeploy a Cloud Run service directly from a self-contained source code archive (.tar.gz),
skipping the container image build step for faster deployment.
The archive must include all dependencies:
- For compiled languages (Go, Java), include pre-compiled binaries.
- For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/).
Deployment steps:
1. Package source code and dependencies into a .tar.gz archive (max 250MiB).
It's recommended to create archive from the root of the application's source directory.
2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service.
3. Deploy to Cloud Run using this tool, specifying:
- source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object).
- command: Command to start the application.
- base_image_uri: Base image for the container (e.g., go124, nodejs24, python314).
See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options.
The runtime picked should match the local environment.
- args: (Optional) Arguments for the command.
- env: (Optional) Environment variables (e.g., name: `PYTHONPATH`, value: `./vendor`).
- ports: (Optional) Container ports to expose (defaults to 8080).Deploy a Cloud Run service directly from a self-contained source code archive (.tar.gz), skipping the container image build step for faster deployment. The archive must include all dependencies: - For compiled languages (Go, Java), include pre-compiled binaries. - For scripting languages (Python, Node.js), include pre-installed libraries (e.g., vendor/, node_modules/). Deployment steps: 1. Package source code and dependencies into a .tar.gz archive (max 250MiB). It's recommended to create archive from the root of the application's source directory. 2. Upload the archive to a Google Cloud Storage bucket, preferably in the same region as the service. 3. Deploy to Cloud Run using this tool, specifying: - source_code: Google Cloud Storage object path to the archive (e.g., gs://bucket/object). - command: Command to start the application. - base_image_uri: Base image for the container (e.g., go124, nodejs24, python314). See https://docs.cloud.google.com/run/docs/configuring/services/runtime-base-images for options. The runtime picked should match the local environment. - args: (Optional) Arguments for the command. - env: (Optional) Environment variables (e.g., name: `PYTHONPATH`, value: `./vendor`). - ports: (Optional) Container ports to expose (defaults to 8080).
No input schema was published for this tool.
deploy_service_from_file_contentsDeploys a Cloud Run service directly from local source files. This method is suitable for
scripting languages like Python and Node.js, of which the source code can be embedded in the
request. This is ideal for quick tests and development feedback loops. You must include all
necessary dependencies within the source files because it skips the build step for faster
deployment.
**Key Requirements:**
1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having `filename` and `content`.
2. Size limit: you are subject to total request size limit of 50MiB.Deploys a Cloud Run service directly from local source files. This method is suitable for scripting languages like Python and Node.js, of which the source code can be embedded in the request. This is ideal for quick tests and development feedback loops. You must include all necessary dependencies within the source files because it skips the build step for faster deployment. **Key Requirements:** 1. source_code: Should set to sourceCode.inlinedSource.sources with array of source files, each having `filename` and `content`. 2. Size limit: you are subject to total request size limit of 50MiB.
No input schema was published for this tool.
5 of 5 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Deploy applications to Cloud Run
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.