Meta Ads MCP

MCP server for Facebook and Instagram ads: campaigns, creatives, budgets and analytics through a conversation with the agent

MCP server OfficialNeeds a VPN

pipeboard-co/meta-ads-mcpAuthor:Pipeboard

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/meta-ads-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Assembled automatically, review before installing.

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport http 'Meta Ads MCP' https://meta-ads.mcp.pipeboard.co/ --header 'Authorization: Bearer <your PIPEBOARD_API_TOKEN>'

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "Meta Ads MCP": {
      "type": "http",
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "Meta Ads MCP": {
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"Meta Ads MCP","type":"http","url":"https://meta-ads.mcp.pipeboard.co/","headers":{"Authorization":"Bearer <your PIPEBOARD_API_TOKEN>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "Meta Ads MCP": {
      "type": "http",
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.codex/config.toml, for all projects

[mcp_servers."Meta Ads MCP"]
url = "https://meta-ads.mcp.pipeboard.co/"
http_headers = { Authorization = "Bearer <your PIPEBOARD_API_TOKEN>" }

If the file already exists, append the block to the end.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "Meta Ads MCP": {
      "httpUrl": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "Meta Ads MCP": {
      "serverUrl": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "Meta Ads MCP": {
      "type": "streamableHttp",
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "Meta Ads MCP": {
      "type": "streamable-http",
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "Meta Ads MCP": {
      "type": "remote",
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "Meta Ads MCP": {
      "url": "https://meta-ads.mcp.pipeboard.co/",
      "headers": {
        "Authorization": "Bearer <your PIPEBOARD_API_TOKEN>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

PIPEBOARD_API_TOKENsecret, required: Your Pipeboard API token for authentication

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Checked against the repository on Sep 26, 2026, commit 093062c.

Text for your agent

Connect the remote MCP server at https://meta-ads.mcp.pipeboard.co/ and sign in to Pipeboard to link your Meta ad account. In claude.ai integration settings add this URL as a remote server, and in Cursor add an entry with a url field in mcp.json.

Other ways from the author

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

Pipeboard remote server. After adding it, sign in to link your Meta ad account.

This is third-party code. Review the repository files before installing.

What it does

The server lets the agent run Meta ads on Facebook and Instagram: create campaigns, ad sets and ads, change budgets, pause them, upload images and creatives, set targeting and read performance. It advertises around 42 tools, including dynamic creative testing and page management. The main way to connect is Pipeboard's hosted remote MCP at meta-ads.mcp.pipeboard.co with OAuth or token sign-in, where Meta accounts are linked once in a dashboard. Every write requires explicit confirmation, and new campaigns start paused where the platform allows it. A local from-source run with your own Meta Developer app is also possible. It is one of five ad servers in the Pipeboard family.

Who it is for. For marketers and founders who run Meta ads and want to manage them through an agent.

Good fit when

You need to analyze Meta campaign performance through a conversation with the agent
You need to create and edit campaigns, ad sets and creatives without manual work in the dashboard
You need to change budgets and targeting quickly with confirmation on every write

Not a fit when

You do not run Meta advertising
You have no access to Meta and Pipeboard services from your region

Example request

Show which Meta campaigns brought the cheapest leads last week and suggest what to optimize

Limitations

The remote server needs a Pipeboard account; the service has a free plan and paid tiers, and a local run needs your own Meta Developer app. Meta services are restricted in Russia and usually require a VPN and a foreign ad account, so we mark access without a VPN as unavailable. Writes change a real ad account and spend real budget. The license is BUSL-1.1, source-available with restrictions rather than a fully free license.

How to disable. Remove the integration in your client settings, for example in claude.ai, or delete the server entry from the MCP config. If you used a token, revoke it in the Pipeboard dashboard.

MCP

Transport: http, stdio
Authentication: OAuth

Environment variables
Environment variables
PIPEBOARD_API_TOKEN secret	Pipeboard token for non-interactive sign-in, obtained from the dashboard.
META_ACCESS_TOKEN secret	Meta access token for a local run with your own Meta Developer app.

Security check

Changes a real Meta ad account and spends real budget
Requires account access and ad platform tokens

README in short

The README describes an MCP server for managing Meta ads on Facebook and Instagram through any MCP client: Claude, ChatGPT, Perplexity, Cursor. The recommended path is Pipeboard's hosted remote MCP over streamable HTTP, with OAuth or token sign-in and ad account linking in a dashboard. The server is the Meta node in Pipeboard's family of five ad servers sharing one login and one write-confirmation model. It advertises around 42 tools for campaigns, ad sets, ads, creatives, image upload, insights and targeting. A local from-source run with your own Meta Developer app is available, under a BUSL-1.1 license.

FAQ

Is this Meta's official server?

No. It is an independent open-source project on Meta's public APIs. The Pipeboard service behind it is described as a Meta Business Partner and an approved Meta app.

How much does it cost?

Pipeboard has a free plan and paid tiers. The local from-source run is free but needs your own Meta Developer app.

Humanizer

Editors’ pick

A skill that strips AI writing tells from text using Wikipedia's list, without adding invented facts

SkillLow riskNo VPN needed52.7K

Marketing Skills for AI agents

Marketing Skills for AI Agents

Editors’ pick

About fifty skills for CRO, copywriting, SEO, analytics, ads and launches, built for coding agents

SkillLow risk51.8K

SendPulse MCP server

SendPulse MCP

Official

SendPulse's official remote MCP server: statistics, campaigns and user data through an agent chat

MCP serverHigh riskRussian stack1

Yandex Direct MCP generated from a machine-readable schema

yandex-direct-mcp

Editors’ pick

An MCP server and CLI covering all 113 Yandex Direct API v5 methods generated from WSDL, exposing 9 read tools by default and writes only on demand

MCP serverHigh riskRussian stackNo VPN needed1

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

Humanizer

Marketing Skills for AI agents

SendPulse MCP server

Yandex Direct MCP generated from a machine-readable schema