Connect Meta and Facebook Ads to Claude

One Meta ad account for Facebook and Instagram

Facebook Ads and Instagram ads managed through Meta use the Meta advertising integration. You do not need a second Adport provider called Facebook, and signing in to a personal Instagram account is not the setup for advertising reports.

Choose the business and ad account that own the campaigns. If you manage multiple clients, create a separate Adport project for each client and save only the intended accounts. A business identity can see more assets than you want an individual agent connection to use. Check the saved account IDs before starting a report.

Set up Meta access, then add Claude Code

For hosted use, connect Meta in your Adport project, save the selected ad accounts, and enable agent access. Use the Claude Code instructions under AI assistants:

claude mcp add --transport http --scope user adport https://app.adport.dev/mcp

Run /mcp in Claude Code and complete the Adport sign-in. Ask Claude to list Meta accounts and match the intended account to Ads Manager. Claude Code documents the HTTP MCP setup and sign-in flow.

For local use, the Meta integration guide explains the Business app, system user, asset assignment, and token permissions. The read/write surface uses ads_read and ads_management. Access to another business's assets may require additional provider approval. Installing Adport does not grant that approval.

npm install -g adport
adport connect meta
adport doctor
adport accounts --provider meta

claude mcp add --transport stdio adport -- adport mcp

Ask Claude for a bounded Insights review

Start with campaigns sharing a relevant objective. A purchase campaign, a lead campaign, and an awareness campaign do not have interchangeable results. Ask Claude to show the source metrics behind its conclusion and identify any missing conversion value before discussing return on ad spend.

Use the same account and reporting period when comparing the answer with Ads Manager. If a breakdown is unavailable in the connected tool, ask for the supported report instead of accepting a table filled with inferred placement or audience values.

Find out whether the budget belongs to a campaign or ad set

Before requesting a change, inspect the existing campaign and its ad sets. Meta can place the controlling budget at different levels. Ask Claude to identify the budget owner, whether it is a daily or lifetime amount, and which entities would be affected.

A request to increase an individual ad set's budget needs a different review from increasing a campaign budget that distributes delivery across ad sets. Give the exact account and entity IDs. Ask for the current value and proposed value in the account's currency; do not infer a currency from the language of your chat.

Turn one finding into a preview

Check the preview against the entity you reviewed. Applying requires its matching pending operation and identical arguments. An expired preview or a different amount requires a new preview. After an approved change, fetch the entity again and verify the budget that Meta accepted.

Campaign creation in Adport is paused by policy. Creating a campaign does not automatically supply a complete ad set, creative, destination, and tracking setup. Inspect those separately before considering activation.

If Meta accounts or results are missing

Check Meta asset assignment and token permissions, then the Adport project's saved accounts and agent-access settings. Reporting access and permission to manage campaigns are different checks. A successful OAuth screen alone is not evidence that every requested operation is permitted.

The Meta Ads MCP page lists the connector's operations and prerequisites. Meta maintains the Marketing API documentation. For Google campaigns alongside Meta, use the Google Ads and Claude guide and preserve each platform's attribution definitions in cross-platform reports.