ZuckerBot — Claude Code MCP server for Meta Ads audits and campaigns
Wires your agent into the Meta Marketing API: account audits, campaign management, audiences and server-side conversion tracking. Useful when you'd rather run ads from chat than from a dashboard.
claude mcp add --transport http zuckerbot https://zuckerbot.ai/api/mcpWhat ZuckerBot — Meta Ads MCP Server does
ZuckerBot is an MCP server from DatalisHQ that exposes the Meta Marketing API to your agent. It ships more than 50 tools: an account audit with an opportunity score and a prioritised to-do list, campaign management, creative analysis, audience building and CAPI setup. The agent picks the right tool once you describe the job in plain words.
Two ways to run it. Locally with npx -y zuckerbot-mcp, which needs ZUCKERBOT_API_KEY in the client config. Or remotely against https://zuckerbot.ai/api/mcp, a Streamable HTTP endpoint that keeps nothing on your machine. No key means no server. Launching campaigns also requires a connected ad account and a selected Facebook page.
One tool is worth flagging: activate_campaign is marked temporarily unavailable, so campaigns built through the intelligence flow stay in planning. Actual launches go through launch_campaign. MIT licence, repo at DatalisHQ/zuckerbot.
What it helps with
- audit an ad account and find where spend is being wasted
- build a campaign with targeting and budget from the chat window
- create a lookalike audience from an existing seed
- set up server-side conversion tracking with CAPI
- pull campaign metrics: spend, leads, CPL, CTR, ROAS
Example prompts for the agent
- Audit my ad account and tell me what to fix first
- Draft a leads campaign with a 5000 budget and suggest creative angles
- Build a lookalike audience from my current seed audience
How to install ZuckerBot — Meta Ads MCP Server
1Platform CLI: remote server
claude mcp add --transport http zuckerbot https://zuckerbot.ai/api/mcp2Platform CLI
claude mcp add --env ZUCKERBOT_API_KEY=<ZUCKERBOT_API_KEY> --transport stdio zuckerbot-meta-ads-mcp-server -- npx -y zuckerbot-mcpReplace <…> with your own values
1Platform CLI: remote server
codex mcp add zuckerbot-meta-ads-mcp-server --url https://zuckerbot.ai/api/mcp2Platform CLI
codex mcp add zuckerbot-meta-ads-mcp-server --env ZUCKERBOT_API_KEY=<ZUCKERBOT_API_KEY> -- npx -y zuckerbot-mcpReplace <…> with your own values
Config file
{
"mcpServers": {
"zuckerbot-meta-ads-mcp-server": {
"url": "https://zuckerbot.ai/api/mcp"
}
}
}{
"mcpServers": {
"zuckerbot-meta-ads-mcp-server": {
"command": "npx",
"args": [
"-y",
"zuckerbot-mcp"
],
"env": {
"ZUCKERBOT_API_KEY": "<ZUCKERBOT_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"zuckerbot-meta-ads-mcp-server": {
"type": "http",
"url": "https://zuckerbot.ai/api/mcp"
}
}
}{
"servers": {
"zuckerbot-meta-ads-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"zuckerbot-mcp"
],
"env": {
"ZUCKERBOT_API_KEY": "<ZUCKERBOT_API_KEY>"
}
}
}
}Replace <…> with your own values
1Platform CLI: remote server
gemini mcp add -t http zuckerbot-meta-ads-mcp-server https://zuckerbot.ai/api/mcp2Platform CLI
gemini mcp add -e ZUCKERBOT_API_KEY=<ZUCKERBOT_API_KEY> zuckerbot-meta-ads-mcp-server npx -y zuckerbot-mcpReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about ZuckerBot — Meta Ads MCP Server
How do I install ZuckerBot in Claude Code?
Remote, in one command: claude mcp add --transport http zuckerbot https://zuckerbot.ai/api/mcp. For a local run: claude mcp add --env ZUCKERBOT_API_KEY=<ZUCKERBOT_API_KEY> --transport stdio zuckerbot-meta-ads-mcp-server -- npx -y zuckerbot-mcp.
What does ZuckerBot do?
It hands your agent Meta Ads tooling: account audits, campaign creation and launch, audience work, creative analysis and CAPI tracking. Everything is driven from the conversation, with no separate dashboard.
What do I need before launching a campaign?
A ZUCKERBOT_API_KEY, a connected ad account and a chosen Facebook page. The get_launch_credentials tool checks readiness ahead of time.
