META ADS MCP SERVER

Make sense of your Meta Ads.

Explore Facebook and Instagram campaign evidence in your AI assistant. Read account structure, inspect creative and compare performance without changing a live campaign.

Connect your assistant

What you can do

Discover your accounts

List the ad accounts your Meta login can access, then read the selected account details.

Look beneath the campaign

Inspect campaigns, ad sets, ads and creative alongside custom conversions and pixels.

Ask better reporting questions

Read Meta Insights over explicit dates. Keep reporting levels, attribution settings and currency consistent.

SETUP GUIDE

From connection to first answer.

You need an MCP client with remote HTTP and OAuth support, plus a Meta login with access to the data you want to read. Client availability can depend on your plan or administrator.

Add a remote MCP server
Open your AI client’s MCP or connector settings. Add a server named “Adlane Meta Ads” and paste the URL below. Choose Streamable HTTP if your client asks for a transport.
https://mcp.adlane.app/metaads
Sign in and review consent
Start the connection in your client and follow the browser sign-in. Review the requested access, approve if appropriate, then return to your AI client.
Meta requests ads_read. The shared Meta consent screen may display Ads CLI. Choose the business assets you intend to make available.
Check the tools
Refresh the connection if needed. You should see 9 tools, including list_ad_accounts. Ask your assistant to discover accounts before requesting a report.
Ask your first question
Start with a specific scope. Copy or adapt this prompt:
List my accessible Meta ad accounts and ask me which one to use. Read the account currency and timezone. Compare campaign Insights for the last 28 complete days with the previous 28 days. Explain spend, reach and conversion changes, including attribution limitations. Do not change anything.

Using a desktop client with local MCP configuration

If your client accepts an mcpServers JSON configuration but cannot connect to a remote OAuth server directly, the third-party mcp-remote bridge can make the connection. Install Node.js with npm first. Merge this entry into your existing configuration, restart the client and complete browser sign-in.

{
  "mcpServers": {
    "adlane-meta-ads": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.adlane.app/metaads"
      ]
    }
  }
}

The command downloads and runs mcp-remote on your computer. Native remote MCP support is preferable when your client provides it. Do not paste provider passwords or access tokens into the configuration.

Available tools

These tools read data. They cannot create campaigns, change budgets, publish ads or approve Adlane proposals.

list_ad_accountsget_ad_accountlist_campaignslist_ad_setslist_adslist_creativeslist_custom_conversionslist_pixelsget_insights

Connection troubleshooting

No accounts or data?

Meta permissions and app access determine which accounts are visible. Insights depend on attribution and reporting settings. Do not add Meta and Google attributed conversions together as unique sales.

Sign-in did not finish?

Complete consent in the same browser session. If a desktop bridge uses a local return address, allow that callback in your browser. Reconnect from the client if the sign-in expires.

Access stopped working?

Reconnect after access is revoked or a provider token expires. For Meta, expired tokens require a new sign-in. Check your provider permissions before repeatedly retrying a failed report.

Know what leaves your account.

Adlane keeps provider credentials server-side. Requested report data is returned to your chosen MCP client, which may share it with its AI provider. Review that client’s privacy settings before using sensitive reports.

Read Adlane’s privacy notice