gcp-mcp
Related Servers
Alternatives to gcp-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables managing Google Cloud Platform infrastructure through natural language, including VM deployment, SSH key management, remote command execution, and Terraform infrastructure-as-code operations.2-
- AlicenseCqualityDmaintenanceEnables AI assistants to interact with Google Cloud Platform resources through natural language queries. Supports querying and managing GCP services like Compute Engine, Cloud Storage, BigQuery, and more across multiple projects and regions.91,740 npmMIT
- FlicenseBqualityDmaintenanceEnables managing Google Cloud Platform resources through natural language commands in Claude Desktop, supporting comprehensive operations across compute, storage, databases, networking, monitoring, and IAM without manual credential setup.5620-
- AlicenseCqualityDmaintenanceEnables interaction with Google Cloud services including billing cost analysis, log querying, and metrics monitoring through natural language commands. Provides comprehensive tools for managing GCP resources, analyzing costs, detecting anomalies, and retrieving operational insights.401Apache 2.0
- AlicenseCqualityDmaintenanceProvides tools and context for interacting with Google Cloud services, enabling natural language management of billing, monitoring, logging, IAM, Spanner, and more.5678 npmApache 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
Scored across 56 tools
Most tools target distinct GCP resources and include the resource type in the name (e.g., list_compute_instances, list_storage_buckets). However, several configuration and auth tools (config_set_project, set_quota_project, auth_login, auth_list) overlap in purpose and could confuse an agent, and get_instance_details vs get_sql_instance_details may be ambiguous without careful attention.
The majority of tools use a consistent verb_noun snake_case pattern (list_*, get_*, create_*, delete_*). But there are notable exceptions like config_set_project, auth_login, auth_list, set_quota_project, and say_hello that break the pattern, mixing noun_verb and generic verbs.
56 tools is excessive for a coherent MCP server. Even though GCP is broad, many tools are repetitive list/get operations across services, making the set feel bloated and hard to navigate. This count pushes beyond the reasonable range for maintainability and agent usability.
The server is heavily read-focused and lacks full lifecycle coverage for many resources. There are no update/delete tools for buckets, service accounts, GKE clusters, SQL instances, firewall rules, alert policies, and many other resources, and no create operations for several listed services. This leaves obvious dead ends for common management workflows.