IntegrationsGoogle Cloud integration
Your Google Cloud.Read like a runbook.
Connect Google Cloud to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads projects, Compute Engine, Cloud Run, Cloud Storage, Cloud SQL, logs, metrics and billing, and lists the Recommender's cost findings. It signs in with your own Google account, so IAM decides what it sees, and each change is a separate call.
From logs and billsto the next step.
Requests you can make once Google Cloud is connected. The data is fictional.
- Google Cloudacme-prod · recommendations
- VMbatch-worker-2 idle for 14 daysIdle
- Diskdisk-old-01 attached to nothingUnused
- VMapi-pool larger than it needsResize
Find idle spend
A list, not a change
- Google CloudCloud Logging
checkout · severity ERROR
- 212 errors between 01:10 and 01:40.
- Every one: connection to orders-db timed out.
- Revision checkout-00042 served them all.
Read the logs
No service changed
Approval requestWaiting
Codex for you
gcp__stop_instance
“Stop batch-worker-2 in us-central1-a”
Policy: Ask before stopping or deleting anything in acme-prod.
ApproveDeny
Hold a change for a person
Waiting for you
See what broke.Know why before you touch it.
Your agent finds the service, reads its error logs, and drafts what happened, without a redeploy.
Reads fromGoogle Cloud
All connectors →Find out why the checkout service on Cloud Run returned errors last night. Read the logs and draft what happened. Do not redeploy or change anything.
gcp__list_run_servicesok
checkout · us-central1 · revision 00042
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect Google Cloud
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor