A Meta Business Partner that speaks fluent MCP

What it does This repo is Pipeboard’s hosted Model Context Protocol server for Meta Ads. It exposes 42 tools that let AI assistants run Facebook and Instagram campaigns end to end—launching ads, uploading creatives, editing budgets, and pulling performance insights—through natural conversation rather than dashboard clicks. The server is fully remote; you point your MCP client at Pipeboard’s URL and authenticate once.

The interesting bit The project treats ad platforms as a unified agent network rather than isolated integrations. Meta is one of five nodes—alongside Google, TikTok, Snap, and Reddit—sharing a single OAuth flow, rate limit, and safety model where every write demands explicit confirmation and new campaigns start paused. That makes it unusual: a badged Meta Business Partner shipping an open-source MCP interface while betting that cross-platform control matters more than single-platform depth.

Key highlights

• 42 Meta-specific tools covering campaigns, ad sets, creatives, image upload, audience targeting, and page management
• Hosted remote MCP with no self-hosting required; the README actively discourages local installation
• Badged Meta Business Partner and officially approved Meta app, with a free plan available
• One Pipeboard auth grants access to a 230+ tool family across five ad platforms
• Alternative Pipeboard CLI exposes the same tools as typed shell commands for coding agents that prefer subprocess calls

Caveats

• Local installation is documented but treated as a second-class path; the project is clearly optimized for Pipeboard’s hosted service
• It is an independent open-source project consuming Meta’s public APIs, not a first-party Meta product

Verdict Agency developers and marketing teams who want AI assistants to manage spend across multiple ad networks without running infrastructure should try the hosted route. Teams that insist on owning every token and guardrail themselves will still want a self-hosted, single-platform alternative.