How to connect Meta Ads MCP to ChatGPT

Updated November 14, 2026

Short answer: To connect Meta Ads MCP to ChatGPT, use Meta's official endpoint, https://mcp.facebook.com/ads, and ChatGPT's documented custom MCP setup. Meta explicitly documents ChatGPT with OAuth and a Meta developer app ID. OpenAI's current Plugins flow does not require Developer Mode first. Plan, workspace permissions and Meta authorization still determine which accounts and actions you can use.

Confirm the current ChatGPT setup route

OpenAI's custom MCP guide now describes adding a server as a plugin. Its Help Center article says the current Plugins experience does not require turning on Developer Mode first. Instructions copied from an older developer-mode tutorial may therefore use different menus.

The help article also keeps the older custom-app configuration. Use the route that matches your interface; the steps below follow these official sources.

Which plans have documented access

The following distinctions come from OpenAI's current Help Center article:

Being able to use ChatGPT does not establish permission to add a custom server. In an organization, confirm that your role can create the connection or ask the workspace administrator to configure it. Decide whether you need reporting or live edits before choosing a plan.

Prepare Meta authorization

Meta's get-started page documents this developer-app route:

1. Create or reuse an app in Meta's developer dashboard.
2. Add Create & manage ads with ads MCP server.
3. Configure the client redirect URL in Facebook Login for Business.
4. In ChatGPT, choose OAuth, enter https://mcp.facebook.com/ads and set your Meta app ID as OAuth Client ID under Advanced OAuth Settings.
5. Complete Meta's login dialog with your Facebook or Meta Managed Account and approve permissions.

Keep credentials in the provider's authentication screens.

For the callback, OpenAI's MCP authentication guidance says to copy the exact redirect URI from the server's management page into the authorization server's allowlist. Use that value for this connection.

Owning a Meta developer app is not a prerequisite: Meta points people without one to its ads AI connectors setup.

Add the server in the current Plugins interface

Follow OpenAI's Add custom MCP server instructions:

1. In ChatGPT on the web, go to Plugins.
2. Select the plus button, then Add custom MCP server.
3. Enter a name and optional description. Under Connection, enter the Meta server URL: https://mcp.facebook.com/ads.
4. Configure OAuth using Meta's requirements above.
5. Review the warning and select I understand and want to continue.
6. Select Create as a plugin and review the discovered tools.
7. Install the resulting plugin before using it. In the prompt box, type @ and select the installed plugin.

Check both sides of the configuration if authorization fails. The endpoint, Meta app settings and ChatGPT workspace permissions all matter. A successful tool-discovery screen should be followed by a reporting test, not an immediate budget change.

If you have the legacy Apps interface

OpenAI's retained custom-app instructions document Workspace settings → Apps → Create for admins/owners, or Settings → Apps → Create for authorized users. Supply the endpoint and metadata, choose authentication, select Scan Tools, finish OAuth and then select Create.

Use those controls only if your interface offers them. They are a separate documented configuration route; mixing its final buttons with the Plugins steps can make a setup guide impossible to follow. In the current Plugins experience, a missing old Developer Mode toggle is not itself a reason to stop.

Test reading before allowing writes

Meta's overview describes reporting and ad-management tools among its capabilities. The categories do not establish that every tool will be available to every user or account. Inspect what the authenticated connection actually exposes.

Start with a narrow request: “List the ad accounts available through this connection. Make no changes.” Then choose one account and ask for a completed reporting period with account and campaign IDs, spend, result type, results, currency and time zone.

Compare the answer with Ads Manager using the same account, period and result definition. Investigate missing accounts before expanding the request. Keep unlike currencies separate and ask the assistant to identify unavailable fields instead of filling gaps with estimates.

For writes, approval behavior needs separate attention. OpenAI's plugin testing guide calls for checking authentication, annotations and confirmation behavior. OpenAI's agent safety guidance recommends keeping MCP approvals enabled. Neither statement proves that this Meta connection will ask before every possible write under every configuration.

Before using live edits, inspect the allowed tools and require a specific proposal: object IDs, current values, proposed values and scope. Do not grant broad spending authority just to test whether authentication works. Run that check in your own account before relying on live edits.

Third-party connectors and the Claude route

As of November 2026, Pipeboard's guide and Madgicx's MCP documentation list ChatGPT among supported clients. They are separate provider connections with their own authentication and commercial terms. A vendor's client listing does not override OpenAI's plan or workspace permissions.

Multitool Ads is documented for Claude only. Follow connect Facebook ads to Claude for its setup. It covers analysis across Meta accounts, creatives, comments and Business Manager access, plus a preview and your approval before any ad change; ChatGPT is not a documented client for it.

If you want to inspect that underlying account workspace, the Multitool ADS live demo opens with demo data and needs no account. Connecting an assistant is a separate authorized-account workflow.

Sources: Meta Ads MCP get started and overview; Meta ads AI connectors setup; OpenAI custom MCP server guide, MCP authentication, current plan and workspace help, plugin testing and agent safety guidance; Pipeboard setup and Madgicx MCP docs, as of November 2026; Multitool's Claude connector guide.