Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Recao is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Rank a competitor's EU App Store ads by longevity. From Apple's official Ad Repository.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http recao-mcp https://recao.app/api/mcp
# 2 — ask your agent for something these tools do
# search_app_advertiser, get_competitor_ads, get_ad_details and 14 more
Recao costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RAAll 1 server
recao.app1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http recao-mcp https://recao.app/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search the Apple Ad Repository for apps or developers advertising on the EU App Store. Returns ids to use with get_competitor_ads. Start here with your competitor's app name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | App or developer name to search for |
| types | string | no | — |
Get 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). Source: official Apple Ad Repository (DSA transparency data).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | number | yes | appId or developerId from search_app_advertiser |
| type | string | no | — |
| countries | array | no | EU country codes to filter (default: all 25). Available: AT,BE,BG,HR,CY,CZ,DK,EE,FI,FR,DE,GR,HU,IE,IT,LV,LU,NL,PL,PT,RO,SK,SI,ES,SE |
| datePreset | string | no | — |
Get full details and locale/creative variations for one specific ad (use adId from get_competitor_ads). Shows every language variant, creative asset URLs, and icon variations. Useful to see how a competitor localizes a winning ad.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| adId | string | yes | — |
| datePreset | string | no | — |
Get a Recao GTM playbook: the go-to-market moves a solo app founder's agent runs, wired to the competitor data tools. Start with 'the-roadmap' (diagnoses the founder's stage and its binding constraint, then routes you to the right playbook). Call with no slug to list all playbooks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | — |
Request a free Recao account for your human. This does NOT create an active account: it registers a PENDING one and emails your human an activation link; nothing works and no terms are accepted until they click it (the human accepts the terms at activation, not you). The API key in the response stays inert until then. Consent stays with the human, so calling this is a request, not a decision made
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | The account owner's email (the human founder's) | |
| app_name | string | no | The user's own app (App Store name), so reports and memory attach to it |
Get 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). Payment happens in the browser. Hand the link to the human.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | yes | — |
List this account's company memory, one line per entry (name + description), newest first. Traverse index-first: scan this, then memory_recall(name) for full bodies. Memory accrues automatically from your competitor scans (exhaust) and from your own memory_note writes.
No parameter schema on file.
Read one memory entry's full body by name (get names from memory_index).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Memory name (kebab-case slug from memory_index) |
Write (or update) a memory entry on this account: decisions, campaign outcomes, learnings. Use a short kebab-case name and a one-line description (that's the index line); details go in body. Your future sessions and Recao's weekly reports read this.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Short kebab-case slug, e.g. 'campaign-tiktok-hooks-june' |
| description | string | yes | One-line summary for the index |
| body | string | yes | Full content (markdown fine) |
Where 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. Reads your scans and memory. Sharpen it: write a memory_note named 'company-stage' with your MRR band and funnel numbers, and this tool will use it.
No parameter schema on file.
Generate 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. The persona brief anchors the same character in generate_clips takes, and the stills are the customer's reference artifact for the creative. Ask for up to 3; the default model returns a single strong base still, imagen and flux
| Parameter | Type | Required | Notes |
|---|---|---|---|
| persona_brief | string | yes | Physical description plus vibe of the invented UGC creator. One person (age, look, styling, setting, energy). |
| count | integer | no | How many stills to request (2 to 3). The default model returns 1 regardless; imagen and flux honor this. |
| model | string | no | Image model. Default seedream-4.0 (lowest cost). |
Render UGC video scenes as ad-ready clips, metered per second of video (the estimate shows the exact price before anything renders). Pass 3 to 6 scenes (5 to 8 seconds each, one action per scene, spoken lines at most 20 words; empty spoken_line for silent characters). Consecutive scenes pack into single TAKES of up to 15 seconds, one generation each. HOW CHARACTER IDENTITY WORKS, read carefully: a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| avatar_id | string | no | Avatar id from generate_avatar (starts with av_). Its persona brief describes the recurring character in text; identity holds within a take only, not across takes. |
| persona | string | no | Alternative to avatar_id: describe the recurring character or the full ensemble (several characters) in words. Same limits: identity holds within a take, not across takes. Ignored when avatar_id is pr |
| reference_image_urls | array | no | Up to 9 https image URLs of products or props to keep on-model in every take. No people in these images. |
| scenes | array | yes | 3 to 6 scenes in order. Adjacent scenes sharing a character land in the same take when their combined length allows it. |
| aspect | string | no | Output aspect ratio |
| model | string | no | seedance-2.0 (default, highest quality) or seedance-2.0-fast (same generation, faster and cheaper). |
| confirm | boolean | no | Set true to start the metered render. Returns a job_id to poll with clips_status. |
Check a generate_clips render job by its job_id. Returns the status (processing, done, or error). When done, returns the finished clip URLs, the model used, and the booked cost in EUR. When it errored, returns the reason. Only jobs on your own account are visible.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The job_id returned by generate_clips with confirm=true |
Stitch rendered scene clips into one ad-ready MP4 with burned-in subtitles and crossfades. Pass 1 to 6 clips in order, each with its mp4 url, its duration in seconds (3 to 12), and an optional subtitle line to burn over that clip. Every clip is scaled and padded to the chosen aspect (9:16 default 1080x1920, 1:1 1080x1080, or 16:9 1920x1080). Optional intro and outro title cards: pass intro/outro a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| clips | array | yes | 1 to 6 clips in playback order |
| aspect | string | no | Output aspect ratio: 9:16 (default, 1080x1920), 1:1 (1080x1080), or 16:9 (1920x1080). |
| intro | object | no | Optional intro title card shown before the clips. |
| outro | object | no | Optional outro title card shown after the clips (e.g. a call to action). |
Check an assemble_video job by its job_id. Returns the status (processing, done, or error). When done, returns the final MP4 url, the aspect, clip count, total duration, and the booked cost in EUR. When it errored, returns the reason. Only jobs on your own account are visible.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| job_id | string | yes | The job_id returned by assemble_video |
Show 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. Use it to report costs back to your human.
No parameter schema on file.
Show the authenticated account (plan, email, verification state), or confirm you're anonymous.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Recao or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Recao can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.