Meta Ads MCP Server

Disclaimer: This is an unofficial third-party tool and is not associated with, endorsed by, or affiliated with Meta in any way. This project is maintained independently and uses Meta's public APIs in accordance with their Terms of Service. Meta, Facebook, Instagram, and other Meta brand names are trademarks of their respective owners.

Table of Contents

• Features

• Requirements

• Installation

• Obtaining a Meta Access Token

• Authentication

• Enabling Write Tools

• Transport Modes

• Cursor / Claude Desktop Setup

• Remote HTTP Server

• Available Tools

  • Accounts

  • Campaigns

  • Ad Sets

  • Ads

  • Creatives

  • Media

  • Insights

  • Targeting Catalog

  • Pages

  • Budget Schedules

  • Activities

  • Pagination

• End-to-End: Create an Ad from Scratch

• Pagination

• Development

• Project Structure

• License

Related MCP server: ArmaVita Meta Ads MCP

Features

All mutation tools (create / update / delete / pause / resume / upload / budget schedule) are off by default and only register when you opt in — see Enabling Write Tools.

Requirements

• Node.js >= 18

• A Meta User Access Token with the right permissions for what you plan to do — see below.

Installation

# From npm
npx meta-ads-mcp-server --access-token YOUR_META_ACCESS_TOKEN

# From source
git clone https://github.com/hashcott/meta-ads-mcp.git
cd meta-ads-mcp
npm install
npm run build
node dist/index.js --access-token YOUR_META_ACCESS_TOKEN

Obtaining a Meta Access Token

This server uses the Meta Marketing API. You need an access token attached to a Meta App that has the right permissions.

Quick option — Graph API Explorer (read-only experiments)

1. Open the Graph API Explorer.

2. Pick your Meta App from the top-right dropdown (create one at developers.facebook.com/apps if you don't have any — choose type "Business").

3. Click Generate Access Token, then under Permissions add at minimum:

   • ads_read — for all the read tools.

   • ads_management — required for any write tool (create / update / delete / pause / resume / upload / budget schedule).

   • business_management — recommended if you operate via Business Manager.

   • pages_show_list, pages_read_engagement — required for the Pages tools.

4. Copy the generated token. This is a short-lived token (~1 hour) — fine for testing.

Production option — long-lived User token

Short-lived tokens from the Explorer expire in about an hour. Exchange yours for a 60-day token:

curl -G "https://graph.facebook.com/v22.0/oauth/access_token" \
  --data-urlencode "grant_type=fb_exchange_token" \
  --data-urlencode "client_id=YOUR_APP_ID" \
  --data-urlencode "client_secret=YOUR_APP_SECRET" \
  --data-urlencode "fb_exchange_token=YOUR_SHORT_LIVED_TOKEN"

Response contains "access_token": "..." — that token is valid for ~60 days. Refresh it the same way before it expires, or build a full OAuth flow if you need permanent access.

Production option — System User token (recommended for servers)

For unattended production use (no expiry), generate a System User token in Business Manager:

1. Go to Business Manager → Business Settings → Users → System Users.

2. Create a system user (or use an existing one), assign the relevant ad account, and grant ads_read / ads_management.

3. Click Generate New Token → pick your Meta App → select the same permissions → Never for expiration.

System User tokens don't expire and are ideal for backend deployments.

Verifying your token

curl "https://graph.facebook.com/v22.0/me?access_token=YOUR_TOKEN"

Should return your user/system-user object. If it returns an error, double-check the permissions and that the token isn't expired.

Authentication

Pass your Meta access token using either method:

CLI argument (recommended for Cursor / Claude Desktop):

node dist/index.js --access-token YOUR_META_ACCESS_TOKEN

Environment variable:

export META_ADS_ACCESS_TOKEN=YOUR_META_ACCESS_TOKEN
node dist/index.js

The token is held only in memory of the running process — it is never written to disk by this server.

Enabling Write Tools

By default the server registers only the 35 read tools — create / update / delete / pause / resume / upload / budget-schedule tools are not exposed. This is intentional: a mistakenly-issued meta_ads_delete_campaign can permanently remove campaigns and their ads.

To opt in, set:

META_ADS_ENABLE_WRITE_TOOLS=true

Accepted truthy values: true, 1, yes, on (case-insensitive). Anything else (or unset) keeps writes off.

When enabled, the server logs a one-line warning to stderr at startup:

[meta-ads-mcp] WARNING: META_ADS_ENABLE_WRITE_TOOLS is on — create/update/delete/pause/resume tools are EXPOSED. These can permanently delete campaigns/ad sets/ads or change live delivery.

Your access token also needs the ads_management permission for the writes to succeed.

Example Cursor / Claude Desktop configuration with writes enabled:

{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": ["-y", "meta-ads-mcp-server"],
      "env": {
        "META_ADS_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN",
        "META_ADS_ENABLE_WRITE_TOOLS": "true"
      }
    }
  }
}

Transport Modes

Cursor / Claude Desktop Setup

Add one of the following to your MCP client configuration file:

Via npx (recommended — no local install required):

{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": ["-y", "meta-ads-mcp-server", "--access-token", "YOUR_META_ACCESS_TOKEN"]
    }
  }
}

Via local build:

{
  "mcpServers": {
    "meta-ads": {
      "command": "node",
      "args": ["/path/to/meta-ads-mcp/dist/index.js", "--access-token", "YOUR_META_ACCESS_TOKEN"]
    }
  }
}

Via environment variable (and opt-in writes):

{
  "mcpServers": {
    "meta-ads": {
      "command": "npx",
      "args": ["-y", "meta-ads-mcp-server"],
      "env": {
        "META_ADS_ACCESS_TOKEN": "YOUR_META_ACCESS_TOKEN",
        "META_ADS_ENABLE_WRITE_TOOLS": "true"
      }
    }
  }
}

Remote HTTP Server

Run as a persistent HTTP server for use with Claude.ai custom connectors or any remote MCP client.

# Start on default port 3000
TRANSPORT=http META_ADS_ACCESS_TOKEN=YOUR_TOKEN node dist/index.js

# Start on a custom port, writes enabled
TRANSPORT=http \
  META_ADS_ACCESS_TOKEN=YOUR_TOKEN \
  META_ADS_ENABLE_WRITE_TOOLS=true \
  PORT=8080 \
  node dist/index.js

Endpoints:

• POST /mcp — MCP protocol endpoint

• GET /health — Health check ({"status":"ok"})

Adding to Claude.ai

1. Go to Settings → Connectors → Add custom connector

2. Enter your server URL: https://your-domain.com/mcp

3. Click Add

Local testing with ngrok

# Terminal 1 — start the server
TRANSPORT=http META_ADS_ACCESS_TOKEN=YOUR_TOKEN PORT=8080 node dist/index.js

# Terminal 2 — expose publicly
ngrok http 8080

Use the generated HTTPS URL (e.g. https://xxxx.ngrok-free.app/mcp) as your connector URL.

Deploying to cloud platforms

Set the following environment variables on your hosting provider (Railway, Render, Fly.io, etc.):

Available Tools

Legend: 🔍 read • ✏️ write (gated by META_ADS_ENABLE_WRITE_TOOLS) • 🛠️ pure utility (no API call).

Accounts

Campaigns

meta_ads_create_campaign inputs:

• act_id (string) — Ad account ID, format act_XXXXXXXXX.

• name (string) — Campaign name.

• objective (enum) — ODAX outcome-based objective:

  • OUTCOME_AWARENESS, OUTCOME_TRAFFIC, OUTCOME_ENGAGEMENT, OUTCOME_LEADS, OUTCOME_SALES, OUTCOME_APP_PROMOTION.

  • Legacy objectives (BRAND_AWARENESS, LINK_CLICKS, CONVERSIONS, APP_INSTALLS, …) are not accepted by Meta v22+ and will return HTTP 400.

• status (default PAUSED), special_ad_categories (default [])

• daily_budget / lifetime_budget (cents) — omit both when use_adset_level_budgets=true.

• bid_strategy — LOWEST_COST_WITHOUT_CAP (default), LOWEST_COST_WITH_BID_CAP, COST_CAP, LOWEST_COST_WITH_MIN_ROAS. Bid-cap strategies require bid_amount on every child ad set.

• bid_cap, spend_cap, campaign_budget_optimization, use_adset_level_budgets, ab_test_control_setups, buying_type.

{
  "act_id": "act_123456789012345",
  "name": "2026 - Spring Sale - Awareness",
  "objective": "OUTCOME_AWARENESS",
  "special_ad_categories": [],
  "status": "PAUSED",
  "bid_strategy": "LOWEST_COST_WITHOUT_CAP",
  "daily_budget": 10000
}

Ad Sets

meta_ads_create_adset highlights:

• Required: act_id, campaign_id, name, optimization_goal, billing_event.

• targeting (object) — full targeting spec; remember targeting_automation.advantage_audience defaults to 0 on Meta v24+ — set it explicitly if you want Advantage+ Audience.

• bid_amount — required for LOWEST_COST_WITH_BID_CAP / COST_CAP.

• bid_constraints — required for LOWEST_COST_WITH_MIN_ROAS, e.g., {"roas_average_floor": 20000} for a 2.0× ROAS floor.

• dsa_beneficiary / dsa_payor — required for EU-targeted ad sets.

• promoted_object — required for APP_INSTALLS.

• frequency_control_specs — MUST be set at creation; Meta makes it immutable afterward.

• regional_regulated_categories / regional_regulation_identities — Taiwan / Australia / Singapore / India regulated verticals.

Ads

ℹ️ Swapping creative_id on a FLEX ad can fail with error_subcode 3858355 if the new creative's asset_feed_spec images don't match its object_story_spec. In that case, create a new ad with the new creative and pause the old one (you lose social proof but the ad runs).

Creatives

meta_ads_create_ad_creative — three common modes:

1. Promote an existing post: pass only object_story_id in the form {page_id}_{post_id}.

2. Single-image link ad: page_id + image_hash + link_url + message + optional headline, description, call_to_action_type.

3. Single-video ad: page_id + video_id + link_url + message + optional headline, call_to_action_type, thumbnail_url.

For advanced layouts (FLEX/DOF, Placement Asset Customization, Dynamic Creative, multi-headline, lead-gen forms, branded content, image crops), pass a fully composed object_story_spec and/or asset_feed_spec — those take precedence over the simple-mode auto-construction.

Media

meta_ads_upload_ad_image accepts exactly one of:

• file — a data URL (data:image/png;base64,iVBORw0KG...) or a raw base64 string.

• image_url — a public URL; the server downloads the bytes and uploads them.

Returns the image_hash you then pass to meta_ads_create_ad_creative.

Insights

All four accept the same option surface: fields, date_preset, time_range, time_ranges, time_increment, level, action_attribution_windows, action_breakdowns, breakdowns, filtering, sort, pagination, and locale.

Time-range precedence: time_ranges > time_range > since/until > date_preset.

Targeting Catalog

Pages

The returned page_id values are the ones you pass to meta_ads_create_ad_creative.

Budget Schedules

Inputs:

• campaign_id (string)

• budget_value (int, positive)

• budget_value_type — ABSOLUTE (cents in account currency) or MULTIPLIER (e.g., 2 doubles the budget)

• time_start, time_end (Unix timestamps in seconds) — time_end > time_start

Activities

Pagination tool

End-to-End: Create an Ad from Scratch

A typical "build a new ad" workflow uses tools across several categories. With META_ADS_ENABLE_WRITE_TOOLS=true:

1. meta_ads_list_ad_accounts                       → pick an act_id
2. meta_ads_get_account_pages                      → pick a page_id
3. meta_ads_search_geo_locations(q="Vietnam")      → grab the country/region keys
4. meta_ads_search_interests(q="cooking")          → grab interest IDs
5. meta_ads_estimate_audience_size(act_id, targeting)  → sanity-check reach
6. meta_ads_upload_ad_image(act_id, image_url)     → returns image_hash
7. meta_ads_create_campaign(act_id, ...)           → returns campaign_id
8. meta_ads_create_adset(act_id, campaign_id, targeting, ...)  → returns adset_id
9. meta_ads_create_ad_creative(act_id, page_id, image_hash, link_url, message, ...)  → returns creative_id
10. meta_ads_create_ad(act_id, name, adset_id, creative_id, status="PAUSED")  → returns ad_id
11. (Optional) meta_ads_get_ad_previews(ad_id, ...)  → render placements before going live
12. meta_ads_resume_ad(ad_id)                       → flip to ACTIVE when ready

All steps that mutate state default to status: "PAUSED" so nothing goes live until you explicitly call a resume tool.

Pagination

Many list tools return paginated results. When a response contains a paging.next URL, use meta_ads_fetch_pagination_url to retrieve subsequent pages:

1. Call meta_ads_get_campaigns_by_adaccount  →  receive first page
2. Check if response.paging.next exists
3. Call meta_ads_fetch_pagination_url(url=response.paging.next)  →  receive next page
4. Repeat until paging.next is absent

Development

npm run dev              # Watch mode — auto-recompile on change
npm run build            # Compile TypeScript to dist/
npm run clean            # Remove dist/
npm run clean && npm run build   # Full rebuild from scratch

Quick smoke test:

# Default (read-only)
META_ADS_ACCESS_TOKEN=dummy node dist/index.js
# → "Meta Ads MCP server running via stdio"

# With writes enabled
META_ADS_ACCESS_TOKEN=dummy META_ADS_ENABLE_WRITE_TOOLS=true node dist/index.js
# → WARNING line + "Meta Ads MCP server running via stdio"

Project Structure

meta-ads-mcp/
├── src/
│   ├── index.ts                  # Entry point, server setup, transport selection, write-tools warning
│   ├── constants.ts              # API version, base URLs, isWriteToolsEnabled() flag
│   ├── types.ts                  # Shared TypeScript interfaces
│   ├── services/
│   │   └── graph-api.ts          # HTTP client (GET/POST/DELETE), auth, error handling, param builders
│   ├── schemas/
│   │   ├── common.ts             # Shared Zod schemas (pagination, date ranges, filters)
│   │   └── insights.ts           # Insights-specific Zod schemas
│   └── tools/
│       ├── accounts.ts           # Account tools
│       ├── insights.ts           # Insights tools (account/campaign/adset/ad level)
│       ├── campaigns.ts          # Campaign read + write/lifecycle tools
│       ├── adsets.ts             # Ad set read + write/lifecycle tools
│       ├── ads.ts                # Ad read + write/lifecycle tools
│       ├── creatives.ts          # Creative read tools, image crops utility, create/update creative
│       ├── media.ts              # Image list / upload / hash lookup / video / preview
│       ├── activities.ts         # Activity log tools
│       ├── pagination.ts         # Pagination utility tool
│       ├── targeting.ts          # Interest/behavior/demographic/geo search + audience-size estimate
│       ├── pages.ts              # Facebook Pages list and name search
│       └── budget-schedules.ts   # Campaign budget schedule create
├── dist/                         # Compiled JavaScript output (generated)
├── package.json
└── tsconfig.json

License

MIT © hashcott