Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
PPC Ad Editor 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.
96/100
tool-list score
2
tools declared
remote
at its publisher
—
calls last 7d
What it does
Preview Google Search, PMax, Display, YouTube, Meta and LinkedIn ad mockups in chat. No sign-in.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ppc-ad-editor-mcp https://studio.ppcadeditor.com/api/mcp/preview
# 2 — ask your agent for something these tools do
# preview_ad, get_ad_formats
PPC Ad Editor costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PPAll 1 server
ppcadeditor1 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 ppc-ad-editor-mcp https://studio.ppcadeditor.com/api/mcp/previewReconnect, 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
2 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.
Show a realistic mockup of one ad (Google Search, Display, Performance Max, Demand Gen, YouTube, Facebook/Instagram, LinkedIn) right in the chat. No account needed. The ad copy comes from the caller. Images are hosted HTTPS URLs in images[] / logos[], for example from the advertiser's website; this tool never generates images, and Google Search ads need none. Studio, YouTube and www.ppcadeditor.co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| format | string | yes | Ad format of the mockup. Field limits per format are listed in the format specs. |
| name | string | no | Optional name for the ad, used if the user saves it |
| headlines | array | no | Short headlines. The character limit depends on the format and is listed in this tool's format specs. Google Search headlines are 30 characters. There is no single limit for every format. |
| descriptions | array | no | Not the Facebook or Instagram body. On META_SINGLE and META_CAROUSEL this is the optional link line under the headline, 25 characters, and it may be omitted. Body copy belongs in primary_texts (125 ch |
| long_headlines | array | no | Long headlines for Performance Max, Display and Demand Gen. Character limits are in the format specs. Google Search and Meta do not use this field. |
| primary_texts | array | no | Body copy for Facebook, Instagram and LinkedIn. META_SINGLE, META_CAROUSEL and META_STORY: 125 characters. Google Search does not use this field. |
| final_url | string | yes | — |
| display_path_1 | string | no | Optional Google display path. 15 characters. |
| display_path_2 | string | no | Optional second Google display path. 15 characters. |
| business_name | string | no | Business name shown on the ad. 25 characters. |
| call_to_action | string | no | Button label, for example Learn more. 30 characters. |
| images | array | no | Core ad-body images (Meta hero, Carousel cards, PMAX assets, etc.). Feature-gated per format. Google image EXTENSIONS (shown below an RSA text ad) go in extensions.images. |
| logos | array | no | Core ad-body logos (brand/profile image shown next to the ad on Meta, LinkedIn, RDA, PMAX). |
| videos | array | no | Core ad-body videos (YouTube URLs). Primary for YOUTUBE format, optional for Meta/PMAX/RDA. |
| extensions | object | no | Ad extensions (aka ad assets). Google formats only — ignored on Meta/LinkedIn/YouTube. |
Returns the full specification for each ad format: field counts, character limits and supported media.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| formats | array | no | Optional filter: only return specs for these formats |
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 PPC Ad Editor 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: —
ATool-list grade · score 96 / 100
Release 1.1.0 · scanned 3 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestfe8d5b3aa22e7a85dc833a140bd2eb46247e9a2210bf1641277d1c04aed9ef10
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| preview_ad | no tags | |
| get_ad_formats | no tags |
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
Integrityfirst-seen
Surface digestfe8d5b3aa22e7a85
Scanned2026-11-03
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.1.0.
1.1.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 PPC Ad Editor 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.