Ad Legends is not in the Connectors Directory
That is expected today. Add the production MCP URL manually with Add custom connector.
Add custom connector is missing
Your Claude plan, workspace policy, or role may not allow it. Free accounts are limited to one custom connector; managed workspaces require an Owner or Primary Owner.
The OAuth window does not finish
Allow the browser window, confirm cookies and pop-ups are not being blocked, sign in to the intended Ad Legends account, and choose Connect again.
Ad Legends is connected but missing from the chat
Start a new conversation, open the plus menu, choose Connectors, and turn on Ad Legends for that conversation.
The brand list is empty or incomplete
Confirm OAuth used the correct Ad Legends account and that the account has permission to the expected brands.
You connected the wrong account
Disconnect the custom connector or revoke MCP access in Ad Legends settings, then reconnect and choose the correct account.
Desktop instructions mention a local config file
Those instructions are for local MCP servers or Desktop extensions. Ad Legends is a remote account-based connector and uses Claude Connectors settings.
Ad Legends is not visible inside Claude Design
The Design beta and workspace controls can differ. Use the connected server from standard Claude chat, Cowork, or Claude Code alongside the Design project, and follow the companion workflow on this page.