ZuckerBot — Meta Ads MCP Server
NPM · ZUCKERBOT-MCP · 2 COMPONENTS · SCANNED SEP 20
60+ Meta Ads tools for AI agents: audits, campaign management, audiences and CAPI tracking.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 37 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 9145 tokens (~152/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "zuckerbot_delete_audience" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the ZuckerBot — Meta Ads MCP Server server?
ZuckerBot — Meta Ads MCP Server runs locally as an npm package, launched with npx -y zuckerbot-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · zuckerbot-mcp
claude mcp add crumbedsausage-zuckerbot -- npx -y zuckerbot-mcp
{
"mcpServers": {
"crumbedsausage-zuckerbot": {
"command": "npx",
"args": [
"-y",
"zuckerbot-mcp"
]
}
}
} {
"servers": {
"crumbedsausage-zuckerbot": {
"command": "npx",
"args": [
"-y",
"zuckerbot-mcp"
]
}
}
} codex mcp add crumbedsausage-zuckerbot -- npx -y zuckerbot-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"crumbedsausage-zuckerbot": {
"type": "local",
"command": [
"npx",
"-y",
"zuckerbot-mcp"
],
"enabled": true
}
}
} openclaw mcp add crumbedsausage-zuckerbot --command npx --arg -y --arg zuckerbot-mcp
mcp_servers:
crumbedsausage-zuckerbot:
command: "npx"
args: ["-y", "zuckerbot-mcp"] {
"McpServers": {
"crumbedsausage-zuckerbot": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"zuckerbot-mcp"
]
}
}
} assistant mcp add crumbedsausage-zuckerbot -t stdio -c npx -a -y zuckerbot-mcp
{
"mcpServers": {
"crumbedsausage-zuckerbot": {
"command": "npx",
"args": [
"-y",
"zuckerbot-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/zuckerbot-mcp@0.4.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 114 packages
| Packages resolved | 114 |
|---|---|
| Stale | 37 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
zuckerbot_research_reviews ~126
Fetch review intelligence for a business by name. Searches Google and Yelp to surface star rating, review count, recurring sentiment themes, and standout customer quotes that can be used directly in ad copy. Use before creating a campaign to identify proof points and objection-handling angles.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | string | yes | Business name to research reviews for (e.g., 'Rosebud Dental Austin') |
| location | string | – | Optional city/region to narrow review search (e.g., 'Austin, TX') |
| platform | string | – | Review platform to search. Defaults to all. |
No output schema declared.
No examples provided.
zuckerbot_rotate_webhook_secret ~101
Rotate the Conversions API webhook secret for a business. The new secret is returned exactly once, in this response only — every other read shows just webhook_secret_set and webhook_secret_last4. The old secret stops authenticating immediately, so update the system that signs your inbound webhooks (for example your CRM workflow's stored secret) in the same sitting.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | – | Optional business ID override for the authenticated API key |
No output schema declared.
No examples provided.
zuckerbot_send_capi_event ~365
Manually send a Conversions API event for a business contact/lead. Useful for debugging CAPI pipelines, testing stage mappings with real user data, or sending events from custom integrations not covered by the webhook. Authenticates with the business API key OR with an x-zuckerbot-webhook-secret header if using the webhook path.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | – | Optional business ID override (resolved from API key when omitted) |
| crm_source | string | – | Optional CRM source label override (e.g., 'hubspot', 'salesforce') |
| string | – | Optional contact email for identity matching | |
| event_time | string | – | Optional ISO 8601 event timestamp. Defaults to now. |
| fbc | string | – | Optional pre-formatted Facebook click cookie (fb.1.<ms>.<fbclid>), forwarded raw — never hashed |
| fbclid | string | – | Optional Facebook click ID; the server builds a well-formed fbc cookie from it |
| fbp | string | – | Optional Facebook browser ID cookie (_fbp), forwarded raw — never hashed. Improves match quality for every event |
| first_name | string | – | Optional first name for identity matching |
| last_name | string | – | Optional last name for identity matching |
| lead_id | string | – | Optional ZuckerBot lead ID for attribution matching |
| meta_lead_id | string | – | Optional Meta Lead Gen Ads lead ID for attribution matching |
| phone | string | – | Optional contact phone for identity matching |
| source_stage | string | yes | CRM stage key to map to a Meta event (e.g., 'lead', 'salesqualifiedlead', 'customer') |
| value | number | – | Optional event value override in major currency units |
No output schema declared.
No examples provided.
zuckerbot_set_capi_config ~297
Update the Conversions API configuration for a business. Set stage-to-event mappings (e.g., 'lead' → Meta Lead event), enable/disable delivery, change the CRM source, currency, optimisation target, or action source. Changes take effect immediately for new CAPI events. Use zuckerbot_capi_test to verify the updated config works.
| Name | Type | Req | Description |
|---|---|---|---|
| action_source | string | – | Meta Conversions API action_source. Defaults to website for CRM events |
| business_id | string | – | Optional business ID override for the authenticated API key |
| crm_source | string | – | CRM source label, such as hubspot |
| currency | string | – | Business currency used for CAPI event values, such as USD or AUD |
| event_mapping | object | – | CRM stage mapping object keyed by source stage. Stage keys are normalised (lower-cased, non-alphanumerics stripped: signup_completed → signupcompleted); inbound webhook source_stage values are normal… |
| is_enabled | boolean | – | Enable or disable CAPI delivery for the business |
| optimise_for | string | – | Downstream optimisation target for autonomous evaluation |
| rotate_webhook_secret | boolean | – | Rotate the webhook secret on update. The new secret is returned exactly once in the response; prefer zuckerbot_rotate_webhook_secret for a dedicated rotation |
No output schema declared.
No examples provided.
zuckerbot_suggest_angles ~65
Return only the creative angles and audience tiers for a campaign draft — a lightweight alternative to zuckerbot_get_campaign when you need just the strategy summary without the full campaign payload, stored creatives, or tier execution details.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Campaign ID |
No output schema declared.
No examples provided.
zuckerbot_sync_conversion ~238
Send downstream conversion quality feedback to Meta via CAPI. When a ZuckerBot-sourced lead converts (sale, appointment, qualified call) or bounces (uncontactable, bad fit), reporting it here teaches Meta's algorithm to find more (or fewer) people like them — improving lead quality over time. Call this from your CRM when a lead status changes.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | ZuckerBot campaign ID |
| fbc | string | – | Optional pre-formatted fbc cookie, forwarded raw — never hashed |
| fbclid | string | – | Optional Facebook click ID; the server builds a well-formed fbc cookie from it |
| fbp | string | – | Optional _fbp browser cookie, forwarded raw — never hashed. Improves match quality |
| lead_id | string | yes | Lead ID to report conversion for |
| meta_access_token | string | yes | User's Meta access token for CAPI |
| quality | string | yes | Lead quality: 'good' = converted/contacted, 'bad' = lost/unresponsive |
| user_data | object | – | Optional user data to improve match rate |
No output schema declared.
No examples provided.
zuckerbot_tag_creative ~114
Tag Meta ads with creative attributes (hook type, visual style, product focus, CTA type, copy tone, setting) by providing ad metadata and optional asset URLs. ZuckerBot uses Claude vision to analyze the creative and store structured tags. These tags feed the zuckerbot_creative_analysis pipeline. Run this after launching new ads to keep the creative intelligence database current.
| Name | Type | Req | Description |
|---|---|---|---|
| ads | array | yes | One or more Meta ads to tag with creative attributes |
| business_id | string | – | Optional business ID override |
No output schema declared.
No examples provided.
zuckerbot_update_portfolio ~136
Update the name, total daily budget, active status, or tier configuration of an existing audience portfolio. Changes to budget and tiers take effect on the next autonomous evaluation cycle. Use this to adjust a portfolio without relaunching all tiers.
| Name | Type | Req | Description |
|---|---|---|---|
| is_active | boolean | – | Enable or disable the portfolio for autonomous evaluation |
| name | string | – | New portfolio name |
| portfolio_id | string | yes | Audience portfolio ID to update |
| tiers | array | – | Updated tier configuration. Replaces the existing tiers array. |
| total_daily_budget_cents | integer | – | New total daily budget in cents (minimum 500) |
No output schema declared.
No examples provided.
zuckerbot_upload_business_context ~125
Upload a text document (ad performance data, brand guidelines, customer data, sales data, or competitor analysis) so ZuckerBot can extract structured planning insights from it. Accepts raw text content — not binary files. Use this when the business has existing performance data or brand docs that should inform campaign strategy.
| Name | Type | Req | Description |
|---|---|---|---|
| business_id | string | – | Optional business ID override |
| content | string | yes | File content as text |
| context_type | string | – | Optional hint about the type of uploaded context |
| filename | string | yes | Name of the file or document |
No output schema declared.
No examples provided.
zuckerbot_upload_creative ~139
Upload finished creative assets (images or videos) to an approved intelligence campaign. ZuckerBot queues the Meta upload and ad-creation jobs asynchronously, then polls until they complete or the polling window expires. Use this when you have your own creative assets ready.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_id | string | yes | Intelligence campaign ID |
| creatives | array | yes | Creative assets to attach to the campaign |
| meta_access_token | string | – | Optional Meta/Facebook access token override |
| meta_ad_account_id | string | – | Optional Meta ad account ID override (format: act_XXXXX) |
| meta_page_id | string | – | Optional Facebook Page ID override |
No output schema declared.
No examples provided.
What is the ZuckerBot — Meta Ads MCP Server server?
ZuckerBot — Meta Ads MCP Server is listed in the public MCP registry as io.github.Crumbedsausage/zuckerbot. 60+ Meta Ads tools for AI agents: audits, campaign management, audiences and CAPI tracking. This page covers its npm package (zuckerbot-mcp).
Is the ZuckerBot — Meta Ads MCP Server server safe to use?
ZuckerBot — Meta Ads MCP Server scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ZuckerBot — Meta Ads MCP Server server expose?
ZuckerBot — Meta Ads MCP Server exposes 60 tools: zuckerbot_quickstart, zuckerbot_billing_status, zuckerbot_audit_account, zuckerbot_redeem_license, zuckerbot_analyse_account_history, and 55 more. Their descriptions and schemas cost roughly 9,145 tokens of context every time the server is loaded.
Is the ZuckerBot — Meta Ads MCP Server server still maintained?
ZuckerBot — Meta Ads MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the ZuckerBot — Meta Ads MCP Server server under?
ZuckerBot — Meta Ads MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.