Apple Ads MCP vs EveryPage
A side-by-side look at the Apple Ads MCP and EveryPage 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 EveryPage for marketing as a local process. 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 EveryPage when
- You need dedicated capabilities in the Marketing domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
EVERYPAGE_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Marketing | Marketing |
| Quality signal | 45/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | APPLE_ADS_ALLOW_DELETES | EVERYPAGE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Apple Ads MCP | View EveryPage |
Tools & capabilities
Apple Ads MCP tools
No tool names declared yet. Check the project README from the listing page.
EveryPage 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"
}
}
}
}
EveryPage
{
"mcpServers": {
"everypage": {
"command": "npx",
"args": [
"-y",
"everypage-mcp"
],
"env": {
"EVERYPAGE_API_KEY": "YOUR_EVERYPAGE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Apple Ads MCP is categorized under Marketing and uses a local stdio subprocess. EveryPage belongs to Marketing and uses a local stdio subprocess. Pick Apple Ads MCP for marketing work and EveryPage 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. EveryPage 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 everypage 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. EveryPage has 43/100 (Fair) with 3 views, 0 installs and 0 GitHub stars.