Apple Ads MCP
Related Servers
Alternatives to Apple Ads MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceGives MCP clients read-only access to every GET endpoint of Apple's Campaign Management v5 and Apple Ads Platform v1 APIs across multiple ad accounts, over stdio or Streamable HTTP. It exposes one tool per endpoint with per-account OAuth handling, pagination, and structured errors, while excluding all mutation and POST-only reporting endpoints.94 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP clients to read and analyze Pinterest advertising data, with optional guarded write tools that preview changes before applying them, all while keeping your token on your own machine and protecting lead records.26374 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to report on App Store and Apple Maps campaigns, explore search terms and keyword ideas, and adjust budgets, bids, keywords and ads through the Platform API, with dry-run previews, confirmation guards and an audit log.MIT
- AlicenseAqualityBmaintenanceExtends the official Google Ads MCP with a safe write layer for creating paused-by-default Search campaigns and an account auditor, all running locally with no hosted dependencies.131Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables searching an offline catalog of Apple Ads Platform API documentation and issuing authenticated read and write calls to manage App Store and Apple Maps campaigns, reports, keywords, budgets, and recommendations. Read and write are split into separate tools, with read-only mode, pagination merging, and large-report file output.93 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to report on and manage Ads Manager campaigns, creative sets, assets, and MAX ad units, waterfalls, experiments, and revenue data, with dry-run, confirmation, and audit-log safeguards for writes.42MIT
TDQS
Scored across 110 tools
With 110 tools, many near-identical variants exist across resources, such as pause/resume/update/delete previews for campaigns, ad groups, ads, keywords, and negatives. Audit, planning, query, and reporting tools like campaign_audit, optimization_plan, optimization_plan_preview, and account_health have boundaries that are only clear after reading long descriptions, creating real misselection risk.
Tool names are overwhelmingly snake_case and follow predictable resource_action or action_preview patterns. There are minor inconsistencies in singular/plural resource naming, e.g. campaign_get vs campaigns_query and app_get-style patterns vs apps_get/apps_search, plus a few noun-first names like account_health and server_info, but the convention remains readable.
A 110-tool surface is an extreme mismatch for a coherent MCP toolset and far exceeds the 3-15 range where tools can be reliably selected. Many operations are near-duplicate previews or resource-specific variants that could be consolidated through generic resource/action tools or namespacing.
The surface covers the Apple Ads domain broadly: campaigns, ad groups, ads, keywords, negative keywords, creatives, shared budgets, product pages, apps, geo/eligibility, reports, recommendations, change history, auth, and optimization workflows. Mutation paths are consistently modeled through preview receipts plus apply/verify, leaving few obvious dead ends.