Model Context Protocol server for Google Cloud services
Model Context Protocol server for Google Cloud services. The google cloud mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
A Model Context Protocol server that connects to Google Cloud services to provide context and tools for interacting with your Google Cloud resources.
Everything the assistant can do here goes through one of these:
Billing — Manage and analyse Google Cloud billing with cost optimisation insights:Logging — The Logging tool exposed by this serverSpanner — The Spanner tool exposed by this serverMonitoring — The Monitoring tool exposed by this serverProfiler — The Profiler tool exposed by this serverTrace — The Trace tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 2 environment variables: GOOGLE_APPLICATION_CREDENTIALS, GOOGLE_PRIVATE_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of cloud and infrastructure servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Google Cloud MCP's toolset — Billing, Logging, Spanner and 3 more — is a fair guide to whether it matches your workflow. It is maintained by krzko; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Billing | Manage and analyse Google Cloud billing with cost optimisation insights: |
| Logging | The Logging tool exposed by this server. |
| Spanner | The Spanner tool exposed by this server. |
| Monitoring | The Monitoring tool exposed by this server. |
| Profiler | The Profiler tool exposed by this server. |
| Trace | The Trace tool exposed by this server. |
{
"mcpServers": {
"google-cloud-mcp": {
"command": "node",
"args": [
"/Users/foo/code/google-cloud-mcp/dist/index.js"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "/Users/foo/.config/gcloud/application_default_credentials.json"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GOOGLE_APPLICATION_CREDENTIALS | Configuration value read at startup. | Optional |
| GOOGLE_PRIVATE_KEY | Credential the server authenticates with. | Yes |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.