This is the AdvertZip Model Context Protocol server. Connect Claude, Cursor or any MCP client and let it manage your publisher sites, ad zones, mobile apps and advertiser campaigns — with hard safety limits.
https://mcp.advertzip.com/mcp
Prefer a token? Put an AdvertZip AI session key (az_ai_…) or API key (xbl_…) — from console → AI access — in your client config:
{
"mcpServers": {
"advertzip": {
"url": "https://mcp.advertzip.com/mcp",
"headers": { "Authorization": "Bearer az_ai_…" }
}
}
}
create_site · create_sites_bulkverify_site (meta-tag ownership check)create_zone · create_zones_bulkget_zone_embed_codecreate_app · create_ad_unitcreate_campaign · create_ad_groupcreate_creative · set_campaign_targetingset_campaign_statusget_campaign_stats · get_account_statswhoami · get_catalog (+ list/update_*)advertzip_trash_zones_bulk · advertzip_restore_zones_bulkadvertzip_list_trash · advertzip_get_trash_batch46 tools in total. Access is scoped — on the consent screen you choose whether the agent may only read, provision publisher resources, and/or manage campaigns. Two guided prompts (monetize-website, launch-campaign) walk agents through the full flows.
There is no tool that erases anything. Removing a zone or site moves it to a trash bin: it stops serving immediately, disappears from the normal listings, and keeps its id, configuration and statistics for 30 days, after which an internal worker purges it. You can restore it at any point from console → Trash.
Every destructive call is two-phase: the agent must first preview
(dry_run) — which returns the exact list plus a single-use token valid ~10 minutes — and only then execute
with that token. If anything changed in between, the call is refused. The trash permission is its own
checkbox on the consent screen, so an agent only gets it if you grant it.