Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
ChatGPT Ads 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.
100/100
trust score
33
downloads a day
local
runs on your machine
750
downloads in 30d
What it does
ChatGPT Ads MCP server: 30 read tools, 28 opt-in preview-first writes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'OPENAI_ADS_API_KEY=${OPENAI_ADS_API_KEY}' --env 'OPENAI_ADS_ACCOUNT_ID=${OPENAI_ADS_ACCOUNT_ID}' --transport stdio chatgpt-ads-mcp '--' npx -y @getmcpads/chatgpt-ads-mcp-server
# 2 — ask your agent for something these tools do
# openai_ads_get_account, openai_ads_get_campaigns, openai_ads_get_campaign and 17 more
It needs OPENAI_ADS_API_KEY, OPENAI_ADS_ACCOUNT_ID: this reads them from your environment, so export them first.
ChatGPT Ads costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GEAll 15 servers
getmcpads15 servers
2 categories
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. This one runs on your machine: your client starts ChatGPT Ads as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads OPENAI_ADS_API_KEY (Advertiser API key from Ads Manager settings. Scoped to one ad account. Keep it secret), OPENAI_ADS_ACCOUNT_ID (The adacct_ ID the key belongs to. The only account the server will use) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx OPENAI_ADS_API_KEY …, setx OPENAI_ADS_ACCOUNT_ID … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'OPENAI_ADS_API_KEY=${OPENAI_ADS_API_KEY}' --env 'OPENAI_ADS_ACCOUNT_ID=${OPENAI_ADS_ACCOUNT_ID}' --transport stdio chatgpt-ads-mcp '--' npx -y @getmcpads/chatgpt-ads-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: OPENAI_ADS_API_KEY — Advertiser API key from Ads Manager settings. Scoped to one ad account. Keep it secret.; OPENAI_ADS_ACCOUNT_ID — The adacct_ ID the key belongs to. The only account the server will use.. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
20 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Read the configured ChatGPT Ads account: name, currency, time zone, status and brand review. Also verifies that the API key belongs to OPENAI_ADS_ACCOUNT_ID. Run it first.
No parameter schema on file.
List one page of campaigns in the account. Follow last_id only when has_more is true. Budget amounts use integer account-currency micros.
No parameter schema on file.
Read one campaign with its native status, budget, schedule and targeting.
No parameter schema on file.
List one page of ad groups in a campaign. Native ad group IDs start with adgrp_. Follow last_id only when has_more is true.
No parameter schema on file.
Read one ad group with its native bidding, context hints and product set.
No parameter schema on file.
List one page of ads in an ad group with native creative metadata and review status. Follow last_id only when has_more is true.
No parameter schema on file.
Read one ad with its creative and review status. No preview or change is requested.
No parameter schema on file.
List chat card creatives of the account or of one ad group, 20 ads per page, or read up to 60 exact adIds. Each item has the native file_id, signed image_url, title, body, destination and review status. An expired image link is refreshed with one ad read. Follow nextCursor when hasMore.
No parameter schema on file.
Read performance by account, campaign, ad group or ad over inclusive account-local dates. One optional country, device or platform breakdown supports delivery metrics only; use openai_ads_get_conversion_insights for conversions by country or device. Attribution defaults to 30-day click, 1-day view…
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- 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 ChatGPT Ads 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: —
ATrust score 100 / 100
Release 1.0.1 · scanned 26 Oct 2026
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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest4fb87e94a3ef3f8cbc5751e0fa1b574b2eef7d548895528024e9a6a3f66de07f
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
5 of the 11 recovered tools are registered only when !write holds (dist/cli.js:3163) — typically when a key or option is configured. They are part of the server's surface and were analysed; the other branch of the same condition registers the rest.
6 of the 11 recovered tools are registered only when !write is false (dist/cli.js:3163) — typically when a key or option is configured. They are part of the server's surface and were analysed; the other branch of the same condition registers the rest.
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.
No tool is registered unconditionally · (1) 5 only when !write holds (dist/cli.js:3163) · (2) 6 only when !write is false (dist/cli.js:3163) — typically when a key or option is configured. All 11 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| openai_ads_get_bulk_job conditional (1) | no tags | |
| openai_ads_get_bulk_job_operations conditional (1) | no tags | |
| openai_ads_get_write_schema conditional (1) | no tags | |
| openai_ads_get_write_context conditional (1) | no tags | |
| openai_ads_get_mutation conditional (1) | no tags | |
| openai_ads_submit_bulk_job conditional (2) | no tags | |
| openai_ads_upload_image conditional (2) | no tags | |
| openai_ads_upload_image_url conditional (2) | no tags | |
| openai_ads_rename_campaign conditional (2) | no tags | |
| openai_ads_rename_ad_group conditional (2) | no tags | |
| openai_ads_rename_ad conditional (2) | 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 digest4fb87e94a3ef3f8c
Scanned2026-10-26
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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.1. Pin a release below and the command asks for exactly that one.
1.0.1
26 Oct 2026
latestNo release note was published with this version.
1.0.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
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 ChatGPT Ads 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.