A side-by-side look at the Ad Spy and AdCrunch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ad Spy for social media work; choose AdCrunch for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
list_advertisers, list_campaigns, list_ad_groups.Rows where the two servers differ are marked.
| Spec | A Ad Spy | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 39/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Freemium | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Ad Spy | View AdCrunch |
No tool names declared yet. Check the project README from the listing page.
list_advertisersConnected ad accounts across platformslist_campaignsCampaigns for an advertiserlist_ad_groupsAd-group structurelist_adsIndividual adsquery_insightsTime-series performance: spend, ROAS, CPA, impressions, clicks, conversionssearch_adsSearch ad creativeskill_listDiscover and fetch your org's reusable ad-ops playbooksskill_createAuthor and maintain playbooks (Skills store)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.
No confirmed install command for Ad Spy yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"adcrunch": {
"url": "https://mcp.adcrunch.dev/mcp"
}
}
}