In-depth architectural comparison of the Aapl Ads MCP and Recao MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Aapl Ads MCP
Marketing · Local stdio
Quality: 41/100 (Fair) | Auth: other
Recao
Marketing · Remote HTTP/SSE
Quality: 48/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Aapl Ads MCP if you need specialized Marketing tools running via a local process. Choose Recao if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Aapl Ads MCP when:
You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: ASA_CLIENT_ID, ASA_TEAM_ID, ASA_KEY_ID, ASA_ORG_ID, ASA_PRIVATE_KEY_PATH, ASA_PRIVATE_KEY.
Primary tools included: Read-only Apple Search Ads API v5 queries, Campaign, ad group, and keyword listings, Campaign, ad group, and keyword performance reports.
Aapl Ads MCP is categorized under Marketing and uses a local stdio subprocess. In contrast, Recao belongs to Marketing using remote streaming HTTP/SSE transport. Select Aapl Ads MCP when you need capabilities focused on marketing and Recao when you require tools for marketing.
Pull every App Store ad an advertiser ran in the EU (up to 1 year back), sorted by how long each has been live. An ad the advertiser keeps paying for is the closest public signal that it converts.
get_ad_details
Full detail for one ad: every locale variant, creative asset URLs, icon variations, placements, and date range. Shows how a competitor localizes a winning ad.
get_playbook
An Apple Search Ads playbook for indie apps, wired to the data tools. Call with no argument to list the available playbooks.