Google Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PRIVATE_KEY | No | Your Google Cloud service account private key (method 2) | |
| GOOGLE_CLIENT_EMAIL | No | Your Google Cloud service account email (method 2) | |
| GOOGLE_CLOUD_PROJECT | No | Your Google Cloud project ID (optional, will attempt to determine from credentials if not set) | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to your Google Cloud service account key file (method 1) |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| gcp-logging-query-logsB | Query Google Cloud Logs with custom filters. Searches across all payload types (text, JSON, proto) and metadata fields. |
| gcp-logging-query-time-rangeA | Query Google Cloud Logs within a specific time range. Supports relative times (1h, 2d) and ISO timestamps. |
| gcp-logging-search-comprehensiveC | Search across all log fields including textPayload, jsonPayload, protoPayload, labels, HTTP requests, and metadata. Provides maximum context. |
| gcp-spanner-execute-queryD | – |
| gcp-spanner-list-tablesD | – |
| gcp-spanner-list-instancesD | – |
| gcp-spanner-list-databasesD | – |
| gcp-spanner-query-natural-languageD | – |
| gcp-spanner-query-countD | – |
| gcp-monitoring-query-metricsD | – |
| gcp-monitoring-list-metric-typesD | – |
| gcp-monitoring-query-natural-languageD | – |
| gcp-trace-get-traceD | – |
| gcp-trace-list-tracesD | – |
| gcp-trace-find-from-logsD | – |
| gcp-trace-query-natural-languageD | – |
| gcp-iam-get-project-policyB | Retrieve the IAM policy for a Google Cloud project |
| gcp-iam-test-project-permissionsA | Test which permissions the current caller has on a Google Cloud project |
| gcp-iam-test-resource-permissionsA | Test which permissions the current caller has on specific Google Cloud resources |
| gcp-iam-validate-deployment-permissionsA | Check if current caller has required permissions for deploying to common GCP services |
| gcp-iam-list-deployment-servicesB | List all GCP services with pre-defined deployment permission sets |
| gcp-iam-analyse-permission-gapsC | Compare current permissions against required permissions for specific operations and identify gaps |
| gcp-error-reporting-list-groupsD | – |
| gcp-error-reporting-get-group-detailsD | – |
| gcp-error-reporting-analyse-trendsD | – |
| gcp-profiler-list-profilesD | – |
| gcp-profiler-analyse-performanceD | – |
| gcp-profiler-compare-trendsD | – |
| gcp-billing-list-accountsA | List all Google Cloud billing accounts accessible to the user |
| gcp-billing-get-account-detailsA | Retrieve detailed information about a specific Google Cloud billing account |
| gcp-billing-list-projectsA | List all projects associated with a specific Google Cloud billing account |
| gcp-billing-get-project-infoA | Retrieve billing configuration and status for a Google Cloud project |
| gcp-billing-list-servicesB | List all available Google Cloud services for billing and cost analysis |
| gcp-billing-list-skusB | List all SKUs (Stock Keeping Units) and pricing information for a Google Cloud service |
| gcp-billing-analyse-costsC | Perform detailed cost analysis with trends and insights for Google Cloud billing data |
| gcp-billing-detect-anomaliesC | Detect unusual cost patterns and spending anomalies in Google Cloud billing data |
| gcp-billing-cost-recommendationsB | Generate cost optimisation recommendations with potential savings for Google Cloud billing |
| gcp-billing-service-breakdownC | Get detailed cost breakdown by Google Cloud service with usage and SKU information |
| gcp-utils-set-project-idB | Set the default Google Cloud project ID to use for all operations |
| gcp-utils-get-project-idA | Get the current Google Cloud project ID and recent project history |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyse-errors | Analyse errors in logs over a specified timeframe with optional severity and service filtering |
| trace-request | Trace a specific request through logs using trace ID |
| performance-overview | Get a performance overview for services over a specified timeframe |
| alert-investigation | Investigate a specific alert and analyse related metrics and logs |
| schema-explanation | Get a comprehensive overview of a Cloud Spanner database schema |
| query-optimisation | Analyse and provide optimisation suggestions for a Cloud Spanner SQL query |
| data-exploration | Analyse a Cloud Spanner table schema, performance, and data patterns |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 40 tools
Tools are separated by service prefix, but within services like logging and Spanner, multiple tools for querying logs or databases overlap in purpose. Additionally, many tools lack descriptions, increasing ambiguity.
All tools follow a consistent pattern: 'gcp-{service}-{action}-{noun}' in snake_case. For example, gcp-billing-list-accounts, gcp-iam-get-project-policy. No mixing of styles.
40 tools is high but not extreme for a multi-service server. However, several services have only 3 tools with missing descriptions, suggesting the count is inflated without full coverage.
Many services have significant gaps: error reporting, monitoring, profiler, and trace lack CRUD operations and detailed descriptions. Spanner is missing update/delete. Billing and logging are more complete, but overall surface is incomplete.