OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
MCP & Tooling

Meta Ads MCP

Meta Ads MCP is a hosted remote Model Context Protocol server that connects compatible AI assistants to Meta advertising operations across Facebook, Instagram and other Meta ad surfaces.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Meta Ads MCP — OpenViST project profile in MCP & Tooling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when you want a connected AI assistant to handle documented Meta Ads tasks through natural-language requests, or to review campaign performance without switching away from the MCP client.

Who it is for

  • Advertisers and marketing teams using an MCP-compatible assistant to work with Meta campaigns.
  • Developers configuring an assistant connection or a local installation for Meta advertising workflows.

Documented uses

  • Launch campaigns, ad sets and ads, and update budgets or targeting.
  • Upload images and create or edit ad copy, headlines, descriptions and calls to action.
  • Retrieve campaign and account information and analyze advertising performance.
  • Ask for recommendations on ad spend, targeting and creative improvements.
Before you choose

Requirements & limits

The hosted remote MCP is presented as requiring no self-hosting or developer token. Claude’s documented setup requires Pro or Max; the README’s Cursor setup uses a Pipeboard login and a connected Facebook Ads account.

  • The hosted endpoint is the recommended route; local installation requires creating a Meta Developer App.
  • The README says every write requires explicit confirmation.
  • The project is published as open source and identifies Python as its primary language.
  • Pipeboard’s CLI is a separate option for shell-based workflows.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Connect Claude to Meta Ads MCP

Set up the hosted remote MCP integration in Claude and connect a Facebook Ads account.

Before you start

  • Claude Pro or Max
  • A Pipeboard login
  • A Facebook Ads account to connect

Steps

  1. Open Claude’s integrations settings and add an integration using https://meta-ads.mcp.pipeboard.co/ as its URL.

  2. Select Connect for the integration.

  3. Log in to Pipeboard and follow the prompts to connect the Facebook Ads account.

Expected outcome

Claude can use the connected MCP server to analyze Meta ad campaigns, review performance insights and manage advertising.

Guide limitations

  • The documented Claude setup requires a Pro or Max plan.
  • This guide covers the hosted connection, not local installation.
Documentation 1 ↗
Source-based practical guide

Add the remote MCP server to Cursor

Configure Cursor to connect to the hosted Meta Ads MCP server.

Before you start

  • Cursor
  • A Pipeboard login
  • A Facebook Ads account to connect

Steps

  1. Add a server entry named meta-ads-remote with the URL https://meta-ads.mcp.pipeboard.co/ to ~/.cursor/mcp.json.

  2. Enable the remote MCP server in Cursor.

  3. Select “Needs login” and complete the login flow.

Expected outcome

Cursor is connected to the Meta Ads MCP server after login, allowing it to use the documented advertising tools.

Guide limitations

  • The guide describes the interactive login route; direct token authentication is a separate advanced option.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
pipeboard-co/meta-ads-mcp · Official homepage title · retained in its source language
How we review sourcesSuggest a correction