> For the complete documentation index, see [llms.txt](https://docs.mechcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mechcloud.io/cloud-computing/cost-explorer/gcp.md).

# GCP

This page documents the GCP-specific setup and supported resources for Cost Explorer (Gantt).

### Step 1: Add Your GCP Account

Cost Explorer (Gantt) requires your GCP account to be added to MechCloud. Follow the GCP onboarding guide to connect your account:

[Add GCP Account](/cloud-computing/add-an-account/gcp.md)

### Step 2: Configure Permissions

The service account used by Workload Identity Federation must have the following IAM roles on the project:

* **Compute Viewer** (`roles/compute.viewer`) — to read Compute Engine instances and disks
* **Cloud Asset Viewer** (`roles/cloudasset.viewer`) — to list and search project resources

### Step 3: Create a Resource Context

A Resource Context defines the logical boundary within which Stateless IaC and related visualizations operate. Follow the Resource Context setup guide:

[Resource Context](/cloud-computing/stateless-iac/resource-context.md)

### Step 4: Provision Infrastructure Using Stateless IaC

Once the GCP account and Resource Context are configured, infrastructure can be provisioned using Stateless IaC.

Follow the Stateless IaC authoring guide:

[Stateless IaC for GCP](/cloud-computing/stateless-iac/gcp.md)

### Supported Resources

See the [Supported Resources](/cloud-computing/cost-explorer/gcp/supported-resources.md) page for the complete list of GCP resource types supported by Cost Explorer.

### Demo

Coming soon.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mechcloud.io/cloud-computing/cost-explorer/gcp.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.