gcp-billing-list-accountsLABSCO SUMMARY
One connection instead of eight consoles.
The value is in the chain rather than any single tool: find the error group, pull the logs around it, jump from a log entry to its trace, then check whether the fix you want to deploy has the IAM permissions to land. Billing sits in the same server, which is unusual — cost anomaly questions get answered in the same session as the incident that caused them.
What it is
An MCP server that connects to Google Cloud and exposes the observability and administration surfaces an on-call engineer reaches for: Logging, Monitoring, Trace, Error Reporting, Profiler, IAM, Spanner and Billing. Several tools accept a natural-language query instead of a filter expression.
What you get
- Log entries queried by project, severity, resource type, service and time range —
gcp-logging-query-logs,gcp-logging-query-time-range,gcp-logging-search-comprehensive - Metrics retrieved and metric types enumerated, including from a plain-language question —
gcp-monitoring-query-metrics,gcp-monitoring-list-metric-types,gcp-monitoring-query-natural-language - Distributed traces fetched, listed, and found from a log entry —
gcp-trace-get-trace,gcp-trace-list-traces,gcp-trace-find-from-logs,gcp-trace-query-natural-language - Error groups listed with detail and trend analysis —
gcp-error-reporting-list-groups,gcp-error-reporting-get-group-details,gcp-error-reporting-analyse-trends - IAM policy read, permissions tested, and deployment permission gaps analysed before you ship —
gcp-iam-get-project-policy,gcp-iam-test-project-permissions,gcp-iam-validate-deployment-permissions,gcp-iam-analyse-permission-gaps - Spanner instances, databases and tables listed, and SQL executed against them —
gcp-spanner-list-instances,gcp-spanner-list-databases,gcp-spanner-list-tables,gcp-spanner-execute-query - Billing accounts, services and SKUs read, with cost analysis, anomaly detection and recommendations —
gcp-billing-analyse-costs,gcp-billing-detect-anomalies,gcp-billing-cost-recommendations,gcp-billing-service-breakdown - CPU and heap profiles listed and compared across deployments —
gcp-profiler-list-profiles,gcp-profiler-analyse-performance,gcp-profiler-compare-trends
Requirements
Google Cloud credentials, either as a service account key file pointed at by GOOGLE_APPLICATION_CREDENTIALS or as GOOGLE_CLIENT_EMAIL and GOOGLE_PRIVATE_KEY set directly; gcloud auth application-default login produces the former. GOOGLE_CLOUD_PROJECT sets the default project, otherwise it is taken from the credentials. Install is a clone plus pnpm install and pnpm build, then launching dist/index.js with node; the package.json names it google-cloud-mcp at 0.5.0. If the server times out on startup, lazyAuth: true defers authentication until a tool is actually called.
Setup effort
Build from source — git clone https://github.com/krzko/google-cloud-mcp.git
USE CASES
01
Working an incident from symptom to cause
Start from error groups in the last hour, pull the matching logs, then follow a log entry to its distributed trace.
02
Checking a deployment will not fail on permissions
Test the specific permissions against the target project and get back the gaps before the deploy runs.
03
Explaining a jump in the cloud bill
Break the spend down by service for the period, look for anomalies, and get concrete cost recommendations back.
04
Inspecting a Spanner database you did not build
List the instances and databases, read a table's structure, then run the query you actually wanted.
38 tools
Listed in project docs. Your client may show a different list.
gcp-billing-get-account-detailsgcp-billing-list-projectsgcp-billing-get-project-infogcp-billing-list-servicesgcp-billing-list-skusgcp-billing-analyse-costsgcp-billing-detect-anomaliesgcp-billing-cost-recommendationsgcp-billing-service-breakdowngcp-error-reporting-list-groupsgcp-error-reporting-get-group-detailsgcp-error-reporting-analyse-trendsgcp-iam-get-project-policygcp-iam-test-project-permissionsgcp-iam-test-resource-permissionsgcp-iam-validate-deployment-permissionsgcp-iam-list-deployment-servicesgcp-iam-analyse-permission-gapsgcp-logging-query-logsgcp-logging-query-time-rangegcp-logging-search-comprehensivegcp-spanner-execute-querygcp-spanner-list-tablesgcp-spanner-list-instancesgcp-spanner-list-databasesgcp-spanner-query-natural-languagegcp-spanner-query-countgcp-monitoring-query-metricsgcp-monitoring-list-metric-typesgcp-monitoring-query-natural-languagegcp-profiler-list-profilesgcp-profiler-analyse-performancegcp-profiler-compare-trendsgcp-trace-get-tracegcp-trace-list-tracesgcp-trace-find-from-logsgcp-trace-query-natural-languageBEFORE YOU INSTALL
What to know first
Tools you get
38 tools named in the project's documentation.
Requires
- Node.js with pnpm, to build from a clone
- Google Cloud credentials: GOOGLE_APPLICATION_CREDENTIALS pointing at a key file, or GOOGLE_CLIENT_EMAIL and GOOGLE_PRIVATE_KEY instead
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/krzko/google-cloud-mcp.git
cd google-cloud-mcp
pnpm install
pnpm buildAuthenticate to Google Cloud:
TERMINAL
gcloud auth application-default loginMCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"google-cloud-mcp": {
"command": "node",
"args": [
"/Users/<YOUR_USERNAME>/code/google-cloud-mcp/dist/index.js"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/Users/<YOUR_USERNAME>/.config/gcloud/application_default_credentials.json"
}
}
}
}/Users/foo/code/google-cloud-mcp is the README's example clone; yours is the full path of your clone. The credentials path is the file gcloud auth application-default login wrote on your machine. That file is the key-file method the project recommends; to use GOOGLE_CLIENT_EMAIL and GOOGLE_PRIVATE_KEY instead, put those two in the env block instead of GOOGLE_APPLICATION_CREDENTIALS.
