# Your Google Cloud. Read like a runbook.

Source: https://corespeed.io/integrations/gcp

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.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Google Cloud after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## 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.

You ask your agent: "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."

It calls CoreSpeed:

- `gcp__list_run_services`: ok, 488 ms
- `gcp__query_logs`: ok, 1306 ms
- `gcp__list_error_groups`: ok, 541 ms

It reads from: Google Cloud.

### Incident summary: Thirty minutes of timeouts.

Checkout failed from 01:10 to 01:40 because it could not reach orders-db. It recovered without a change.

**What happened**

- 212 requests failed with a database connection timeout.
- All came from revision checkout-00042.

**Check next**

- The orders-db Cloud SQL instance's restarts.
- The service's connection limit.

_Illustrative project · Fictional data · Nothing redeployed_

All connectors: https://corespeed.io/docs/connectors

## From logs and bills to the next step

Requests you can make once Google Cloud is connected. The data is fictional.

### Find idle spend

acme-prod · findings · Recommender, in your agent

- Idle: batch-worker-2
- Unattached: disk-old-01
- A list, not a change

### Read the logs

checkout · errors · Cloud Logging

- Window: 01:10 to 01:40
- Cause: Database connection timeouts
- No service changed

### Hold a change for a person

Stop a VM · A write waits for you

- Instance: batch-worker-2
- Policy: Ask before stopping anything
- Waiting for you

## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Which Google Cloud products does it cover?

Projects and IAM, Compute Engine, Cloud Run, GKE, Cloud Storage, Cloud SQL, Pub/Sub, Logging, Monitoring, billing and Recommender. BigQuery has a connector of its own.

### What can my agent see?

Only what your Google account can see. The connection uses your own sign-in, so your IAM roles in each project decide every call.

### Does reading logs change anything?

No. Reading is separate from writing. Starting, stopping or deleting a resource is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/gcp

## Related pages

- [AWS for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/aws): Let your agent call any AWS API with your IAM credentials. Writes and secret reads can wait for a person.
- [Cloudflare for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/cloudflare): Audit DNS, check Workers and R2, and change Cloudflare settings from your agent, with the permissions you grant.
- [MCP gateway for your agents and tools](https://corespeed.io/solutions/mcp-gateway): Reach connected apps, built-in tools, and your own remote MCP servers through one authenticated CoreSpeed MCP endpoint.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Cloud Logging query language: https://cloud.google.com/logging/docs/view/logging-query-language
- Recommender overview: https://cloud.google.com/recommender/docs/overview
- Cloud Run documentation: https://cloud.google.com/run/docs

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)