Cloud Run MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | Lists available GCP projects |
| create_projectA | Creates a new GCP project and attempts to attach it to the first available billing account. A project ID can be optionally specified; otherwise it will be automatically generated. |
| list_servicesB | Lists Cloud Run services in a given project and region. |
| get_serviceB | Gets details for a specific Cloud Run service. |
| get_service_logB | Gets Logs and Error Messages for a specific Cloud Run service. |
| deploy_local_filesB | Deploy local files to Cloud Run. Takes an array of absolute file paths from the local filesystem that will be deployed. Use this tool if the files exists on the user local filesystem. |
| deploy_local_folderA | Deploy a local folder to Cloud Run. Takes an absolute folder path from the local filesystem that will be deployed. Use this tool if the entire folder content needs to be deployed. |
| deploy_file_contentsA | Deploy files to Cloud Run by providing their contents directly. Takes an array of file objects containing filename and content. Use this tool if the files only exist in the current chat context. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, but the three deployment tools (deploy_file_contents, deploy_local_files, deploy_local_folder) could cause confusion as they all handle deployment with subtle differences in input source. The other tools (create_project, get_service, get_service_log, list_projects, list_services) are clearly differentiated by their target resources and actions.
All tool names follow a consistent verb_noun pattern with snake_case, such as create_project, deploy_file_contents, get_service, and list_services. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 8 tools, the server is well-scoped for managing Cloud Run deployments and related GCP projects. The count is reasonable, covering core operations like deployment, service management, and project handling without being overwhelming or insufficient.
The tool set covers key workflows for Cloud Run, including deployment, service retrieval, logging, and project management. Minor gaps exist, such as missing update or delete operations for services or projects, but agents can likely work around these with the provided tools for basic deployment and monitoring tasks.