META ADS MCP SERVER · READ-ONLY · OAUTH

Meta Ads MCP server for Facebook and Instagram reporting.

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.

The hosted Meta Ads MCP server needs no API keys, no local process and no developer setup: paste one endpoint into your AI client, sign in with Meta, and ask.

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.

Set up the Meta Ads MCP server in Claude, Claude Code, Cursor or VS Code

Every client below supports remote HTTP MCP with OAuth. The server name is yours to choose; adlane-meta-ads is used in the examples.

Claude (web and desktop)

Open Settings, choose Connectors, then Add custom connector. Paste https://mcp.adlane.app/metaads as the remote MCP server URL and save. Click Connect on the new connector to start Meta sign-in.

Claude Code

Run the command below in your terminal, then type /mcp inside Claude Code to authenticate.

claude mcp add --transport http adlane-meta-ads https://mcp.adlane.app/metaads

Cursor

Add this entry to .cursor/mcp.json in your project or to the global MCP settings. Cursor opens the browser for OAuth the first time the server is used.

{
  "mcpServers": {
    "adlane-meta-ads": {
      "url": "https://mcp.adlane.app/metaads"
    }
  }
}

VS Code (GitHub Copilot agent mode)

Create .vscode/mcp.json with this entry, then start the server from the MCP view.

{
  "servers": {
    "adlane-meta-ads": {
      "type": "http",
      "url": "https://mcp.adlane.app/metaads"
    }
  }
}

Desktop clients without remote OAuth support

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 configuration, restart the client and complete browser sign-in. Native remote MCP support is preferable when your client provides it. Do not paste provider passwords or access tokens into any configuration.

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

Available Meta Ads MCP 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

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.

Hosted Meta Ads MCP server vs running your own

Open-source Meta Ads MCP servers on GitHub suit developers who are comfortable creating API credentials and running a local process. The hosted endpoint trades that control for a two-minute setup, read-only scope and nothing to maintain.

Consideration	Self-hosted open-source server	Adlane hosted endpoint
Setup	Register an app or developer token, create OAuth credentials, install and run locally	Paste one URL into your client and sign in with Meta
Credentials	Stored on your machine; you rotate and secure them	Tokens encrypted server-side and bound to your connection; revoke from your Meta account at any time
Works from	The computer running the process	Any client on any device, including web-based clients
Write access	Depends on the project; some expose campaign and budget mutations	None. Changes exist only as reviewed proposals inside the Adlane workspace
Cost	Free software; your time to set up and maintain	Free, with no Adlane subscription required

Both approaches read the same provider data. Choose self-hosting if you need custom tools or write access under your own controls; choose the hosted endpoint if you want Meta Ads evidence in your AI client today without touching an API console.

Meta’s official Ads AI connector vs Adlane’s Meta Ads MCP

Meta announced its own ads AI connectors on 29 April 2026, in open beta, for MCP-compatible assistants such as ChatGPT and Claude. Meta describes them as a way to create and manage campaigns and to read insights from a third-party AI tool. If you want your assistant to make changes in Ads Manager, that is the first option to evaluate.

Adlane’s endpoint is narrower on purpose. It requests only ads_read, so a prompt cannot change a budget, an audience or a live ad. When you do want a change, Adlane drafts it as a proposal that a person reviews in the workspace, and new campaigns start paused.

Consideration	Meta’s official AI connector	Adlane Meta Ads MCP
Who runs it	Meta	Adlane, an independent service
Access	Reporting and campaign management, as described by Meta	Read-only (ads_read)
Changes to live ads	Can be made from the assistant, subject to the permissions you grant	Not possible from the MCP; proposals are approved inside Adlane
Status	Open beta at launch	Live, with no Adlane subscription required; visible accounts depend on your Meta permissions
Best for	Managing campaigns directly from chat	Analysing accounts without risk of an accidental edit

Source: Digiday: Meta opens its ad ecosystem to third-party AI tools (29 April 2026). Check the provider’s current documentation before you rely on a feature list; these products change quickly.

Connection troubleshooting

No accounts or data?

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.

Meta Ads MCP server: questions, answered

Is this Meta’s official ads MCP?

No. Meta offers its own AI connectors for compatible assistants. Adlane’s Meta Ads MCP is an independent, read-only endpoint that uses the Marketing API with the ads_read permission after you sign in.

Is a Facebook Ads MCP the same as a Meta Ads MCP?

Yes. Facebook and Instagram ads are managed in Meta Ads Manager through the same Marketing API, so “Facebook Ads MCP” and “Meta Ads MCP” describe the same kind of server. This one reads Facebook and Instagram campaigns from one connection.

Can it publish ads or change spend?

No. The tools list accounts, campaigns, ad sets, ads, creatives, pixels and custom conversions, and read Insights. Any change is a separate proposal inside Adlane that a human approves.

Which Meta login should I use?

The one that already has access to the ad account in Business Manager. Page access alone does not grant advertising-report access.

Why do Meta conversions differ from my analytics or Google Ads?

Each system attributes with its own rules and windows. Keep the attribution setting visible in every report and never add Meta and Google attributed sales together as unique orders.

Can I read reach and frequency?

Yes, through Insights over explicit dates. Reach is unique within the scope you request, so ask for the whole-period figure rather than adding daily rows.

Which clients are supported?

Any client with remote HTTP MCP and OAuth: Claude, Claude Code, Cursor and VS Code are covered in the setup guide. ChatGPT needs a plan that allows custom connectors.

Does it cost anything?

The MCP endpoint has no Adlane subscription gate. Your AI client may have its own plan requirements, and Meta access depends on your permissions and app review status.

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