Connect Dgate MCP or install the CLI

This is a bootstrap Skill with two access paths. Its job is to connect the managed Dgate MCP service or install dgate with the matching managed dgate-cli Skill/Rule bundle. Do not duplicate business-operation guidance here: after setup, use the connected MCP tool descriptions or the installed local dgate-cli skills. Read references/ram-policies.md for the required RAM-permission declaration.

Select the access path

1. If dedicated Dgate MCP tools are already connected, do not install anything. Verify the connection as described below and use those tools.
2. For a cloud, sandbox, or other managed Agent where installing a binary is inconvenient, prefer the managed Streamable HTTP MCP service.
3. For a local Agent IDE or a user who explicitly requests the dgate command, use the CLI path.
4. If the user chooses a path, honor it. Never install the CLI merely because MCP is available, or replace a requested CLI installation with MCP.

Managed MCP path

1. Detect the current Agent host and its MCP configuration surface. Preserve every existing MCP server and unrelated setting.
2. Obtain the target Region and a Region-matched Agent Data Gateway AccessToken from the console. Treat the AccessToken as a secret: never ask the user to paste it into chat, print it, or place it in source, logs, URLs, screenshots, or artifacts. Have the user enter it through the host's encrypted secret or header configuration.
3. Configure a Streamable HTTP server named dgate. Replace only the placeholders below: