Regional MCP Server Configuration

Mandatory Step 0 Pre-Flight Check

[!IMPORTANT] Pre-Flight Check Before Using Dataproc / Regional Services or Falling Back to CLI: Whenever a task involves a regional Google Cloud service (e.g. Dataproc clusters, Spark batches, jobs, or sessions): 1. Check for MCP tools first: Before executing any gcloud dataproc or CLI commands, check whether the expected mcp__*__<service>__* tools (e.g. mcp__*__dataproc__*) are registered in the current environment (ToolSearch or deferred tools). 2. If tools are missing or calls fail/hang on a malformed host: Do NOT immediately fall back to gcloud/bq CLI. Inspect the live MCP configuration files (below) for unreplaced $GCP_REGION, ${REGION}, or ${user_config.GCP_REGION} placeholders. 3. If the region placeholder is already replaced with a valid region (e.g. us-central1): This skill does not apply — proceed normally with the task.