Apple Ads MCP vs RouterGrowth
A side-by-side look at the Apple Ads MCP and RouterGrowth MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Apple Ads MCP for marketing work as a local process; choose RouterGrowth for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose 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.
Choose RouterGrowth when
- You need dedicated capabilities in the Marketing domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 45/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Paid service |
| Required env vars | APPLE_ADS_ALLOW_DELETES | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | — |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Apple Ads MCP | View RouterGrowth |
Tools & capabilities
Apple Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
RouterGrowth tools
No tool names declared yet. Check the project README from 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": {
"apple-ads-mcp": {
"command": "npx",
"args": [
"--yes",
"markdownlint-cli2@0.23.2"
],
"env": {
"APPLE_ADS_ALLOW_DELETES": "YOUR_APPLE_ADS_ALLOW_DELETES_HERE"
}
}
}
}
RouterGrowth
{
"mcpServers": {
"routergrowth": {
"url": "https://api.routergrowth.com/mcp"
}
}
}
Frequently asked questions
Apple Ads MCP is categorized under Marketing and uses a local stdio subprocess. RouterGrowth belongs to Marketing and uses a remote HTTP/SSE transport. Pick Apple Ads MCP for marketing work and RouterGrowth 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. RouterGrowth is listed as a paid service. Auth: oauth 2.0. 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 routergrowth 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. RouterGrowth has 47/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.