Apple Ads MCP vs GrowSurf

A side-by-side look at the Apple Ads MCP and GrowSurf MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Apple Ads MCP logoApple Ads MCPMarketing · Local subprocess (stdio)Local Apple Ads research, reports, and receipt-gated campaign management.45FairAuth: not declaredGrowSurf logoGrowSurfMarketing · Local subprocess (stdio)Build and manage GrowSurf referral and affiliate programs through AI assistants.61GoodAuth: not declared

Verdict: choose Apple Ads MCP for marketing work as a local process; choose GrowSurf for marketing as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Apple Ads MCP logoChoose Apple Ads MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: APPLE_ADS_ALLOW_DELETES.
Explore Apple Ads MCP

GrowSurf logoChoose GrowSurf when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: GROWSURF_API_KEY, GROWSURF_CAMPAIGN_ID.
  • You want tools like growsurf_integration_guide, growsurf_agent_program_creation_eval, growsurf_program_design_advisor.
Explore GrowSurf

Feature & specification comparison

Rows where the two servers differ are marked.

SpecApple Ads MCP logoApple Ads MCPGrowSurf logoGrowSurf
CategoryMarketingMarketing
Quality signal45/100 · Fair61/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsAPPLE_ADS_ALLOW_DELETESGROWSURF_API_KEYGROWSURF_CAMPAIGN_ID
Verified ownerCommunity listingCommunity listing
GitHub stars60
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listed63

Tools & capabilities

Apple Ads MCP tools

No tool names declared yet. Check the project README from the listing page.

GrowSurf tools 63

  • growsurf_integration_guidePlan a web integration for a referral or affiliate program. Returns Markdown steps for installing the Universal Code, identifying participants, tracking referrals or sales, and verifying webhooks. Does not inspect or change a program. Use `growsurf_client_snippets` for browser JavaScript examples, `growsurf_api_library_snippets` for backend code, or `growsurf_mobile_sdk_guide` for native or React Native apps.
  • growsurf_agent_program_creation_evalGenerate Markdown prompts and acceptance checks for evaluating an agent's program-creation workflow: starter content, rewards, configuration, and frontend installation. Does not create a program or run the checks. Use `growsurf_program_design_advisor` to choose a program design, or `growsurf_integration_guide` to plan its web integration.
  • growsurf_program_design_advisorGenerate program designs, benchmarks, typical rewards, and metric definitions, including participant-to-referral and lead-to-referral ratios. Read-only. Returns a short draft, complete `benchmarkFacts`, a proposed `configurationPlan`, and unresolved `decisions`. Incentive amounts and qualifying actions remain unresolved unless supplied by the customer. `detail: summary` returns a configuration draft and reward structure; `detail: full` adds detailed benchmark tables. Hosted figures describe GrowSurf's high-performing programs; without a bundle, guidance is documentation-based. `programType: AFFILIATE` selects affiliate advice. `industry: other` covers local services, pets, hospitality, and agencies. All inputs are optional.
  • growsurf_troubleshoot_referral_trackingDiagnose referral tracking and program problems. Accepts a symptom or description without requiring a program or participant ID. Covers referrals not credited, participant emails not sending, rewards not issued, participants not added, Universal Code not detected, integrations or CRMs not syncing, Zapier errors, fraud flags, and analytics discrepancies. Returns ordered diagnostic checks, likely causes, fixes, and documentation links. It does not read program or participant records. Unknown `symptom` keys return the available symptoms. A `description` matches only when it contains a symptom label or alias verbatim; otherwise the symptom list is returned.
  • growsurf_mobile_sdk_guideGet Markdown implementation guidance for native iOS/Android SDK 0.9.0 or React Native SDK 0.1.0, including attribution, `shareUrl` sharing, `trackShare`, and the native GrowSurf Window. Choose `platform` and `participantState` to tailor the guide; `includeInstallSnippets` controls installation examples. Does not install an SDK or create a participant token. Use `growsurf_client_snippets` for browser JavaScript or `growsurf_api_library_snippets` for backend token-creation code.
  • growsurf_api_library_snippetsGenerate Markdown code examples for the official backend REST API libraries in TypeScript, Python, PHP, Ruby, and Java. Select `language` and `workflow`; both default to `all`. Covers setup, program lookup, participant creation, referral credit, sales, and mobile participant tokens. Returns code without executing API calls. Use `growsurf_client_snippets` for browser JavaScript or `growsurf_mobile_sdk_guide` for native or React Native app setup.
  • growsurf_get_campaignFetch your GrowSurf campaign (program) details via REST. Embedded reward settings do not establish that an individual reward was earned, approved, or delivered. Earned reward records belong to the individual participant. Targets `campaignId` if supplied, otherwise `GROWSURF_CAMPAIGN_ID`.
  • growsurf_list_campaignsList the GrowSurf programs available to the bound team, including their IDs for program selection. Deleted programs are not returned. Does not require `GROWSURF_CAMPAIGN_ID`.
  • growsurf_create_campaignCreate a new GrowSurf program (campaign) with type-appropriate starter content and optional inline rewards. Starter content includes Design, Emails, Options, Installation, and GrowSurf Window defaults. Only `type` is required. The program starts in `DRAFT` status and is owned by the credential's bound team. `currencyISO` defaults to `USD` and is immutable after creation. `goal` sets the sharing settings at creation and cannot be set later. Incentives require the customer's chosen amount or commission rate. Without `rewards`, GrowSurf's starter rewards are switched off and award nothing. Editor-tab configuration is not accepted here. Does not require `GROWSURF_CAMPAIGN_ID`. The response includes the new program `id`.
  • growsurf_update_campaignUpdate your GrowSurf program's (campaign's) identity and lifecycle: name, companyName, companyLogoImageUrl, and status (set IN_PROGRESS to publish/resume the program, COMPLETE to end it). Only the fields you send are changed. `type`, `urlId`, and `currencyISO` are immutable (currency is chosen once at program creation), so this tool does not accept them. Editor-tab config (design, emails, options, installation) is edited with the dedicated config sub-resource tools, not here. Targets `campaignId` if you pass it, otherwise GROWSURF_CAMPAIGN_ID.
  • growsurf_clone_campaignClone your GrowSurf program (campaign) into a new DRAFT program. Integrations and credentials are not copied; active rewards are cloned. Targets `campaignId` if you pass it, otherwise GROWSURF_CAMPAIGN_ID.
  • growsurf_list_campaign_rewardsList your GrowSurf program's configured Campaign Rewards, including switched-off rewards and rewards whose group is not selected. Deleted rewards are excluded. A reward can be earned only when it also appears in the campaign response's embedded `rewards` array. These settings do not establish that a participant earned or received a reward; earned reward records belong to the individual participant. Targets `campaignId` if supplied, otherwise `GROWSURF_CAMPAIGN_ID`.
  • +51 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Apple Ads MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "apple-ads-mcp": {
      "command": "npx",
      "args": [
        "--yes",
        "markdownlint-cli2@0.23.2"
      ],
      "env": {
        "APPLE_ADS_ALLOW_DELETES": "YOUR_APPLE_ADS_ALLOW_DELETES_HERE"
      }
    }
  }
}

GrowSurf

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "growsurf": {
      "command": "npx",
      "args": [
        "-y",
        "@growsurfteam/growsurf-mcp"
      ],
      "env": {
        "GROWSURF_API_KEY": "YOUR_GROWSURF_API_KEY_HERE",
        "GROWSURF_CAMPAIGN_ID": "YOUR_GROWSURF_CAMPAIGN_ID_HERE"
      }
    }
  }
}

Frequently asked questions

Apple Ads MCP is categorized under Marketing and uses a local stdio subprocess. GrowSurf belongs to Marketing and uses a local stdio subprocess. Pick Apple Ads MCP for marketing work and GrowSurf for marketing.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Apple Ads MCP has no declared pricing — check the project's own site. GrowSurf has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add apple-ads-mcp and growsurf as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Apple Ads MCP has a quality signal of 45/100 (Fair) with 1 views, 0 installs and 6 GitHub stars. GrowSurf has 61/100 (Good) with 2 views, 0 installs and 0 GitHub stars.