Setup & Connect

Q: The connector was added but no tools appear. What now?

Two usual causes. The address may be missing the /mcp path, in which case re-adding it with the full URL fixes it. Otherwise the connector exists but is not switched on for the current chat, and enabling it in that chat's tools menu is enough. Neither case requires signing in again.

Opus Growth is a hosted remote MCP server. There is nothing to install, no API key and no developer token: you add one address to your assistant and sign in once. The video walks through it, and the written steps for each app are below.

What you need

An assistant that supports MCP connectors: Claude, ChatGPT, Claude Code, Cursor, VS Code, Windsurf, Codex or Gemini CLI.
Access to the ad account you want to manage. You authorize with your own account, so you never hand us a password.
No card. Your Opus Growth account is created the first time you sign in and starts with 75 AI-assisted actions that do not expire.

Connection address

This single address is the whole product. Paste it when your assistant asks for a custom connector or an MCP server URL:

https://mcp.opus-growth.com/mcp

Note the /mcp at the end. Leaving it off is the most common reason a connector appears to be added but exposes no tools.

Claude (web and desktop)

Open Settings, then Connectors, then Add custom connector.
Give it a name such as Opus Growth and paste the address above.
Save. The connector appears in the list, and you enable it for a chat from the tools menu.
Ask for something real, for example to list your ad accounts. On the first tool call Claude opens a browser window for sign-in.

ChatGPT

Open Settings, then Connectors, and add a custom connector. On some plans this sits behind developer mode.
Paste the same address and save.
Enable the connector in the chat where you want to use it, then ask it to list your accounts. Sign-in happens once, in the browser.

The video tab above shows the current ChatGPT screens, which move around more often than Claude's.

Terminal and code editors

Claude Code. Add the server, then authorize from inside a session:

claude mcp add --transport http opus-growth https://mcp.opus-growth.com/mcp

The default scope registers it for the current project. Use -s user to make it available in every project on your machine, or -s project to write a .mcp.json your team can commit. Then start Claude Code, type /mcp, pick opus-growth and choose Authenticate. On a remote box with no browser, open the printed authorization URL on your laptop instead; the callback completes the same way.

Cursor, VS Code, Windsurf, Codex. Same connector, different file. Cursor reads ~/.cursor/mcp.json, VS Code reads .vscode/mcp.json, Windsurf reads ~/.codeium/windsurf/mcp_config.json, and Codex uses ~/.codex/config.toml with an [mcp_servers.opus-growth] section holding the same URL. In Cursor, use agent mode: MCP tools are called by the agent, not by a plain editor question.

Confirming it works

Ask your assistant to list your ad accounts. If the account names come back, the connector is live. If it answers from general knowledge instead, the connector is not enabled for that chat. Connecting an account and checking your balance cost nothing, so this check is free.

Troubleshooting

The connector was added but no tools appear. What now?

Two usual causes. The address may be missing the /mcp path, in which case re-adding it with the full URL fixes it. Otherwise the connector exists but is not switched on for the current chat, and enabling it in that chat's tools menu is enough. Neither case requires signing in again.

Do I have to reconnect in every new chat?

No. Authorization belongs to your Opus Growth account, not to a conversation, so once you have signed in, new chats pick the connection up. What is per-chat is only whether the connector is switched on.

Can I use the same account from more than one app?

Yes, and that is the point of a hosted server. The ad accounts you authorize in Claude are the same ones you see in ChatGPT, Cursor, Claude Code or Codex; only the way you add the connector differs. You connect each ad platform once, from whichever app you like.

Do I need to write code or run a server?

No. There is nothing to install and nothing to host: no API key, no Google Ads developer token and no local process. The address above points at our server, and everything runs there.

Is a credit card required to start?

No. An account is created on first sign-in with 75 AI-assisted actions that never expire, and no payment method is asked for. Reading reports from the customer panel is free.

Which ad platforms do I connect after setup?

Setup only adds the connector. Each platform is then a separate one-time sign-in that you trigger by asking for it, and every platform has its own page in this documentation with the permissions it requests and what can go wrong.