AdButler MCP Server
OfficialRelated Servers
Alternatives to AdButler MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to create, analyze, and optimize ad campaigns across Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Amazon Ads, and ChatGPT Ads through natural language using 400+ tools.93MIT
- AlicenseAqualityFmaintenanceEnables AI assistants to manage Google Ad Manager campaigns, line items, creatives, and advertisers through natural language, automating ad operations that normally require countless clicks through the UI.3518MIT
- AlicenseBqualityDmaintenanceIntegrates PropellerAds' programmatic advertising platform with AI to automate campaign management, real-time optimization, and performance analysis. It enables users to create, scale, and manage ad campaigns through natural language commands for tasks like bid adjustment and zone blacklisting.213MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with the Amazon Advertising API to manage campaigns, keywords, product ads, and retrieve performance metrics.934 npm3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage TikTok advertising campaigns through the TikTok Ads API. Supports campaign creation, performance analytics, audience management, creative operations, and custom reporting through natural language interactions.49MIT

PaidSync MCP Serverofficial
AlicenseNot gradedqualityFmaintenanceConnects Google Ads, Meta Ads, and LinkedIn Ads to AI assistants, enabling natural language ad campaign management, reporting, and optimization across platforms.MIT
TDQS
Scored across 622 tools
With 622 tools, substantial overlaps are unavoidable: serve_ad/get_ad do the same thing via different HTTP verbs, vast_* and vast42_* duplicate nearly the same object hierarchy, and list_all_campaigns/list_campaigns or get_report_schedule_generated/get_report_generated create real misselection risk. The generic search/describe/call_adbutler_api tools also blur the boundary with every wrapped endpoint.
The dominant verb_noun snake_case pattern (list_, get_, create_, update_, delete_, archive_) is consistent and readable across most resources. However, there are notable deviations like vast42_list_linears vs vast_list_linear_media, serve_ad, convert_native_to_image, and get_contact_report_schedules (which is a list), plus odd compound prefixes like campaign_bulk_create_catalog_ad_items.
622 tools is an extreme count that defeats the purpose of an MCP tool surface; an agent cannot practically discover or select from this many operations. The set should be scoped by domain (e.g., core ad serving, VAST, reporting, contracts) or consolidated behind generic API access.
The tool surface is remarkably broad and covers most AdButler domains with CRUD operations, archives, conversion tags, reports, placements, targeting, and contract workflows. Minor gaps exist (e.g., no explicit update/delete for user database/user resources), but the generic call_adbutler_api fallback prevents dead ends.