Regional MCP Server Configuration
Mandatory Step 0 Pre-Flight Check
[!IMPORTANT] Pre-Flight Check Before Using Composer / Dataform / Dataflow /
Regional Services or Falling Back to CLI: Whenever a task involves a
regional Google Cloud service (e.g. Cloud Composer environments, DAGs, or
Airflow tasks; Dataform repositories, workspaces, or workflow invocations;
Dataflow jobs, pipelines, or templates): 1. Check for MCP tools first:
Before executing any gcloud composer, gcloud dataform, gcloud dataflow,
or other CLI commands, check whether the expected mcp__*__<service>__* tools
(e.g. mcp__*__composer__*, mcp__*__dataform__*, mcp__*__dataflow__*) 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 ${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.
Some Google Cloud MCP servers are region-scoped (e.g. Composer:
https://composer.$GCP_REGION.rep.googleapis.com/mcp, Dataform:
https://dataform.$GCP_REGION.rep.googleapis.com/mcp, Dataflow:
https://dataflow.$GCP_REGION.rep.googleapis.com/mcp). If the Data Agent Kit
plugin has not been configured with a region, the server fails to connect
silently — it registers zero tools, with no error and no placeholder string
visible anywhere to notice. Treat a missing mcp__*__<service>__* tool as the
trigger, not just a failed call — that's the most common way this skill gets
skipped in favor of a gcloud/bq fallback.
When to use
- User asks to use a regional service (e.g. "list composer environments", "why
did my DAG fail", "list dataform repositories", "list dataflow jobs"), and
the matching
mcp__* tools aren't present — check ToolSearch or the
deferred-tools listing first — or a call to one fails/hangs on a malformed
host.
- Then inspect the live config (below) for
$GCP_REGION, ${region}, or
${REGION}. If found, run the procedure. If the region is already set, this
skill doesn't apply — investigate normally instead.
Supported services
Each regional MCP server in the config file is enabled through a service in
@skill:dak-setup:
- Cloud Composer / Airflow: MCP server
dak-composer, enabled by the
Apache Airflow service.
- Dataform: MCP server
dak-dataform, enabled by the BigQuery service.
- Dataflow: MCP server
dak-dataflow, enabled by the Dataflow service.
Locating the live config
Inspect the Data Agent Kit plugin MCP config file that is actually loaded at
runtime (read-only — hand-editing it to replace region placeholders is
PROHIBITED):
- Claude Code:
~/.claude/plugins/cache/<marketplace>/dak/<version>/.claude-plugin/mcp.json
(get <marketplace>/<version> from
~/.claude/plugins/installed_plugins.json) or ./.claude-plugin/mcp.json.
- Codex CLI:
~/.codex/plugins/cache/<marketplace>/dak/<version>/mcp.json
or ./mcp.json.
- Antigravity CLI:
~/.gemini/config/plugins/<plugin name>/mcp_config.json (run
agy plugin list for the installed plugin name) or ./mcp_config.json.
- IDE-global MCP configs (not managed by
@skill:dak-setup):
~/.gemini/config/mcp_config.json and
~/.gemini/antigravity/mcp_config.json are managed by the Data Cloud IDE
extension settings rather than @skill:dak-setup.
The plugin's saved configuration (project, region, and services) is in
~/.config/data-agent-kit/config.json.
Procedure
[!CAUTION] Manual Placeholder Edits Are PROHIBITED: You MUST NOT hand-edit
mcp.json, .claude-plugin/mcp.json, or mcp_config.json (or instruct the
user to manually edit them) to replace $GCP_REGION, ${region}, or
${REGION}. @skill:dak-setup owns the plugin configuration and overwrites
manual edits every time the agent starts.
You MUST NOT call the regional MCP tools yet — they will not be available
until configuration and restart complete.
You MUST inspect the live config file(s) above (read-only) for
dak-composer, dak-dataform, and dak-dataflow URLs containing
$GCP_REGION, ${region}, or ${REGION}:
- If all regional server URLs already contain a concrete region (e.g.
us-central1): stop using this skill and troubleshoot the task
normally.
- If the placeholder appears only in an IDE-global config
(
~/.gemini/config/mcp_config.json or
~/.gemini/antigravity/mcp_config.json): do NOT invoke
@skill:dak-setup; tell the user to set their GCP project and region in
the Data Cloud IDE extension settings.
- If
~/.config/data-agent-kit/config.json already has a non-empty
region and includes the matching service but the live plugin config
still has the placeholder: the agent has not been restarted since setup
ran. Do NOT run @skill:dak-setup again; go to step 4.
If an unreplaced placeholder is present in a live Data Agent Kit plugin
MCP config, you MUST immediately invoke and follow @skill:dak-setup to
configure the plugin:
- During
@skill:dak-setup, ensure Apache Airflow (for Composer /
dak-composer), BigQuery (for Dataform / dak-dataform), and/or
Dataflow (for Dataflow / dak-dataflow) is included in the enabled
services without dropping any previously enabled services
(@skill:dak-setup replaces the service list rather than merging it),
and verify @skill:dak-setup reports that the plugin has been
configured.
- If direct execution of
@skill:dak-setup is blocked (for example,
inside Codex CLI's default read-only sandbox), instruct the user to run
the setup skill directly:
- Claude Code or Antigravity CLI: run
/dak:dak-setup (or
/dak-setup for Antigravity Marketplace installs).
- Codex CLI: restart Codex with
codex -s danger-full-access and
run $dak:dak-setup.
You MUST tell the user that an agent restart is required after setup
completes — MCP connections load once at startup and do not hot-reload
mid-session. Restarting does not lose the conversation:
- Claude Code:
claude --resume (or --continue)
- Codex:
codex resume --last (or codex resume for a picker)
- Antigravity:
agy --continue (or agy -c)
1---2name: resolving-mcp-region-configs3description: >-4 Mandatory Step 0 pre-flight check for regional Google Cloud MCP servers (Composer dak-composer, Dataform dak-dataform, and Dataflow dak-dataflow) before using regional MCP tools or falling back to gcloud/bq CLI.5 Use whenever a task involves Cloud Composer / Managed Airflow environments, DAGs, or tasks; Dataform repositories, workspaces, compilations, or workflow invocations; or Dataflow jobs, pipelines, or templates, and the expected mcp__*__composer__*, mcp__*__dataform__*, or mcp__*__dataflow__* tools are missing (ToolSearch/deferred tools) or fail on a malformed host.6 Inspects the live Data Agent Kit plugin MCP config (mcp.json, .claude-plugin/mcp.json, mcp_config.json) across Claude Code, Codex CLI, and Antigravity CLI for unreplaced $GCP_REGION, ${region}, or ${REGION} placeholders, and delegates configuration to @skill:dak-setup instead of editing by hand.7 Do NOT use when regional MCP endpoints already have a valid region, when regional MCP tools work, or for non-regional services.8license: Apache-2.09metadata:10 source: https://skillmd.com/skills/googlecloudplatform/resolving-mcp-region-configs11 version: v912 publisher: google13---1415# Regional MCP Server Configuration1617## Mandatory Step 0 Pre-Flight Check1819> [!IMPORTANT] **Pre-Flight Check Before Using Composer / Dataform / Dataflow /20> Regional Services or Falling Back to CLI**: Whenever a task involves a21> regional Google Cloud service (e.g. Cloud Composer environments, DAGs, or22> Airflow tasks; Dataform repositories, workspaces, or workflow invocations;23> Dataflow jobs, pipelines, or templates): 1. **Check for MCP tools first**:24> Before executing any `gcloud composer`, `gcloud dataform`, `gcloud dataflow`,25> or other CLI commands, check whether the expected `mcp__*__<service>__*` tools26> (e.g. `mcp__*__composer__*`, `mcp__*__dataform__*`, `mcp__*__dataflow__*`) are27> registered in the current environment (`ToolSearch` or deferred tools). 2.28> **If tools are missing or calls fail/hang on a malformed host**: Do **NOT**29> immediately fall back to `gcloud`/`bq` CLI. Inspect the live MCP configuration30> files (below) for unreplaced `$GCP_REGION`, `${region}`, or `${REGION}`31> placeholders. 3. **If the region placeholder is already replaced with a valid32> region (e.g. `us-central1`)**: This skill does not apply — proceed normally33> with the task.3435Some Google Cloud MCP servers are region-scoped (e.g. Composer:36`https://composer.$GCP_REGION.rep.googleapis.com/mcp`, Dataform:37`https://dataform.$GCP_REGION.rep.googleapis.com/mcp`, Dataflow:38`https://dataflow.$GCP_REGION.rep.googleapis.com/mcp`). If the Data Agent Kit39plugin has not been configured with a region, the server fails to connect40**silently** — it registers zero tools, with no error and no placeholder string41visible anywhere to notice. Treat a missing `mcp__*__<service>__*` tool as the42trigger, not just a failed call — that's the most common way this skill gets43skipped in favor of a `gcloud`/`bq` fallback.4445## When to use4647- User asks to use a regional service (e.g. "list composer environments", "why48 did my DAG fail", "list dataform repositories", "list dataflow jobs"), and49 the matching `mcp__*` tools aren't present — check `ToolSearch` or the50 deferred-tools listing first — or a call to one fails/hangs on a malformed51 host.52- Then inspect the live config (below) for `$GCP_REGION`, `${region}`, or53 `${REGION}`. If found, run the procedure. If the region is already set, this54 skill doesn't apply — investigate normally instead.5556### Supported services5758Each regional MCP server in the config file is enabled through a service in59`@skill:dak-setup`:6061- **Cloud Composer / Airflow**: MCP server `dak-composer`, enabled by the62 `Apache Airflow` service.63- **Dataform**: MCP server `dak-dataform`, enabled by the `BigQuery` service.64- **Dataflow**: MCP server `dak-dataflow`, enabled by the `Dataflow` service.6566## Locating the live config6768Inspect the Data Agent Kit plugin MCP config file that is actually loaded at69runtime (read-only — hand-editing it to replace region placeholders is70**PROHIBITED**):7172- **Claude Code**:73 `~/.claude/plugins/cache/<marketplace>/dak/<version>/.claude-plugin/mcp.json`74 (get `<marketplace>`/`<version>` from75 `~/.claude/plugins/installed_plugins.json`) or `./.claude-plugin/mcp.json`.76- **Codex CLI**: `~/.codex/plugins/cache/<marketplace>/dak/<version>/mcp.json`77 or `./mcp.json`.78- **Antigravity CLI**:79 `~/.gemini/config/plugins/<plugin name>/mcp_config.json` (run80 `agy plugin list` for the installed plugin name) or `./mcp_config.json`.81- **IDE-global MCP configs (not managed by `@skill:dak-setup`)**:82 `~/.gemini/config/mcp_config.json` and83 `~/.gemini/antigravity/mcp_config.json` are managed by the Data Cloud IDE84 extension settings rather than `@skill:dak-setup`.8586The plugin's saved configuration (project, region, and services) is in87`~/.config/data-agent-kit/config.json`.8889## Procedure9091> [!CAUTION] **Manual Placeholder Edits Are PROHIBITED**: You MUST NOT hand-edit92> `mcp.json`, `.claude-plugin/mcp.json`, or `mcp_config.json` (or instruct the93> user to manually edit them) to replace `$GCP_REGION`, `${region}`, or94> `${REGION}`. `@skill:dak-setup` owns the plugin configuration and overwrites95> manual edits every time the agent starts.96971. You MUST NOT call the regional MCP tools yet — they will not be available98 until configuration and restart complete.992. You MUST inspect the live config file(s) above (read-only) for100 `dak-composer`, `dak-dataform`, and `dak-dataflow` URLs containing101 `$GCP_REGION`, `${region}`, or `${REGION}`:102 - **If all regional server URLs already contain a concrete region** (e.g.103 `us-central1`): stop using this skill and troubleshoot the task104 normally.105 - **If the placeholder appears only in an IDE-global config**106 (`~/.gemini/config/mcp_config.json` or107 `~/.gemini/antigravity/mcp_config.json`): do **NOT** invoke108 `@skill:dak-setup`; tell the user to set their GCP project and region in109 the Data Cloud IDE extension settings.110 - **If `~/.config/data-agent-kit/config.json` already has a non-empty111 `region` and includes the matching service** but the live plugin config112 still has the placeholder: the agent has not been restarted since setup113 ran. Do **NOT** run `@skill:dak-setup` again; go to step 4.1143. **If an unreplaced placeholder is present in a live Data Agent Kit plugin115 MCP config**, you MUST immediately invoke and follow `@skill:dak-setup` to116 configure the plugin:117 - During `@skill:dak-setup`, ensure `Apache Airflow` (for Composer /118 `dak-composer`), `BigQuery` (for Dataform / `dak-dataform`), and/or119 `Dataflow` (for Dataflow / `dak-dataflow`) is included in the enabled120 services without dropping any previously enabled services121 (`@skill:dak-setup` replaces the service list rather than merging it),122 and verify `@skill:dak-setup` reports that the plugin has been123 configured.124 - **If direct execution of `@skill:dak-setup` is blocked** (for example,125 inside Codex CLI's default read-only sandbox), instruct the user to run126 the setup skill directly:127 - **Claude Code or Antigravity CLI**: run `/dak:dak-setup` (or128 `/dak-setup` for Antigravity Marketplace installs).129 - **Codex CLI**: restart Codex with `codex -s danger-full-access` and130 run `$dak:dak-setup`.1314. You MUST tell the user that an agent restart is required after setup132 completes — MCP connections load once at startup and do not hot-reload133 mid-session. Restarting does **not** lose the conversation:134135 - **Claude Code**: `claude --resume` (or `--continue`)136 - **Codex**: `codex resume --last` (or `codex resume` for a picker)137 - **Antigravity**: `agy --continue` (or `agy -c`)