GCP MCP
Related Servers
Alternatives to GCP MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityCmaintenanceEnables managing Google Cloud Platform (GCP) resources through natural language commands, including compute instances, storage, databases, and monitoring.56-
- 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-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Google Workspace services (Gmail, Calendar, Drive, Docs, Sheets, Chat, Slides, People) through natural language using Claude Desktop, Claude Code CLI, and other MCP clients.699 npm3MIT
- 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
- AlicenseAqualityCmaintenanceEnables AI agents to manage Google Cloud Platform resources including projects, IAM, service accounts, and APIs directly through GCP REST APIs without requiring gcloud CLI or Terraform.331,740 npmMIT
- 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
TDQS
Scored across 56 tools
Most tools have distinct purposes targeting specific GCP resources and actions, with clear boundaries between services like Compute Engine, Cloud Storage, IAM, and monitoring. However, some overlap exists between list_assets and other listing tools, and say_hello is an outlier that could cause confusion.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_instance, list_firewall_rules, get_bucket_details, and delete_object. The naming convention is uniform across all 56 tools, making them predictable and easy to understand.
With 56 tools, the count is excessive for a single server, making it overwhelming and difficult for agents to navigate efficiently. While GCP is broad, this many tools suggests poor scoping and could lead to confusion or performance issues in tool selection.
The toolset provides comprehensive coverage across multiple GCP services, including authentication, compute, storage, networking, IAM, and monitoring, with CRUD operations for many resources. Minor gaps exist, such as missing update operations for some resources like firewall rules or service accounts, but core workflows are well-supported.