Marketing
recao.app
Provides competitive intelligence on Apple App Store ads, including search, competitor ad analysis, and go-to-market playbooks.
ENDPOINT 1
https://recao.app/api/mcp
MCP server metadata
- Name
- recao
- Version
- 0.2.0
Recao is the go-to-market layer a solo app founder's agent uses to run growth. The live capability is reading competitors' App Store ads (Apple, 25 EU storefronts) ranked by longevity (how long an ad stays live = the signal it converts), plus GTM playbooks and per-account memory. Start with roadmap_status to find the founder's stage and the playbook to run, or search_app_advertiser to pull a rival's ads. sign_up gets a free API key so memory persists across sessions. Meta and TikTok are next, not live yet.
Known tools 17
search_app_advertiserSearch the Apple Ad Repository for apps or developers advertising on the EU App Store.
Inferred read-onlyget_competitor_adsGet all Apple App Store ads a competitor has run (EU storefronts, up to 1 year back), with creative copy, placements, formats, and an inferred winner analysis: ads sorted by how long they've been running (longevity = the advertiser keeps paying = likely converting).
Inferred read-onlyget_ad_detailsGet full details and locale/creative variations for one specific ad (use adId from get_competitor_ads).
Inferred read-onlyget_playbookGet a Recao GTM playbook: the go-to-market moves a solo app founder's agent runs, wired to the competitor data tools.
Inferred read-onlyupgradeGet the checkout link to upgrade this account to a paid plan (Indie €29/mo: 10 competitors + weekly auto-reports; Pro €79/mo: 25 competitors, new channels first, full API).
Inferred read-onlymemory_indexList this account's company memory, one line per entry (name + description), newest first.
Inferred read-onlymemory_recallRead one memory entry's full body by name (get names from memory_index).
Inferred read-onlymemory_noteWrite (or update) a memory entry on this account: decisions, campaign outcomes, learnings.
Potential side effectsroadmap_statusWhere the founder's agent starts its go-to-market work: diagnose which stage of the Recao Roadmap this account is in (S0 pre-launch to S4 scale), the binding constraint, and the playbook to run.
Inferred read-onlygenerate_avatarGenerate a UGC persona: your agent passes a persona brief (physical look plus vibe of one invented creator), and we return stills of that invented person plus an avatar_id.
Inferred read-onlygenerate_clipsRender UGC video scenes as ad-ready clips, metered per second of video (the estimate shows the exact price before anything renders).
Inferred read-onlyassemble_videoStitch rendered scene clips into one ad-ready MP4 with burned-in subtitles and crossfades.
Inferred read-onlyusageShow this account's metered generation spend this period and its billing position: the usage cap, what has accrued toward it, and whether generation is waiting on a payment.
Potential side effectswhoamiShow the authenticated account (plan, email, verification state), or confirm you're anonymous.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.recao]
url = "https://recao.app/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: recao
Remote MCP URL: https://recao.app/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"recao": {
"url": "https://recao.app/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"recao": {
"type": "http",
"url": "https://recao.app/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "recao",
"transport": "streamable-http",
"url": "https://recao.app/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.