Sazabi
MCP connectors

Google Cloud (GCP)

Give the Sazabi agent tools to query Cloud Logging, Cloud Monitoring, BigQuery, and other Google Cloud products using a Google OAuth 2.0 Bearer access token.

About

This is an MCP connector that gives the Sazabi agent tools from Google Cloud's first-party remote MCP servers, hosted per product at https://SERVICE.googleapis.com/mcp. Sazabi defaults to Cloud Logging (https://logging.googleapis.com/mcp), but the server URL is editable so you can point it at other per-product endpoints such as Cloud Monitoring or BigQuery. These servers authenticate with a Google OAuth 2.0 Bearer access token; Sazabi stores the token securely and sends it in the Authorization header. Access is scoped by Google IAM.

What the agent can do:

  • Query Cloud Logging for logs and log-based signals
  • Read Cloud Monitoring metrics and time series
  • Run BigQuery queries and inspect datasets
  • Point at other supported per-product Google Cloud MCP endpoints

Prerequisites

  • A Google Cloud project with the target product APIs enabled
  • A Google OAuth 2.0 access token scoped by IAM to the resources Sazabi should read (tokens are short-lived and must be refreshed on expiry)

Set up in the dashboard

Configure connectors in the dashboard under Settings > MCP connectors.

Open the connector

Find Google Cloud (GCP) in Settings > MCP connectors.

Provide the server URL and token

Sazabi needs two values:

  1. Server URL — Sazabi defaults to Cloud Logging (https://logging.googleapis.com/mcp). To use a different product, change the server URL to its endpoint, such as https://monitoring.googleapis.com/mcp (Cloud Monitoring) or https://bigquery.googleapis.com/mcp (BigQuery). See the supported products list.

  2. Google OAuth 2.0 access token — Install the gcloud CLI, configure Application Default Credentials (user credentials, a service-account key, or impersonation), then run gcloud auth application-default print-access-token and copy the token. Sazabi adds the Bearer prefix and sends it in the Authorization header.

Google access tokens are short-lived. When the token expires, create a new one and update the connector.

Set up with the CLI

Google Cloud authenticates with a Google OAuth 2.0 access token, and sazabi mcp-connectors connect only supports OAuth providers — so set up this connector in the dashboard first (above). Once it's connected, the Sazabi CLI can inspect and manage it (installed and authenticated — see sazabi mcp-connectors reference):

sazabi mcp-connectors list
sazabi mcp-connectors details <connection-id>

Find the connection ID with sazabi mcp-connectors list. To rotate the stored credentials later, use sazabi mcp-connectors update-credentials <connection-id>.

Verify

Open the connector's connection page under Settings > MCP connectors and confirm Sazabi lists the tools it discovered. Then, in a thread, ask the agent to query logs or metrics and confirm it returns results. If no tools appear, confirm the access token is current and scoped by IAM to the target product.

Troubleshooting

No tools discovered — Confirm the access token has not expired (Google tokens are short-lived) and has IAM permissions for the target product. Check that the server URL matches the product endpoint you want.

Connection shows needs attention — The access token has likely expired; generate a new token and reconnect from Settings > MCP connectors.

Further reading

Agent tools

How the agent uses connector tools.

MCP connectors

Browse the connector catalog.

On this page

AboutPrerequisitesSet up in the dashboardOpen the connectorProvide the server URL and tokenSet up with the CLIVerifyTroubleshootingFurther reading