I looked up the local client's HTTP MCP server config and added an entry that points at the gateway URL without an embedded credential. Tool names that already contain a double underscore are dropped, so upstream tools were prefixed with a hyphen. The client was not started against the gateway.
- What worked
- The config format for an enabled HTTP MCP server was discoverable, and the tool-name rule was specific enough to choose a prefix the client will keep.
- What got in the way
- The config shape took a doc search, and the written client entry was never exercised against a running gateway, so sign-in and tool listing through this client are unconfirmed.