A
licenseA
qualityC
maintenanceEnables MCP-compatible AI agents to deploy applications to Google Cloud Run by providing tools for deploying code, listing services, and managing Google Cloud projects.
8
2,055 npm
631
Apache 2.0
cloud-run
by rajath-raman
Related Servers
Alternatives to cloud-run
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables management of GCP resources and integration with AI development tools via a stateless MCP server hosted on Cloud Run.14 npmMIT
- AlicenseBqualityNot gradedmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Artifact Registry, BigQuery, Cloud Build, Compute Engine, Cloud Run, Cloud Storage, and monitoring services through a standardized MCP interface.1MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Compute Engine, Cloud Run, Storage, BigQuery, and other GCP services through a standardized MCP interface.16MIT
- AlicenseNot gradedqualityBmaintenanceGrok plugin for deploying and managing Google Cloud Run services via MCP tools, slash commands, and a skill.Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Cloud Platform services through gcloud CLI commands via a Cloud Run deployed MCP server. Supports executing gcloud commands and managing GCP resources through natural language.MIT
TDQS
A3.7/5.0
Scored across 8 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: listing vs creating projects, listing vs getting services, fetching logs, and three deployment methods differentiated by file source (local files, folder, or content). The deployment tools include explicit 'use this tool if' guidance to remove any ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: list_projects, create_project, list_services, get_service, get_service_log, deploy_local_files, deploy_local_folder, deploy_file_contents. The pattern is uniform and predictable.
Tool Count5/5
8 tools is well-scoped for a Cloud Run management server, covering project, service, log, and deployment operations without unnecessary redundancy. Each tool serves a distinct purpose within a reasonable count.
Completeness3/5
The tool set covers project listing/creation, service listing/detail/logs, and multiple deployment modes, but lacks operations for updating or deleting services, managing revisions, or handling traffic splits. These are notable gaps for a full Cloud Run lifecycle, though core workflows are handled.
Maintenance
ActivityInactive
ResponsivenessNo issues