Meta Ads MCP

What pipeboard-co/meta-ads-mcp MCP server does

The pipeboard-co/meta-ads-mcp MCP server connects an MCP-compatible assistant to Meta advertising accounts. It covers the main hierarchy of Meta Ads objects: ad accounts, campaigns, ad sets, ads, and creatives. Supported workflows include creating campaigns, setting objectives and budgets, configuring targeting and optimization, uploading images, creating ads, and retrieving performance insights.

The server is intended for Facebook and Instagram advertising managed through Meta's advertising APIs. Campaigns can be created with an initial paused state, and ad configuration can include page IDs, destination URLs, copy, headlines, descriptions, tracking specifications, and dynamic creative settings.

How it works

The recommended deployment is a hosted remote MCP service using the endpoint https://meta-ads.mcp.pipeboard.co/. An MCP client connects to that URL and discovers the available tools. The README identifies 42 Meta Ads tools covering campaigns, ad sets, ads, creatives, image uploads, insights, and several targeting-related operations.

Authentication is handled through Pipeboard. Users can complete an interactive login and connect a Facebook Ads account, or provide a Pipeboard API token through the endpoint URL. The remote approach avoids local server hosting and does not require a Meta developer token according to the project documentation.

Write operations use an explicit confirmation model, and newly created campaigns start paused where supported. This is relevant for agents that can both inspect account data and make changes, since analysis and mutation can occur in the same MCP session.

Setup and configuration

For Claude, add the hosted URL as an integration and complete the Pipeboard and Facebook Ads login flow. Cursor users can place the endpoint in ~/.cursor/mcp.json as a remote MCP server, then finish authentication when the client prompts for login. Other MCP clients can use the same remote URL if they support the required remote MCP transport.

The pipeboard-co/meta-ads-mcp MCP server can also accept a Pipeboard token in the URL for direct token authentication. The documented pattern is https://meta-ads.mcp.pipeboard.co/?token=YOUR_PIPEBOARD_TOKEN; the token is obtained from Pipeboard's API token page. No local environment variables are required for the hosted connection described in the README.

Tools and capabilities

Available inputs cover common Meta Ads resource operations, including:

• Listing ad accounts for a Meta user, with account limits and status filters.
• Creating and updating campaigns with objectives, statuses, special ad categories, budgets, and bid strategies.
• Creating ad sets with targeting specifications, optimization goals, billing events, bids, and bid constraints.
• Creating ads from existing creatives or supplied image, page, URL, copy, headline, and description fields.
• Supporting single and dynamic creative variants through headline, description, tracking, and dynamic creative parameters.
• Uploading images and retrieving campaign performance insights.

Values such as budgets and bid amounts are supplied in cents in the account currency. Several fields are constrained by Meta-specific options, including campaign objectives, bid strategies, and optimization or billing settings.

Limitations and notes

The hosted service depends on access to Pipeboard and a connected Meta Ads account. It is not a standalone local implementation in the recommended setup. Users choosing direct token authentication must protect the token because it is included in the connection URL.

The project documentation describes the repository as an independent open-source project using Meta's public APIs, while the hosted service is operated by Pipeboard. The provided material does not specify the repository's software license or provide a local installation command, so those details should not be assumed.