Support & FAQ

• Your licence code from your Dealify purchase (format ZB-XXXXX-XXXXX-XXXXX).
• An email address — sign-in uses one-time email codes, no password.
• A Meta ad account you can access through Facebook Business Manager, with a Facebook Page.
• An MCP-capable AI agent — claude.ai, Claude Desktop, Claude Code, Cursor, or any other MCP client.

Setup takes about 5 minutes at zuckerbot.ai/start.html.

Go to zuckerbot.ai/start.html and follow the four steps:

1. Sign in with your email (we send a one-time code).
2. Redeem your ZB-… licence code.
3. Mint your API key (shown once — store it safely).
4. Connect Meta via Facebook login or a System User token.

• Invalid format: codes look like ZB-XXXXX-XXXXX-XXXXX. The alphabet deliberately excludes easily-confused characters (0/O, 1/I/L) — re-check any you typed.
• Code doesn't exist: copy-paste it directly from your Dealify receipt rather than retyping.
• Already redeemed: each code is single-use. If you redeemed it yourself under a different email, sign in with that email instead. If you never redeemed it, contact us with the code and your purchase receipt.

Redeem each code while signed in to the same account at start.html. Your tier upgrades automatically: 1 code = Tier 1, 2 codes = Tier 2, 3 codes = Tier 3 (the maximum). Your existing API key keeps working and picks up the higher limits — no need to reconnect anything.

Keys are shown once at creation and never again. If you lose yours, sign back in at start.html and mint a new key from step 3 — your licence tier carries over to every key on your account. Store it in a password manager.

1. In claude.ai, open Settings → Connectors → Add custom connector.
2. Enter the URL: https://zuckerbot.ai/api/mcp
3. When prompted, sign in with your email — use the same email you redeemed your licence with.

That's it — no API key needed; the sign-in links the connector to your licence.

Honest answer: we haven't certified ZuckerBot against ChatGPT yet, so we're not going to hand you steps we can't stand behind.

ChatGPT can reach remote MCP servers, and our endpoint is a standards-compliant remote MCP server — nothing about it is Claude-specific. But which ChatGPT plans expose custom connectors, and whether they allow tools that act rather than just read, has moved around. ZuckerBot is also a large toolkit, and some clients cap how much tool definition they'll accept.

If you want to try it, the connector URL is https://zuckerbot.ai/api/mcp and you sign in with the email you redeemed your licence with. Please tell us how it goes — email support@zuckerbot.ai either way, and we'll write this section properly.

Two paths that definitely work today: the claude.ai connector above, and npx zuckerbot-mcp with a key from start.html in any local MCP client. And note the connector is one credential per account — see "My old connector stopped working" below before running two agents at once.

With your API key from start.html:

claude mcp add zuckerbot --env ZUCKERBOT_API_KEY=zb_live_… -- npx -y zuckerbot-mcp

Or add to your MCP config file manually:

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

Two options:

• Remote: add https://zuckerbot.ai/api/mcp as a remote MCP server. Sign in via the OAuth prompt, or send the header Authorization: Bearer zb_live_… directly.
• Local: use the npx -y zuckerbot-mcp config above with ZUCKERBOT_API_KEY set.

Remote (https://zuckerbot.ai/api/mcp) needs no install and signs in with your email — best for claude.ai and quick setup. Local (npx zuckerbot-mcp) runs on your machine and authenticates with your API key — best for Claude Code, scripts, and anywhere you manage env vars. Both expose the same tools and count against the same limits.

Check spam/junk first. Codes are valid for a short window — if it expired, request a fresh one. If emails consistently don't arrive, contact us and include the email address you're using.

That's by design. Each time you complete the connector sign-in, ZuckerBot issues a fresh connector credential and revokes the previous one. Note this is one connector credential per account, across every client — not one per device. So signing in the connector from a second app disconnects the first: connect ChatGPT and your claude.ai connector stops working, and vice versa.

To run two agents at once, keep one of them on the connector and give the other a key you mint yourself at start.html — self-minted keys are never revoked by a reconnect. If one of them is a web-only client like ChatGPT, keep that one on the connector and move the local client (Claude Desktop, Claude Code, Cursor) onto npx zuckerbot-mcp with your own key.

• Facebook login (recommended): click through the Facebook OAuth flow at start.html step 4. Fastest, but Meta login tokens expire after about 60 days, so you'll occasionally reconnect.
• System User token (advanced): create a System User in Business Manager → System Users, assign it your Page and ad account, and generate a token that never expires. Best if you want set-and-forget.

If tools start returning a Meta authentication error (Meta error code 190), your login token has expired. Sign in at start.html and redo step 4 — takes under a minute. To stop this happening, switch to a System User token, which never expires.

You've pasted a Page access token. ZuckerBot needs a User or System User token — generate it from the System User itself in Business Manager (not from a Page), with the ad permissions assigned.

Facebook connect links are valid for 10 minutes. If you left the tab open too long, just start the connection again from step 4.

It depends on your tier: 1 ad account on Tier 1, 3 on Tier 2, 10 on Tier 3. An ad account is registered to your licence the first time your agent works with it (e.g. the first audit). If you hit your cap, redeem another code to move up a tier.

	Tier 1 (1 code)	Tier 2 (2 codes)	Tier 3 (3 codes)
Ad accounts	1	3	10
API calls / month	2,500	10,000	30,000
Rate limit	30/min	60/min	120/min

All tiers get the full tool set. Limits are per account (not per key) and reset monthly.

Each tool invocation your agent makes is one call. A simple question might be a single call; a full account audit or campaign build involves several. For reference, 2,500 calls/month is comfortable for regularly managing one ad account.

Requests are declined with a clear error (HTTP 429) until the month rolls over — there is no overage billing, ever. The cap is a hard stop, not a surprise bill. The per-minute rate limit behaves the same way: a 429 with a retry_after your agent waits on. If you're hitting either regularly, stack another code for a higher tier.

Ask your agent: "What's my ZuckerBot billing status?" — the zuckerbot_billing_status tool returns your tier, calls used this month, and remaining quota.

No. Generating creatives has real per-render costs, so it's excluded from the lifetime deal to keep the deal sustainable — it may arrive later as an optional paid add-on. Creative analysis is included: your agent can analyse, compare, QA, and tag the ad creatives you already have, and tell you what's working.

No. Campaigns and ads are provisioned in a PAUSED state — nothing runs and nothing spends until you explicitly approve and request the supported legacy launch. Campaign builds also go through a preview/approve step, so you (and your agent) see the full plan — budget included — before delivery begins.

Audits, insights, and research tools are read-only. Management tools can create, launch, and pause supported campaigns on the ad accounts you've connected — the same permissions you granted via Facebook login or your System User token. ZuckerBot only ever acts on your instruction through your agent.

Encrypted at rest with AES-256-GCM. Your token is decrypted server-side only at the moment it's needed to call the Meta API, and is never exposed to the browser or to other tenants. Full detail on the security page.

Honest answer: ZuckerBot runs on Meta's Marketing API, so like every tool in this category it depends on Meta keeping that API available. If we ever wound the service down, we'd give reasonable notice by email, and you can export or delete your data at any time by emailing support@zuckerbot.ai. Your Meta account and its data always remain yours, held in your own Meta Business Manager — ZuckerBot only ever acts on it with your access.

You've hit your per-minute limit (30/60/120 depending on tier). The error includes a retry_after — most agents wait and retry automatically. If your agent runs big parallel workloads, a higher tier raises the ceiling.

You've used your month's calls. The counter resets at the start of the next month, or redeem another licence code to move up a tier immediately.

A skip response tells you the exact reason rather than pretending success:

• missing_meta_credentials — connect your Meta account first (start.html step 4).
• capi_disabled / missing pixel — set your pixel in the CAPI config (ask your agent to run zuckerbot_set_capi_config).

Ask your agent for zuckerbot_capi_status — it shows readiness, recent events, and any recent failures with reasons.

Three possibilities, in order of likelihood:

• Meta token expired (error 190) → reconnect Meta at start.html.
• Connector key rotated — you reconnected the connector elsewhere, which revoked the old session → reconnect this client.
• Wrong or truncated API key in a local config → re-check the ZUCKERBOT_API_KEY value.

Email us with: what you asked your agent to do, the error message (tool errors include a code field), the approximate time, and the last 4 characters of your API key. We can trace exactly what happened.

Lifetime-deal purchases are covered by Dealify's money-back guarantee — refunds are requested and processed through Dealify, per the terms on the listing where you bought. Once refunded, the associated licence codes are deactivated.

Licences are bound to the account that redeemed them. If you need to move to a different email, contact us from the original address and we'll sort it out.

Email us from your account email and we'll remove your account, keys, Meta connection, and stored data. See the Privacy Policy for details on what we store.