How to connect your ad accounts to ChatGPT
Add Get MCP Ads to ChatGPT with one URL and OAuth: an Ads cockpit in the sidebar, a panel beside conversations, settings, mentions and automations.
The same URL in every client. Sign in once when ChatGPT asks; nothing is installed and no key is issued.
Both readings are on this page.
For you
What the answer looks like, and what to type to get it.
ChatGPT speaks the Model Context Protocol, so there is nothing to install. You paste one URL, sign in once, and your advertising accounts become tools it can call.
SetupLink to this section
- Open Settings, then Security and login, and turn on Developer mode.
- Go to chatgpt.com/plugins and select the plus button.
- Name it Get MCP Ads, and enter the MCP server URL below as the connection, with OAuth.
- Paste
https:/, create the connection, then approve the sign-in page./ mcp. getmcpads. com/ mcp - Review the tools ChatGPT discovered, then start a new conversation.
What you get in ChatGPTLink to this section
- Ads cockpit in the sidebar. Every client workspace and ad account, the alerts that fired, your automations, launches and Sheets exports, full screen. Open an account to load its KPIs and campaigns.
- Ads panel beside the conversation. One account's KPIs, campaigns and creatives stay visible while you chat. Tick campaigns or creatives and ask why they are dropping: ChatGPT already knows which ones you mean.
- Automations. Ask ChatGPT to watch an alert and what to do when it fires, for example pause the ad set whose CPA passed your target and explain why. Alerts are checked every hour.
- Settings. Your default client, reporting period and KPI focus live on the plugin page and apply whenever a request names no client or dates.
- Mentions and pickers. Type @ in the ChatGPT desktop app to point at an account, a campaign, an alert or a launch. Ambiguous requests open a visual account picker, and launches can start from creatives you pick in your ad library.
Before it can answer anythingLink to this section
Connecting the client is one half. The other is connecting at least one advertising platform in the dashboard and ticking which accounts to expose. Both need you, not the assistant: one is a consent screen at Google or Meta, the other is a decision about which accounts a machine may read.
For your agent
The tool sequence, the parameters that matter, and what will be refused.
Both readings as Markdown: /guides/setup/chatgpt.md
Setting up ChatGPT against this gateway. The endpoint is https:/, and each source also has its own endpoint if a narrower tool list is wanted.
What the client does on its ownLink to this section
- It requests
https:/and receives a 401 with a/ mcp. getmcpads. com/ mcp WWW-Authenticateheader. - It reads the protected resource metadata named in that header.
- It registers itself through dynamic client registration. No key is issued or pasted.
- It opens the authorisation page with PKCE and waits for the person to approve.
- It calls
tools/listand receives the tools for the connected sources, plus four routing tools.
Checking it workedLink to this section
Call list_accounts. It answers without touching any advertising API, so it separates a connection problem from an account problem. An empty list means the platform is connected but nothing was ticked.