Meta Ads MCP

A Model Context Protocol (MCP) server for interacting with Meta Ads. Analyze, manage and optimize Meta advertising campaigns through an AI interface. Use an LLM to retrieve performance data, visualize ad creatives, and provide strategic insights for your ads on Facebook, Instagram, and other Meta platforms.

DISCLAIMER: This is an unofficial third-party tool and is not associated with, endorsed by, or affiliated with Meta in any way. This project is maintained independently and uses Meta's public APIs according to their terms of service. Meta, Facebook, Instagram, and other Meta brand names are trademarks of their respective owners.

mcp-name: co.pipeboard/meta-ads-mcp

Community & Support

• Discord. Join the community.
• Email Support. Email us for support.

Table of Contents

• 🚀 Getting started with Remote MCP (Recommended for Marketers)
• Local Installation (Technical Users Only)
• Features
• Configuration
• Available MCP Tools
• Licensing
• Privacy and Security
• Testing
• Troubleshooting

Getting started with Remote MCP (Recommended)

The fastest and most reliable way to get started is to 🚀 Get started with our Meta Ads Remote MCP. Our cloud service uses streamable HTTP transport for reliable, scalable access to Meta Ads data. No technical setup required - just connect and start analyzing your ad campaigns with AI!

For Claude Pro/Max Users

1. Go to claude.ai/settings/integrations (requires Claude Pro or Max)
2. Click "Add Integration" and enter:
   • Name: "Pipeboard Meta Ads" (or any name you prefer)
   • Integration URL: https://mcp.pipeboard.co/meta-ads-mcp
3. Click "Connect" next to the integration and follow the prompts to:
   • Login to Pipeboard
   • Connect your Facebook Ads account

That's it! You can now ask Claude to analyze your Meta ad campaigns, get performance insights, and manage your advertising.

Advanced: Direct Token Authentication (Claude)

For direct token-based authentication without the interactive flow, use this URL format when adding the integration:

https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN

Get your token at pipeboard.co/api-tokens.

For Cursor Users

Add the following to your ~/.cursor/mcp.json. Once you enable the remote MCP, click on "Needs login" to finish the login process.

{
  "mcpServers": {
    "meta-ads-remote": {
      "url": "https://mcp.pipeboard.co/meta-ads-mcp"
    }
  }
}

Advanced: Direct Token Authentication (Cursor)

If you prefer to authenticate without the interactive login flow, you can include your Pipeboard API token directly in the URL:

{
  "mcpServers": {
    "meta-ads-remote": {
      "url": "https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN"
    }
  }
}

Get your token at pipeboard.co/api-tokens.

For Other MCP Clients

Use the Remote MCP URL: https://mcp.pipeboard.co/meta-ads-mcp

📖 Get detailed setup instructions for your AI client here

Advanced: Direct Token Authentication (OpenClaw and other clients)

For MCP clients that support token-based authentication, you can append your Pipeboard API token to the URL:

https://mcp.pipeboard.co/meta-ads-mcp?token=YOUR_PIPEBOARD_TOKEN

This bypasses the interactive login flow and authenticates immediately. Get your token at pipeboard.co/api-tokens.

Local Installation (Advanced Technical Users Only)

🚀 We strongly recommend using Remote MCP instead - it's faster, more reliable, and requires no technical setup.

Meta Ads MCP also supports a local streamable HTTP transport, allowing you to run it as a standalone HTTP API for web applications and custom integrations. See Streamable HTTP Setup Guide for complete instructions.

Features

• AI-Powered Campaign Analysis: Let your favorite LLM analyze your campaigns and provide actionable insights on performance
• Strategic Recommendations: Receive data-backed suggestions for optimizing ad spend, targeting, and creative content
• Automated Monitoring: Ask any MCP-compatible LLM to track performance metrics and alert you about significant changes
• Budget Optimization: Get recommendations for reallocating budget to better-performing ad sets
• Creative Improvement: Receive feedback on ad copy, imagery, and calls-to-action
• Dynamic Creative Testing: Easy API for both simple ads (single headline/description) and advanced A/B testing (multiple headlines/descriptions)
• Campaign Management: Request changes to campaigns, ad sets, and ads (all changes require explicit confirmation)
• Cross-Platform Integration: Works with Facebook, Instagram, and all Meta ad platforms
• Universal LLM Support: Compatible with any MCP client including Claude Desktop, Cursor, Cherry Studio, and more
• Enhanced Search: Generic search function includes page searching when queries mention "page" or "pages"
• Simple Authentication: Easy setup with secure OAuth authentication
• Cross-Platform Support: Works on Windows, macOS, and Linux

Configuration

Remote MCP (Recommended)

✨ Get started with Remote MCP here - no technical setup required! Just connect your Facebook Ads account and start asking AI to analyze your campaigns.

Local Installation (Advanced Technical Users)

For advanced users who need to self-host, the package can be installed from source. Local installations require creating your own Meta Developer App. We recommend using Remote MCP for a simpler experience.

Available MCP Tools

1. mcp_meta_ads_get_ad_accounts

   • Get ad accounts accessible by a user
   • Inputs:
     • access_token (optional): Meta API access token (will use cached token if not provided)
     • user_id: Meta user ID or "me" for the current user
     • limit: Maximum number of accounts to return (default: 200)
   • Returns: List of accessible ad accounts with their details

2. mcp_meta_ads_get_account_info

   • Get detailed information about a specific ad account
   • Inputs:
     • access_token (optional): Meta API access token (will use cached token if not provided)
     • account_id: Meta Ads account ID (format: act_XXXXXXXXX)
   • Returns: Detailed information about the specified account

3. mcp_meta_ads_get_account_pages

   • Get pages associated with a Meta Ads account
   • Inputs:
     • access_token (optional): Meta API access token (will use cached token if not provided)
     • account_id: Meta Ads account ID (format: act_XXXXXXXXX) or "me" for the current user's pages
   • Returns: List of pages associated with the account, useful for ad creation and management

4. mcp_meta_ads_get_campaigns

   • Get campaigns for a Meta Ads account with optional filtering
   • Inputs:
     • access_token (optional): Meta API access token (will use cached token if not provided)
     • account_id: Meta Ads account ID (format: act_XXXXXXXXX)
     • limit: Maximum number of campaigns to return (default: 10)
     • status_filter: Filter by status (empty for all, or 'ACTIVE', 'PAUSED', etc.)
   • Returns: List of campaigns matching the criteria

5. mcp_meta_ads_get_campaign_details

   • Get detailed information about a specific campaign
   • Inputs:
     • access_token (optional): Meta API access token (will use cached token if not provided)
     • campaign_id: Meta Ads campaign ID
   • Returns: Detailed information about the specified campaign

6. mcp_meta_ads_create_campaign

   • Create a new campaign in a Meta Ads account
   • Inputs:

     • access_token (optional): Meta API access token (will use cached token if not provided)

     • account_id: Meta Ads account ID (format: act_XXXXXXXXX)

     • name: Campaign name

     • objective: Campaign objective (ODAX, outcome-based). Must be one of:

       • OUTCOME_AWARENESS
       • OUTCOME_TRAFFIC
       • OUTCOME_ENGAGEMENT
       • OUTCOME_LEADS
       • OUTCOME_SALES
       • OUTCOME_APP_PROMOTION

       Note: Legacy objectives such as BRAND_AWARENESS, LINK_CLICKS, CONVERSIONS, APP_INSTALLS, etc. are no longer valid for new campaigns and will cause a 400 error. Use the outcome-based values above. Common mappings:

       • BRAND_AWARENESS → OUTCOME_AWARENESS
       • REACH → OUTCOME_AWARENESS
       • LINK_CLICKS, TRAFFIC → OUTCOME_TRAFFIC
       • POST_ENGAGEMENT, PAGE_LIKES, EVENT_RESPONSES, VIDEO_VIEWS → OUTCOME_ENGAGEMENT
       • LEAD_GENERATION → OUTCOME_LEADS
       • CONVERSIONS, CATALOG_SALES, MESSAGES (sales-focused flows) → OUTCOME_SALES
       • APP_INSTALLS → OUTCOME_APP_PROMOTION

     • status: Initial campaign status (default: PAUSED)

     • special_ad_categories: List of special ad categories if applicable

     • daily_budget: Daily budget in account currency (in cents)

     • lifetime_budget: Lifetime budget in account currency (in cents)

     • bid_strategy: Bid strategy. Must be one of: LOWEST_COST_WITHOUT_CAP, LOWEST_COST_WITH_BID_CAP, COST_CAP, LOWEST_COST_WITH_MIN_ROAS.

---