M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
M

Meta Ads MCP

Community
Manage Meta Ads through AI conversation.
How to install ↓ Compare GitHub source repository ↗
Category
Other #196 of 230
Stars
★ 1.3k Very popular
Transport
Streamable HTTP
Runtime
Hosted (no local runtime)
Credentials
API key / credential required
License
Other / unspecified
Last commit
Tools
29
41FMRS · D

This is a hosted remote MCP server for Meta advertising operations, covering accounts, campaigns, ad sets, ads, creatives, targeting, budgets, and insights. The source documents compatibility with multiple MCP clients and describes write confirmations plus paused initial campaigns; it is not maintained by Meta, and remote use requires evaluating data and advertising-operation risks.

Strongest · Setup experience 11/20 Weakest · Reliability 7/20

Reliability
7/20
Security and permissions
7/20
Maintenance
7/20
Documentation
9/20
Setup experience
11/20
Why each score
Reliability 7/20
The static material shows a plausible Streamable HTTP remote endpoint, client configuration examples, and fairly detailed tool parameters, but provides no committed CI, tests, or reproducible evidence for initialization and tools/list. The manifest URL differs from the README's recommended URL, the README claims 42 tools while only 29 are detailed, and error handling, dependencies, and edge behavior are not evidenced, so points are deducted.
Security and permissions 7/20
The README claims explicit confirmation for writes and paused defaults for new ads, and says remote authentication is handled in the cloud; however, these controls are not supported by source-code or test evidence. Tools broadly accept optional access tokens, and the README recommends placing an API token in a URL query parameter, creating leakage risk through logs, browser history, or proxies. Permission scope, data flow, retention, and least privilege are insufficiently documented. No malware, credential theft, or other explicit red-line behavior is shown, so this is not scored in the 0-4 range.
Maintenance 7/20
The repository is not archived, the manifest gives a defined name and version 1.0.118, and the README provides Discord, email support, and Pipeboard ownership cues, so it is not visibly abandoned. However, there is no commit history, release cadence, dependency-update evidence, vulnerability-response process, or verifiable maintainer identity. The manifest says NOASSERTION while the README claims Business Source License 1.1, so the licensing evidence is contradictory and points are deducted.
Documentation 9/20
The README supplies remote and local paths, setup examples for several mainstream clients, authentication steps, inputs and outputs for 29 tools, an example, licensing information, and basic troubleshooting. Points are deducted because the manifest and README disagree on the remote URL, the tool counts do not match, the local setup guide is referenced but not provided, and there is no clear evidence for costs, rate limits, retention, permission scope, or systematic error diagnosis.
Setup experience 11/20
The hosted MCP path is short and covers Claude, Cursor, and other MCP clients, with stated Windows, macOS, and Linux support. Points are deducted for two different remote URLs, dependence on an external Pipeboard account and Meta account connection, the security and fragility of query-parameter token configuration, and missing runtime details for the local installation path.

Static review · not runListed 2026-07-29

Read the FMRS scoring method →

Fit and risk

What it can accessUses the networkChanges third-party account data

Best for

  • Marketers managing Facebook and Instagram advertising
  • Teams wanting conversational AI analysis and control of Meta Ads
  • Users who prefer hosted remote MCP access without managing infrastructure
  • Users needing dynamic creative testing and performance insights

Not for

  • Users who only need read-only reporting and do not want write access
  • Users without Meta advertising activity or an accessible ad account
  • Users requiring fully self-hosted operation with no hosted service
  • Users specifically seeking an MCP server maintained by Meta

Required permissions

  • Requires access to Meta ad accounts, campaigns, ad sets, ads, creatives, Pages, and performance data depending on the tool used
  • Write operations may create or modify campaigns, ad sets, ads, creatives, budgets, statuses, and targeting
  • Authentication uses Pipeboard OAuth or a Pipeboard token; local deployment requires a Meta Developer App

Risks and side effects

  • Creating or updating ads can trigger real delivery and spending; writes should be reviewed before confirmation
  • Incorrect budgets, bids, targeting, or statuses can affect performance and spend
  • The remote service processes ad-account requests; users should evaluate their trust in Pipeboard
  • Image uploads and creative changes can affect brand presentation and campaign results

Setup

Before you start

Runtime：Hosted (no local runtime)

PIPEBOARD_API_TOKEN optionalsecret Pipeboard API token used only for direct token auth via ?token= URL parameter; obtain at pipeboard.co/api-tokens. Not required as a local env var when using the hosted remote MCP with interactive OAuth.

Use the hosted remote MCP: connect a Facebook Ads account through Pipeboard, then add https://meta-ads.mcp.pipeboard.co/ to a compatible MCP client. In Cursor, place the provided configuration in ~/.cursor/mcp.json and complete login. Claude users can add the URL under Integrations; some clients also support appending a Pipeboard token to the URL. Advanced users can deploy locally using the repository's Streamable HTTP guide, but must create their own Meta Developer App.

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

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

.vscode/mcp.json
{
  "servers": {
    "meta-ads-remote": {
      "url": "https://meta-ads.mcp.pipeboard.co/"
    }
  }
}

Goes in your project's .vscode/mcp.json (VS Code uses a "servers" key).

Terminal
claude mcp add --transport http meta-ads-remote https://meta-ads.mcp.pipeboard.co/

Run it in a terminal; replace any <…> placeholders with your own values first.

Generate and validate client config

Check that it works

After adding the remote URL https://meta-ads.mcp.pipeboard.co/ and logging in, check that mcp_meta_ads_get_ad_accounts appears in the client's tool list, then ask the AI to use it to list your ad accounts — a returned account list confirms the connection works.

Troubleshooting

  1. Confirm that the MCP client supports streamable HTTP
  2. Confirm that Pipeboard login is complete and the correct Facebook Ads account is connected
  3. Call mcp_meta_ads_get_ad_accounts first to verify access, then mcp_meta_ads_get_account_info
  4. Check the remote URL and login state in the Cursor configuration
  5. For local deployment, check Streamable HTTP configuration, the Meta Developer App, and token caching
  6. When creating campaigns, use the documented outcome-based objectives rather than deprecated legacy objectives

Things to try

Once connected, you can ask your AI assistant things like:

  • List all my accessible Meta ad accounts and show recent spend for each.
  • Create a new awareness campaign called '2025 - Bedroom Furniture - Awareness' in account act_123456789012345, starting paused.
  • Show performance insights for my campaigns over the last 7 days broken down by age, and suggest budget reallocations.
  • Search interest targeting options for 'travel' and show audience sizes.

Tools 29

mcp_meta_ads_get_ad_accounts read-only
Get ad accounts accessible by a user.
mcp_meta_ads_get_account_info read-only
Get detailed information about a specified ad account.
mcp_meta_ads_get_account_pages read-only
Get Facebook Pages associated with an ad account.
mcp_meta_ads_get_campaigns read-only
Get campaigns with optional status filtering.
mcp_meta_ads_get_campaign_details read-only
Get detailed information about a campaign.
mcp_meta_ads_create_campaign writes
Create a campaign with objectives, budgets, bid strategy, and initial status.
mcp_meta_ads_get_adsets read-only
Get ad sets, optionally filtered by campaign.
mcp_meta_ads_get_adset_details read-only
Get detailed information about an ad set.
Show 21 more tools
mcp_meta_ads_create_adset writes
Create an ad set with budget, targeting, optimization, billing, and scheduling settings.
mcp_meta_ads_get_ads read-only
Get ads, optionally filtered by campaign or ad set.
mcp_meta_ads_create_ad writes
Create an ad using an existing creative.
mcp_meta_ads_get_ad_details read-only
Get detailed information about an ad.
mcp_meta_ads_get_ad_creatives read-only
Get creative details including text, images, and URLs.
mcp_meta_ads_create_ad_creative writes
Create a creative from an uploaded image, supporting simple ads or dynamic creative testing.
mcp_meta_ads_update_ad_creative writes
Update creative content or settings.
mcp_meta_ads_upload_ad_image writes
Upload an image for use in an ad creative.
mcp_meta_ads_get_ad_image read-only
Get, download, and visualize an ad image.
mcp_meta_ads_update_ad writes
Update an ad's status or bid amount.
mcp_meta_ads_update_adset writes
Update ad set status, targeting, bidding, and frequency controls.
mcp_meta_ads_get_insights read-only
Get performance metrics for an account, campaign, ad set, or ad.
mcp_meta_ads_get_login_link read-only
Get a Meta Ads authentication login link.
mcp_meta_ads_create_budget_schedule writes
Create a budget schedule for a campaign.
mcp_meta_ads_search_interests read-only
Search interest targeting options by keyword.
mcp_meta_ads_get_interest_suggestions read-only
Get interest suggestions based on existing interests.
mcp_meta_ads_validate_interests read-only
Validate interest names or IDs for targeting.
mcp_meta_ads_search_behaviors read-only
Get behavior targeting options.
mcp_meta_ads_search_demographics read-only
Get demographic and related targeting options.
mcp_meta_ads_search_geo_locations read-only
Search geographic targeting options.
mcp_meta_ads_search read-only
Search accounts, campaigns, ads, and Pages.

Use cases

Inspect campaign performance through natural language
Create, pause, and update campaigns, ad sets, and ads
Upload images, create creatives, and test multiple headlines and descriptions
Search interest, behavior, demographic, and geographic targeting
Receive budget, targeting, and creative optimization recommendations

Supported clients

Claude
Claude Desktop
ChatGPT
Perplexity
Cursor
Cherry Studio

Listed from the project's documentation, not tested by this site.

Overview

Meta Ads MCP is a hosted remote MCP server from Pipeboard that lets Claude, ChatGPT, Perplexity, Cursor, and other MCP clients manage Facebook, Instagram, and other Meta ad surfaces through natural language. It covers campaigns, ad sets, ads, creatives, budgets, targeting, and performance analysis. The project uses Meta's public APIs; the hosted service requires no self-hosting or developer token and supports OAuth authentication.

Similar servers

BioMCP 75 · B

One binary. One grammar. Evidence from the biomedical sources you already trust.

★ 659 · Tools 11 Compare with this →
Compare with other MCP servers

Source revision 093062c66556 Data synced 2026-10-19 Read the FMRS scoring method