Connect your ad accounts to ChatGPT with an MCP plugin

Connect an account source, then choose the conversation

A prompt alone does not give ChatGPT access to Ads Manager. The connection has two parts: an advertising platform authorizes Adport to access selected accounts, and a ChatGPT plugin authorizes access to an Adport project. A successful sign-in on one side does not prove that the other side is ready.

Your advertising platform remains the source for campaign delivery, permissions, and ad spend. ChatGPT receives account data through the tools you authorize and can use the returned rows to answer follow-up questions. Start with an explicit account and reporting period so the next question has a stable context.

Use ChatGPT on the web and a workspace that allows custom MCP plugins. Workspace policies can limit installation or tool access. OpenAI documents the current plugin setup, authentication, and workspace restrictions.

Prepare one Adport project for the connection

1. Create or select the project for the intended brand or client.
2. Connect an advertising platform using the account that has access to its ad accounts.
3. Save the specific ad accounts you want this project to expose.
4. Enable agent access for those accounts.
5. Open AI assistants and choose the ChatGPT setup.

Keep client projects separate. An agency login may discover more accounts than a single client connection should use. Record one known account ID and its currency so you can check the first result against the platform dashboard. A project name helps people navigate; the account ID establishes which advertiser a report actually describes.

Add the hosted MCP server in ChatGPT

Open Plugins, choose +, then Add custom MCP server. Name it Adport, paste this server URL, and choose OAuth.

https://app.adport.dev/mcp

Create the plugin, sign in to Adport, and install it. In a new chat, type @ and select Adport before asking your first question.

The server address is a connection endpoint, not a credential to paste into an ordinary chat message. Review the Adport project during OAuth authorization. Complete the installation before expecting the plugin to appear in a conversation. Creating a plugin and selecting it for a chat are separate steps.

Follow the custom MCP setup for your workspace. A public directory listing is not required for this connection path. If the custom-server controls are unavailable, check workspace access rather than looking for an unpublished Adport listing.

Select Adport and verify one account

Confirm that ChatGPT called Adport and returned the advertiser you expected. General advertising advice, a web-search result, or a remembered account name is not evidence of a live connection. Expand the tool details when you need to inspect the request or response.

Next, request a short report for one explicit account and completed date range. A populated report is useful evidence; an empty result needs a date and access check before you conclude that the account has no activity.

Use the next guide for the platform you manage

Continue with Google Ads, Meta and Facebook Ads, TikTok Ads, Snapchat Ads, LinkedIn Ads, or Microsoft and Bing Ads. Each guide gives a reporting question, an interpretation checklist, and troubleshooting for that provider.

Do not compare unlike conversion definitions just because the reports share a column name. Keep currencies separate, label unavailable metrics, and ask which accounts or rows were omitted. The integration directory covers additional platforms and their supported operations.

Troubleshoot the layer that failed

• No Adport option in chat: check installation and the selected ChatGPT workspace.
• Plugin selected but no useful tool call: name Adport explicitly and request account inventory before a broad analysis.
• Sign-in succeeds but accounts are missing: check the authorized Adport project, saved account selection, and agent-access switches.
• Authorization expired: reconnect through OAuth rather than posting tokens or passwords in the conversation.
• Tools changed: refresh the plugin's tools in its settings before retrying.

ChatGPT uses the hosted connection described here. Running a local stdio command in a terminal is not the same installation. If your question is about a self-hosted deployment, first establish how that server is reachable and authorized from the ChatGPT client.

Keep analysis and approval as separate decisions

After a report identifies a useful action, request a preview for an exact account, campaign, and new value. Review the account identity, currency, budget effect, and any policy adjustments. ChatGPT's confirmation interface and Adport's pending-operation checks serve different parts of the process.

Apply only the preview you reviewed, then read back the platform state. A changed request needs a new preview. Role, plan, protected-account settings, and provider permissions still determine whether the action can run. For a shared client workflow, start with the read-only access guide.