MCP.Market

ZuckerBot — Meta Ads MCP Server

online · 100% uptime
by Crumbedsausage·io.github.Crumbedsausage/zuckerbot·v0.4.4·13 stars

60+ Meta Ads tools for AI agents: audits, campaign management, audiences and CAPI tracking.

A95/100grade A
What users say
No reviews yet
Be the first
Safety scan
A95/100

full report

Adoption
Growing

13 stars109 downloads/wk

Reviews

Write one

Nobody has reviewed ZuckerBot — Meta Ads MCP Server yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ZuckerBot — Meta Ads MCP Server tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 source files scanned25/25
  • Live reliabilityremote reachable in 289ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 95/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How ZuckerBot — Meta Ads MCP Server compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
95/100
higher than 97% of 48,273 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
533 ms
faster than 28% of 30,037 servers
GitHub stars
13
more than 89% of 28,534 servers
Downloads a week
109
more than 65% of 11,915 servers with a package

Install ZuckerBot — Meta Ads MCP Server in Claude Code, Cursor or VS Code

claude mcp add --transport http zuckerbot https://zuckerbot.ai/api/mcp
Add to Cursor

What the publisher says

From the ZuckerBot — Meta Ads MCP Server repository's README, as published. We do not edit it. Read it on GitHub

ZuckerBot

The Meta Ads toolkit for AI agents.

Audit your ad account in one message. 50+ tools for account auditing, campaign management, creative analysis, audience building, and conversion tracking. One npx command. Works with Claude, ChatGPT, OpenClaw, Cursor, and any MCP-compatible agent.

{
  "mcpServers": {
    "zuckerbot": {
      "command": "npx",
      "args": ["-y", "zuckerbot-mcp"],
      "env": { "ZUCKERBOT_API_KEY": "zb_live_your_key_here" }
    }
  }
}

Get API Key (free) · npm · Docs · Website

Why ZuckerBot?

Your agent already writes code, manages files, and searches the web. It should manage your ads too.

ZuckerBot gives any AI agent full Meta Ads capabilities through MCP. No dashboard, no UI to learn, no platform to log into. Your agent installs it, connects your ad account, and gets to work.

What agents can do with ZuckerBot:

  • Audit your ad account in one message — spend flagged for review, creative fatigue, opportunity score, prioritised action items (free tier included)
  • Pull campaign performance and spot what's working
  • Analyse ad creatives and recommend what to test next
  • Build and launch campaigns with targeting and budget
  • Create custom and lookalike audiences
  • Set up server-side conversion tracking (CAPI)
  • Research competitors, reviews, and market benchmarks
  • Generate ad creative briefs and copy

How it works

You ↔ Your Agent (Claude, ChatGPT, OpenClaw, Cursor, etc.)
                  ↕
            ZuckerBot MCP
                  ↕
         Meta Marketing API

ZuckerBot handles the Meta API complexity. Your agent handles the conversation. You make the decisions.

Install

Claude Desktop

Add to claudedesktopconfig.json:

{
  "mcpServers": {
    "zuckerbot": {
      "command": "npx",
      "args": ["-y", "zuckerbot-mcp"],
      "env": { "ZUCKERBOT_API_KEY": "zb_live_your_key_here" }
    }
  }
}

OpenClaw

Add to your MCP config:

{
  "mcpServers": {
    "zuckerbot": {
      "command": "npx",
      "args": ["-y", "zuckerbot-mcp"],
      "env": { "ZUCKERBOT_API_KEY": "zb_live_your_key_here" }
    }
  }
}

Cursor / Windsurf / Any MCP Client

Same config pattern. ZuckerBot works with any client that supports the Model Context Protocol.

Remote MCP (no install)

Don't want to run anything locally? https://zuckerbot.ai/api/mcp is a hosted Streamable HTTP endpoint serving the same tools.

  • claude.ai — add it as a custom connector (Settings → Connectors → Add custom connector) and authenticate via OAuth, or pass an Authorization: Bearer zblive... header.
  • Claude Code:
claude mcp add --transport http zuckerbot https://zuckerbot.ai/api/mcp --header "Authorization: Bearer zb_live_..."
  • Any Streamable HTTP client — point it at https://zuckerbot.ai/api/mcp with your API key as a bearer token.

CLI (for humans)

npm install -g zuckerbot-mcp

zuckerbot preview https://your-business.com
zuckerbot meta status
zuckerbot create https://your-business.com --budget 5000 --objective leads

Tools (50+)

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

ZuckerBot — Meta Ads MCP Server: common questions

Is ZuckerBot — Meta Ads MCP Server safe?
Yes, by our scan: it is graded A (95/100). Read the ZuckerBot — Meta Ads MCP Server safety report
How do I install ZuckerBot — Meta Ads MCP Server?
It runs remotely at zuckerbot.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does ZuckerBot — Meta Ads MCP Server need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is ZuckerBot — Meta Ads MCP Server maintained?
The last commit was 47 days ago (2026-09-16). The latest release is v0.4.4.
Is ZuckerBot — Meta Ads MCP Server up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does ZuckerBot — Meta Ads MCP Server compare with other MCP servers?
safety score 95/100 (higher than 97% of 48,273 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 533 ms (faster than 28% of 30,037 servers). Full comparison.