convez.ai
MCP ServerMarketing & VendasIntermediário
attainmentlabs

Meta Ads Manager MCP

attainmentlabs/meta-ads-mcp

Gerencie campanhas Meta direto do Claude com segurança

Ver no GitHub
BomPluginScore · de 0 a 100

Servidor MCP para criar, gerenciar e analisar campanhas de anúncios do Meta (Facebook/Instagram) diretamente pelo Claude. Permite automação completa de campanhas com controles de segurança integrados, incluindo criação, pausas, ativação, relatórios e operações em lote.

Instalação

$npx convez-ai attainmentlabs/meta-ads-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
17
Forks
5
Acompanhando
0
Saúde
50%
Último commit
há 1 mês
Versão
—
Issues abertas
2
Contribuidores
1

Casos de uso

  • Criar campanhas publicitárias Facebook/Instagram automatizadas
  • Consultar métricas e performance de anúncios em tempo real
  • Atualizar orçamentos e status de campanhas em lote
  • Auditar e revisar campanhas antes de ativar gastos

Veredito

Solução bem pensada para automação de anúncios Meta com defaults seguros (campanhas pausadas por padrão, confirmação explícita para ações críticas). Recomendado para quem quer controle total sem depender do backend Meta, com código inspecionável e auditável.

README

A tradução para o português deste README ainda está na fila.

meta-ads-manager-mcp

MCP server for creating and managing Meta (Facebook/Instagram) ad campaigns directly from Claude. Tell Claude what you want. It deploys.

Built by Attainment Labs.


Status in the Meta Ads ecosystem

This is an early independent open source Meta Ads MCP server, first published in February 2026 before Meta later introduced its official Ads AI Connectors and hosted Ads MCP endpoint.

Use Meta's official connector if you want Meta-hosted OAuth and first-party support. Use this project if you want a lightweight, self-managed MCP server that you can inspect, fork, and run with your own Meta app credentials.

Related:


What it does

Add this server to your Claude config. You get campaign creation, reporting, bulk operations, budget control, and safety tools:

ToolWhat it does
create_meta_campaignCreate a full campaign: campaign, ad set, creatives, and ads
get_ad_account_summaryConfirm connected ad account, currency, timezone, spend, balance, and status
list_campaignsList recent campaigns in the configured ad account
list_ad_setsList recent ad sets in the configured ad account
list_adsList recent ads in the configured ad account
get_campaign_statusCheck status of a campaign, its ad sets, and ads
get_meta_insightsPull account, campaign, ad set, or ad performance insights
upload_ad_imageUpload an image and return the image hash for creatives
update_daily_budgetUpdate campaign or ad set daily budget
bulk_update_campaign_statusBulk pause, activate, or delete campaigns
pause_campaignPause a live campaign
activate_campaignActivate a paused campaign
delete_campaignPermanently delete a campaign

All campaigns are created as PAUSED by default. You review before spending.

Safety controls:

  • dry_run=True by default on campaign creation, media upload, budget updates, and bulk status changes.
  • confirm=True is required for live campaign creation, uploads, budget updates, activation, deletion, and bulk status changes.
  • META_ADS_MAX_DAILY_BUDGET_CENTS can cap campaign and ad set daily budgets.
  • META_ADS_AUDIT_LOG_PATH can set a JSONL audit log path. Default is ~/.meta-ads-mcp/audit.jsonl.

Install

Option 1: Let Claude set it up for you (easiest)

If you use Claude Code, paste this prompt:

"Set up meta-ads-mcp for me: https://github.com/attainmentlabs/meta-ads-mcp"

Claude will check your environment, walk you through getting your Meta credentials step by step, edit your ~/.mcp.json, and confirm when it's done. No docs to read.


Option 2: uvx (recommended, no install needed)

# No setup required. uvx runs it directly

Add to ~/.mcp.json:

{
  "mcpServers": {
    "meta-ads": {
      "command": "uvx",
      "args": ["meta-ads-manager-mcp"],
      "env": {
        "META_ACCESS_TOKEN": "your-token-here",
        "META_AD_ACCOUNT_ID": "your-account-id",
        "META_PAGE_ID": "your-page-id",
        "META_ADS_MAX_DAILY_BUDGET_CENTS": "5000"
      }
    }
  }
}

Option 2: pip install

pip install meta-ads-manager-mcp

Then in ~/.mcp.json:

{
  "mcpServers": {
    "meta-ads": {
      "command": "meta-ads-manager-mcp",
      "env": {
        "META_ACCESS_TOKEN": "your-token-here",
        "META_AD_ACCOUNT_ID": "your-account-id",
        "META_PAGE_ID": "your-page-id",
        "META_ADS_MAX_DAILY_BUDGET_CENTS": "5000"
      }
    }
  }
}

Credentials

You need three values from Meta. Full step-by-step walkthrough: SETUP.md

VariableWhere to find it
META_ACCESS_TOKENGraph API Explorer. Long-lived token with ads_management permission
META_AD_ACCOUNT_IDBusiness Manager: Ad Accounts. Numbers only, no act_ prefix
META_PAGE_IDFacebook Page: About → Page transparency → Page ID
META_ADS_MAX_DAILY_BUDGET_CENTSOptional daily budget guardrail
META_ADS_AUDIT_LOG_PATHOptional JSONL audit log path

The access token expires after 60 days. See SETUP.md for the exchange flow.


Usage examples

Once the server is connected, just describe what you want:

Create a campaign:

"Create a Meta campaign targeting US fitness enthusiasts aged 25-40. Daily budget $30. Use the image at /Users/me/ads/hero.jpg. Copy: 'Track every rep. Hit every goal.' Headline: 'FitCommit AI'. CTA: Learn More. Link to fitcommit.ai."

Check status:

"What's the status of campaign 120243616427570285?"

List campaigns:

"List my recent Meta campaigns."

Pull insights:

"Show Meta ad account insights for the last 7 days by campaign."

Update budget safely:

"Dry run a budget update to set ad set 120243616427570285 to $30 per day."

Bulk pause:

"Dry run pausing these three campaigns: 111, 222, 333."

Pause:

"Pause campaign 120243616427570285."

Activate:

"Go live with campaign 120243616427570285."

Delete:

"Delete campaign 120243616427570285."


dry_run mode

create_meta_campaign, upload_ad_image, update_daily_budget, and bulk_update_campaign_status default to dry_run=True. This simulates API calls and returns fake IDs or planned changes without making requests or spending money.

For live changes, set dry_run=False and confirm=True.

activate_campaign and delete_campaign also require confirm=True.


YAML workflow

Prefer writing campaigns as config files? Use meta-ads-cli, the companion CLI tool.


Requirements

  • Python 3.10+
  • uv for the uvx install path
  • A Meta Business Manager account with an ad account and Facebook Page

License

MIT

Ver o original no GitHub

Bom para

Relacionados