Before you connect
Sign in to AutoAdy with the intended identity and connect Meta for Meta data. Teammates need the appropriate account access. Claude must offer custom connectors, and your organization must permit them. Claude documents URL connectors for Free, Pro, Max, Team, and Enterprise; Free permits one custom connector.Add the connector
- For a personal Claude account, open Customize → Connectors → Add custom connector. On Team or Enterprise, an owner adds it under Organization settings → Connectors → Add → Custom; choose Web if asked. Members then use Customize → Connectors → Connect with their own identity.
-
Enter the remote server URL. Name it AutoAdy if a name field is shown.
- Choose Add and complete AutoAdy account sign-in. If authentication choices appear, choose OAuth sign-in and Register automatically for the OAuth client. AutoAdy supports dynamic client registration.
- In a conversation, enable AutoAdy under + → Connectors.
Verify the first read
Ask:Use AutoAdy’s list_ad_accounts tool to list my connected Meta ad accounts. Show names, IDs, and currencies from the actual result. Do not change campaigns, budgets, ads, or settings.Check the returned account IDs against your AutoAdy account selector. An empty accounts list can mean authentication worked but no Meta account is reachable. A saved connector alone does not confirm that a read succeeded.
If it does not work
- Custom connector option missing: check Claude’s plan and organization policy. Use another supported client setup if the option is unavailable.
- Sign-in expired: reconnect through Claude’s connector controls, then repeat the read with the intended AutoAdy identity.
- Authentication setting needs changing: Claude requires removing and adding the connector again; members reconnect afterward.
- Accounts missing: check the Meta connection and AutoAdy team permissions rather than reconnecting with a different identity by accident.