# Claude

> Adding Advibly to Claude as a connector.

Source: https://advibly.com/docs/agents/clients/claude



Claude connects to Advibly as a **custom connector**, authorised in the browser.

<Steps>
  <Step>
    ### Open connector settings [#open-connector-settings]

    In Claude, go to **Settings → Connectors → Add custom connector**.
  </Step>

  <Step>
    ### Give it the URL [#give-it-the-url]

    ```
    https://advibly.com/mcp
    ```

    Leave everything else at its default. There is no API key field to fill in.
  </Step>

  <Step>
    ### Authorise [#authorise]

    Claude opens an Advibly sign-in. Approve it, and the connector's tools appear
    in new conversations.
  </Step>

  <Step>
    ### Verify [#verify]

    Start a new conversation, enable the connector, and ask: “List my Advibly
    brands.” Setup is complete when Claude returns the account's brands without
    asking for an API key.
  </Step>
</Steps>

## First message [#first-message]

> List my Advibly brands, then make three static ad concepts for the first one.

Claude should resolve a real `brand_id`, explain the planned billable calls,
generate three images, and collect any result that is still pending.

## Notes [#notes]

* Tool calls spend your Advibly credits. Ask for the cost first if you are
  unsure: `advibly_check_credits` shows your balance.
* For anything multi-step, ask Claude to open a project so the output is
  grouped - see [Use cases](/use-cases/ugc-video-ad).
* Claude also has [skills](/agents/skills) for whole productions, like a
  finished UGC ad or an animated explainer.
* If the connector disappears or returns `401`, remove it, add it again, and
  repeat OAuth. See [Connection failures](/agents/mcp#connection-failures).