Facebook Ads MCP Server

What is Facebook Ads MCP Server?

An MCP server that lets you manage Facebook Ads directly from Claude AI. It handles OAuth authentication so you sign in with Facebook once, and provides tools for campaigns, ad sets, ads, analytics, audiences, and page posts.

How to use Facebook Ads MCP Server?

Install Node.js 18+, clone the repository, run npm install && npm run build, then add the server to your Claude Desktop config file. On first run a wizard walks you through creating a Facebook App; after entering the App ID and Secret a browser opens for sign-in. Use node dist/index.js login to re-authenticate or add new pages.

Key features of Facebook Ads MCP Server

• Campaign, ad set, and ad management (CRUD)
• Analytics and insights at campaign, ad set, and ad level
• Custom and lookalike audience creation
• Page post creation (text and video)
• Automatic, permanent page token management via OAuth

Use cases of Facebook Ads MCP Server

• View and manage active campaigns from natural language prompts
• Create campaigns with daily budgets and bid strategies
• Analyze ad performance over a custom date range
• Post updates to Facebook pages without leaving the chat
• Build custom or lookalike audiences for targeting

FAQ from Facebook Ads MCP Server

What are the system requirements?

Node.js 18+ and Claude Desktop are required.

How does authentication work?

On first run a wizard guides you through creating a Facebook App. Enter the App ID and App Secret, then a browser automatically opens for Facebook sign-in. No manual token collection is needed.

Are tokens refreshed automatically?

Yes — the server handles token management automatically, and page tokens are permanent after the initial OAuth flow.

What is required for lead campaigns?

Lead campaigns need promotedObject and destinationType on the ad set. For website leads use destinationType=WEBSITE with a pixel ID; for instant forms use destinationType=ON_AD with a page ID and lead form ID.

How does the Conversions API work?

The server sends server-side conversion events with automatic SHA-256 hashing of PII. It supports single and batch event sending, plus offline conversion sets from CRM data.