Recao MCP server
{
"mcpServers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}{
"mcpServers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}{
"mcpServers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}{
"servers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}{
"mcpServers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
Recao exposes Apple's official EU App Store Ad Repository through MCP, letting you search for competitors' ads and rank them by how long they've stayed live. It's for app developers who want to see what creative copy and placements their competitors are actually paying to run.
- Search for a competitor's app and retrieve all their active EU App Store ads sorted by longevity to identify which creatives are performing well enough to stay funded.
- Inspect full details of a specific ad including locale variants, creative assets, placements, and date ranges to understand how competitors localize winning campaigns.
- Query Apple Search Ads playbooks for indie apps that are informed by real competitor ad data from the repository.
Tools this server exposes
| Tool | Does |
|---|---|
| search_app_advertiser | Find an app or developer in Apple's Ad Repository by name and return their IDs for use with other tools. |
| get_competitor_ads | Retrieve all App Store ads an advertiser has run in the EU over the past year, sorted by longevity to show which creatives have stayed live longest. |
| get_ad_details | Fetch complete details for a single ad including every locale variant, creative asset URLs, icon variations, placements, and date ranges. |
| get_playbook | Retrieve Apple Search Ads playbooks for indie apps, populated with live ad repository data. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.