Skip to main content
Open Settings → AI & Agents → External agents to choose the client you use. Its connection acts with your AutoAdy identity’s access. An OpenAI or Claude API key configured inside AutoAdy is a different setup.

​
Choose your client

Connect Claude

Add the remote connector, sign in, and verify an account read.

Connect ChatGPT

Use the custom MCP interface available to your account and workspace.
For Codex, Claude Code, another developer client, or a custom runtime, use the current setup recipe in External agents and the developer client guide. A model name alone does not provide tool access; the client must support the connection method.

​
What every connection needs

  1. Sign in to the AutoAdy identity that should supply access. For Meta data, connect Meta and confirm the intended account.
  2. Follow that client’s recipe. Prefer OAuth account sign-in when supported. For a key-based developer client, create a named key under AutoAdy API keys and keep it in private client settings.
  3. Run Verify your first connection: ask for list_ad_accounts and inspect the actual account names, IDs, and currencies. A saved setup is not a successful read.
  4. Review permissions and approvals before allowing management tools.
A valid credential does not unlock a missing plan entitlement, account grant, or unavailable source. An empty account list calls for checking the Meta connection and team access; an authentication error calls for reconnecting OAuth or replacing a revoked/expired key.

​
Stop using a client

In Settings → AI & Agents → AutoAdy API keys, revoke its named manual key or its Connected apps OAuth row. This ends that authorization; it does not cancel billing, disconnect every provider, or revoke other clients. Credential management. Last reviewed: October 5, 2026.