GCP MCP
Server 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 |
|---|---|
| run-gcp-codeD | Run GCP code |
| list-projectsA | List all GCP projects accessible with current credentials |
| select-projectB | Selects GCP project to use for subsequent interactions |
| get-billing-infoC | Get billing information for the current project |
| get-cost-forecastB | Get cost forecast for the current project |
| get-billing-budgetC | Get billing budgets for the current project |
| list-gke-clustersB | List all GKE clusters in the current project |
| list-sql-instancesB | List all Cloud SQL instances in the current project |
| get-logsB | Get Cloud Logging entries for the current project |
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 9 tools
Tools are mostly distinct: billing-related tools (budget, info, forecast) are clearly separate, and list/select tools for different resources are unambiguous. The only potential confusion is 'run-gcp-code' which is vague but still distinct from other tools.
All tool names follow a consistent verb-noun pattern with hyphens (e.g., get-billing-budget, list-gke-clusters, select-project). The naming convention is uniform and predictable.
The server has 9 tools, which is an appropriate size for a focused GCP management server. It covers several key areas without being overwhelming.
The tool surface is limited to reading and listing operations for select GCP services (billing, logs, GKE, SQL, projects). Missing CRUD operations for resources, compute, storage, IAM, and other common GCP tasks. The vague 'run-gcp-code' tool does not compensate for these gaps.