原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Apple Ads MCP

作者:zelentsov-dev版本 0.3.8i★ –i在你的电脑上运行
注册名称io.github.zelentsov-dev/apple-ads-mcp

安装

概览

作者提供的说明(英文原文)

Local Apple Ads research, optimization, and receipt-gated App Store campaign management.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 营销与社交媒体
  • 你需要填写:APPLE_ADS_MCP_CONFIG

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: APPLE_ADS_MCP_CONFIG

你需要

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "apple-ads": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "APPLE_ADS_MCP_CONFIG",
        "ghcr.io/zelentsov-dev/apple-ads-mcp:v0.3.8"
      ],
      "env": {
        "APPLE_ADS_MCP_CONFIG": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add apple-ads --env APPLE_ADS_MCP_CONFIG=your-value -- docker run -i --rm -e APPLE_ADS_MCP_CONFIG ghcr.io/zelentsov-dev/apple-ads-mcp:v0.3.8

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "apple-ads": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "APPLE_ADS_MCP_CONFIG",
        "ghcr.io/zelentsov-dev/apple-ads-mcp:v0.3.8"
      ],
      "env": {
        "APPLE_ADS_MCP_CONFIG": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "apple-ads": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "APPLE_ADS_MCP_CONFIG",
        "ghcr.io/zelentsov-dev/apple-ads-mcp:v0.3.8"
      ],
      "env": {
        "APPLE_ADS_MCP_CONFIG": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • APPLE_ADS_MCP_CONFIG 必填 env
    Path to a mounted Apple Ads MCP accounts configuration file.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 zelentsov-dev 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“营销与社交媒体”中的其他服务器比较i

  • 星标数多于此分类中其他 2966 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2966 个服务器的 73% 更新
  • 基础检查结果等于或优于此分类中其他 2966 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Apple Ads MCP 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:APPLE_ADS_MCP_CONFIG

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.3.8)于12天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它?

同一分类中有:MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

MCP YouTube Transcript

作者:jkawamoto

An MCP server retrieving transcripts of YouTube videos

在你的电脑上运行★ 495MIT9天前更新
安装

Google Analytics MCP

作者:surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

在你的电脑上运行★ 244MIT9天前更新
安装

AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.

在云端运行★ 137MIT10天前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Apple Ads MCP

Apple Ads MCP is a local-first Model Context Protocol server for the Apple Ads Platform API v1. It gives Codex, Claude, and other MCP clients typed tools to research, inspect, and safely operate App Store advertising accounts.

The server is read-only by default. Credentials stay on your machine, every account-scoped call names an explicit profile and ad account, and every mutation requires a preview plus a short-lived single-use receipt.

Apple Ads MCP is independent open-source software. It is not affiliated with, endorsed by, or sponsored by Apple Inc. Apple Ads and App Store are trademarks of Apple Inc.

Quick start

Install the released binary with Homebrew on macOS or Linux:

brew install zelentsov-dev/tap/apple-ads-mcp

apple-ads-mcp version

Create a local read-only profile. The command stores an absolute private-key path; never paste the private key into a chat, issue, log, or repository:

apple-ads-mcp config init

apple-ads-mcp auth doctor --profile production-read-only apple-ads-mcp accounts discover --profile production-read-only

Register the server with an absolute Homebrew path so desktop apps and IDE extensions do not depend on their inherited shell PATH.

Codex:

codex mcp add apple-ads -- "$(brew --prefix)/bin/apple-ads-mcp" serve --stdio

codex mcp list

Claude Code:

claude mcp add --scope user apple-ads -- "$(brew --prefix)/bin/apple-ads-mcp" serve --stdio

claude mcp get apple-ads

Restart an already running desktop app, CLI session, or IDE extension, then start a new conversation. A safe first request is:

Call server_info, then run account_health for my explicit profile, ad account, and app. Do not enable writes.

Other useful read-only starters:

  • “List the apps I can advertise and explain any eligibility gaps.”
  • “Audit my current Apple Ads campaign structure without changing anything.”
  • “Find keyword opportunities and separate Apple evidence from your inferences.”

Current release

v0.3.8 is the current release. It aligns campaign and ad-group bidStrategy.bid schemas and runtime validation with Apple Ads Platform API v1 (TargetCpa on campaigns versus default Max CPT on ad groups), explicitly sends "bid": null when switching a campaign to MANUAL_CPT so Apple clears any prior TargetCpa, and normalizes decimal money strings in operations_verify. See the v0.3.8 release and migration notes.

The v0.3.5 version-final archive naming, formula-scoped trust from v0.3.4, exact-path verification from v0.3.3, and one-command onboarding from v0.3.2 remain intact.

Optimization is never autonomous: the server has no scheduler and never changes spend in the background. A read-only session can build a baseline and plan. Applying a plan still requires every write gate, an active named policy, one receipt, a fresh report and inventory drift check, and item-level verification.

The release supports the four App Store placements exposed by Apple:

  • Search Results
  • Search Tab
  • Today Tab
  • Product Pages

Placement availability still depends on the selected account, app, storefront, creative, and Apple's eligibility response. An unavailable placement is reported as not_eligible; the server does not attempt to bypass Apple validation.

Keywords and negative keywords are Search Results resources. The Platform API rejects explicit Ad resources for Search Results campaigns, so that placement is operated through its campaign, ad group, keywords, and product-page configuration; explicit ads remain eligibility-gated for the other placements. A Default Product Page creative is unique per app and ad account, so operators should query and reuse it instead of attempting to create a duplicate.

What it can do

AreaMain tools
Access and readinessauth_check, ad_accounts_list, ad_account_get, advertiser_resources_list, account_health
Apps and storefrontsapps_search, apps_get, apps_eligibility, app_locale_details, supported_app_languages, app_store_geo_search
Inventorycampaigns_query, ad_groups_query, keywords_query, negative_keywords_query, ads_query, creatives_query, shared_budgets_query, campaign_inventory
Diagnosticsrejection reasons, campaign status reasons, change history, account and campaign audits
Researchkeyword, phrase, category, target-CPA suggestions, search popularity, impression share
Reportstyped campaign, ad-group, ad, keyword, and search-term reports
Campaign operationcreate/update, budget, countries, schedule, pause, and resume previews
Ad-group operationcreate/update, schedule, targeting, Search Match, bid, deprecated CPA cap, pause, and resume previews
Keywordsindividual and bulk targeting/negative keyword create/update, bid, pause, and resume previews
Ads and creativestyped App Store creative and ad create/update, pause, and resume previews
Recommendationsread, apply-preview, and dismiss-preview for daily budget and target CPA
Optimizationnamed local policies, 28-day baselines, learning/active plans, composite preview/apply/verify, and bounded history
Shared budgetstyped LOC-only create/update/assign/unassign previews with private local billing profiles
Lifecycleseparately gated campaign, ad-group, keyword, negative-keyword, ad, creative, and shared-budget delete previews
Verificationoperations_inspect, operations_apply, operations_verify, and direct resource readback

Every list is bounded to 200 items and uses next pagination. Responses include concise text plus MCP structuredContent; raw Apple envelopes and billing contact PII are not exposed.

There is no raw-request tool, account/delegation mutation, automatic scheduler, Apple Maps surface, or legacy Campaign Management API v5 support.

Safety model

A write is possible only when all gates pass:

  1. The Apple API user has a compatible write role.
  2. The server starts with --allow-writes.
  3. The selected profile has allowWrites: true.
  4. A specialized *_preview tool validates the account, app, storefront, placement, currency, and payload.
  5. operations_apply receives the same unexpired receipt.
  6. The affected inventory still matches the state captured during preview.

Preview receipts expire after ten minutes and are single-use for apply. A bounded tombstone preserves the explicit expired state after the full receipt record is pruned. Every mutation receipt binds canonical object scopes for its target IDs and retains exact read fingerprints; creates and parent deletes also bind the affected inventory and bounded cascade scopes. Generic, bulk, delete, recommendation, shared-budget, and optimization verification shapes for overlapping objects therefore cannot dispatch concurrently. Independent ad-group inventories remain parallel. Bulk receipts return item-level applied, failed, or unknown states. One targeting-keyword bulk receipt may contain multiple per-item ad groups while still sending one Apple bulk request. Apple may partially accept a batch; the server never promises rollback. If an optimization apply has an unresolved outcome, a sanitized recovery recipe remains in owner-only local history so operations_verify can reconcile the supplied receipt after a process restart or normal preview eviction.

Independent previews from the same inventory snapshot intentionally drift after the first apply. Put related keyword creates into one bulk preview when they must be applied as a unit; the server does not weaken this fail-closed invariant.

Mutation requests are not retried after a timeout. The result is committed_unverified, or item-level unknown, until operations_verify and direct readback establish the actual state.

Recommendation apply operations require an explicit maximumAmount. The recommendation currency must match the ad account, the proposed amount must stay under the cap, and the recommendation plus promoted campaign are re-read before apply.

An irreversible delete has five additional gates: --allow-deletes, profile allowDeletes: true, session-only APPLE_ADS_ALLOW_DELETES=true, an exact expected object name or keyword text, and a specialized delete receipt. Campaigns and parents must be PAUSED; cascade inventory is bounded and hashed; creatives must have no referencing ads; shared budgets must have no assignments. DELETE is never retried after an ambiguous result.

Release validation

The v0.3.8 release requires the complete compatibility suite, MCP stdio contract tests, unit and HTTP tests, the race detector, static analysis, vulnerability and secret scans, and distribution validation. Cross-platform CI runs on macOS, Linux, and Windows.

This release uses synthetic acceptance in CI; runtime confirmation against live Apple Ads API v1 is a separate owner-controlled gate. On 2026-08-31, the v0.3.6 P2 read-only matrix and a separately authorized PAUSED targeting-keyword bulk fixture with 2 and 28 items passed against Apple Ads API v1. Both aggregate receipts applied and verified every returned keyword ID directly; the campaign and ad group remained PAUSED throughout the write acceptance.

Earlier v0.3.x live acceptance confirmed read-only optimization baselines and plans, PAUSED fixture creation and readback, budget/bid/strategy updates, pause/resume, receipt drift checks, item verification, and deletion of disposable campaigns, ad groups, keywords, and negative keywords. All retained fixtures remained PAUSED with zero spend.

Account-dependent paths have an explicit evidence boundary:

  • Active optimization-plan apply and MAX_CONVERSIONS changes remain automated-test verified for this release. Optimizer recommendations require the existing history minimums; explicit user-requested previews instead show a warning that statistical readiness has not been established, while preserving contract validation and write gates.
  • Shared-budget create/update/assignment/delete remain contract- and HTTP-test verified because the live acceptance account uses PAYG; Apple requires LOC.
  • Default Product Page ad and creative deletion is confirmed as not_eligible because Apple does not allow those resources to be deleted individually.

These boundaries do not weaken the default safety model: unsupported or insufficiently evidenced operations fail closed and never become successful empty responses.

Install

PlatformHomebrewGitHub archiveOCI image
macOS arm64 / amd64Yes.tar.gzLinux container only
Linux arm64 / amd64Yes.tar.gzYes
Windows arm64 / amd64No.zipLinux container only
Homebrew

The official tap installs a checksum-pinned release binary:

brew install zelentsov-dev/tap/apple-ads-mcp

Upgrade later releases with:

brew update

brew upgrade apple-ads-mcp

GitHub release

Download the archive for your platform from GitHub Releases. Releases include SHA-256 checksums and SPDX SBOMs.

Apple silicon example:

curl -LO https://github.com/zelentsov-dev/apple-ads-mcp/releases/download/v0.3.8/apple-ads-mcp_darwin_arm64_0.3.8.tar.gz

curl -LO https://github.com/zelentsov-dev/apple-ads-mcp/releases/download/v0.3.8/checksums.txt

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx