Google Search Console integration for Model Context Protocol (MCP)
Run1Ads: live Meta ads consultant 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.
What it does
Live Meta ads consultant for e-commerce. Checks ads, Pixel and store hourly, then gives the one fix.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http run1ads-live-meta-ads-consultant-mcp https://run1ads.ai/mcp/rpc
# 2 — ask your agent for something these tools do
# list_brands, get_today, get_performance and 12 more
Run1Ads: live Meta ads consultant costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 run1ads-live-meta-ads-consultant-mcp https://run1ads.ai/mcp/rpcReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
15 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.
List the brands you can open in Run1Ads, with their brand id and whether Meta is connected. Start here if you manage more than one brand. Read only.
No parameter schema on file.
Get today's brief for a brand: the one fix to do first, the other findings ranked by how many buyers they cost, what changed, what is working, and the live check status. Every finding has the number behind it and exact steps. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get the brand's saved Meta ads results (spend, revenue, ROAS, purchases, click rate, cost per click, frequency) and this month's ROAS goal with the gap to it. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get the sales funnel from ad click to purchase. Each step shows how many in 1,000 move on, the benchmark per 1,000, whether it is above or below, the trend, and which step loses the most buyers. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get the hourly live check: when it last ran, today so far, open alerts (critical first) and alerts resolved in the last 7 days. Each alert says why it matters and how to fix it. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| include_resolved | boolean | no | Include alerts resolved in the last 7 days. |
Get the latest store checks: does the store work inside the Instagram and Facebook app browser, is Add to Cart visible on mobile, did the Meta Pixel fire, the five store scores out of 100, the weakest product pages, visitor behaviour, and what went wrong this week for visitors from Meta ads (taps that do nothing, page errors, where they leave, slow pages) with fix steps. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get which ads are tiring: frequency, click rate and its change, and hook rate per ad, highest frequency first. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get a review of the copy on ads already running: first line, headline, call to action and link, with a score and the specific issues found. Also video ads from the last 7 days: hook rate, hold rate, where viewers drop off, a visual review of the frames and fix steps. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get the audience picture: buyers in the period, saved custom audiences with size and whether each is big enough to deliver, and results split by placement. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get recent changes in competitor ads: who changed what (volume, angle, format) and when. Read only, saved data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
Get the brand's fix list: fixes you chose to do, their status, and once newer data is saved, whether the number moved after you marked the fix done. Read only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| status | string | no | — |
Add a fix to the brand's Run1Ads fix list. Pass item_key from get_today to add that finding with its steps and the number to track, or pass your own title. Writes to Run1Ads only. Nothing changes in Meta or on your store.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| item_key | string | no | The key of a finding from get_today (for example vc_atc or fatigue). |
| title | string | no | Your own fix title, if not using item_key. |
| why | string | no | — |
| how | array | no | Steps to apply it. |
| pillar | string | no | funnel, journey, fatigue, content, audience, strategy or general. |
Mark a fix on the fix list as done. Run1Ads records the number at that moment so it can show whether the fix worked once newer data is saved. Writes to Run1Ads only.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| fix_id | integer | yes | The fix id from get_fix_list. |
Ask the Run1Ads consultant a question about this brand in plain English. It answers from the saved account data only, with exact steps you can apply. It advises only and never changes anything. Up to 10 questions per brand per day, shared with the app.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| question | string | yes | — |
Send one finding from get_today to the brand's own Meta ad account as a PAUSED campaign and ad set, so you can finish and switch it on yourself in Ads Manager. Nothing spends. Only findings marked draftable can be sent. Only use this when the user has clearly asked for it, and pass confirm true. Without confirm it returns a preview and sends nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | string | no | Brand id from list_brands. Leave it out to use your most recently updated brand. |
| item_key | string | yes | The key of a draftable finding from get_today (fatigue, creative_copy, placement or lookalike). |
| objective | string | no | — |
| daily_budget_usd | number | no | Daily budget saved on the paused draft. It does not spend until you switch the draft on. |
| confirm | boolean | no | Must be true, and only after the user explicitly asked to send this draft. |
- 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 Run1Ads: live Meta ads consultant or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_brands | no tags | |
| get_today | no tags | |
| get_performance | no tags | |
| get_sales_funnel | no tags | |
| get_live_alerts | no tags | |
| get_store_checks | no tags | |
| get_ad_fatigue | no tags | |
| get_ad_copy_review | no tags | |
| get_audiences | no tags | |
| get_competitor_changes | no tags | |
| get_fix_list | no tags | |
| add_to_fix_list | state-write | state-write: declares readOnlyHint: false |
| mark_fix_done | state-write | state-write: declares readOnlyHint: false |
| ask_consultant | no tags | |
| send_paused_draft | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.
No release note was published with this version.
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.
Any signed-in account that does not publish Run1Ads: live Meta ads consultant can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.