combined-agent-setuplisted

# Connect an agent to Combined Help the user connect their chosen agent to the Combined account they intend to use. Prefer the current client-specific configuration generated by Combined's Set up or Access workspace. This skill supplies connection procedure; it does not grant access to the user's data. ## Establish the connection path Combined's public remote MCP endpoint is: ```text https://platform.trycombined.com/mcp?account_id=ACCOUNT_UUID ``` Replace `ACCOUNT_UUID` with the account the user selected. It fixes tenant scope and is not an authentication secret. Do not infer an account from unrelated browser sessions or choose another account to bypass a failure. The service uses Streamable HTTP. For a client supporting OAuth, configure the account-specific URL and begin connection from that client. A `401` challenge during discovery can be expected: `WWW-Authenticate` advertises the resource metadata used to find the authorization server. Let the user complete sign-in and review the requested grant. For unattended runtimes, use the separately provisioned agent credential as a secret environment variable. The client must support the actual header and environment-expansion syntax used. Do not paste provider API keys or a Combined bearer token into prompts, public config, URLs, or committed files. ## Configure only the selected client Read the current documentation for that client or use its generated Combined configuration. Client config formats differ; do not call a