Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
Google Marketing 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.
99/100
trust score
1
downloads a day
local
runs on your machine
73
downloads in 30d
What it does
MCP server for Google Analytics 4, Google Search Console, Google Ads, and YouTube (Data + Analytics). Each module is independently activated by environment variables.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user google-marketing-mcp '--' npx -y @dongsik/google-marketing-mcp
# 2 — ask your agent for something these tools do
# status, list_accounts, list_properties and 62 more
Google Marketing costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DOAll 1 server
@dongsik1 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. This one runs on your machine: your client starts Google Marketing 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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user google-marketing-mcp '--' npx -y @dongsik/google-marketing-mcpReconnect, 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 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
65 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.
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.
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.
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.
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.
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.
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 MIT
- 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 Google Marketing 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 99 / 100
Release 0.4.3 · scanned 14 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 score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestfd581b74fd4e50244de341f2f7b3eace2aa708bdcc6bc0ec47b99bc2c85132ce
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| 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 (65 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>".
21 of the 65 recovered tools are registered only when ENABLE_GA4 holds (dist/index.js:165) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 1.
7 of the 65 recovered tools are registered only when ENABLE_GSC holds (dist/index.js:388) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 1.
19 of the 65 recovered tools are registered only when DEVELOPER_TOKEN holds (dist/index.js:486) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 1.
17 of the 65 recovered tools are registered only when ENABLE_YT holds (dist/index.js:917) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 1.
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.
1 tool is registered unconditionally · (1) 21 more only when ENABLE_GA4 holds (dist/index.js:165) · (2) 7 more only when ENABLE_GSC holds (dist/index.js:388) · (3) 19 more only when DEVELOPER_TOKEN holds (dist/index.js:486) · (4) 17 more only when ENABLE_YT holds (dist/index.js:917) — typically when a key or option is configured. All 65 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| status | no tags | |
| list_accounts conditional (1) | no tags | |
| list_properties conditional (1) | no tags | |
| run_report conditional (1) | no tags | |
| get_top_pages conditional (1) | no tags | |
| get_traffic_sources conditional (1) | no tags | |
| check_youtube_ga4_traffic conditional (1) | no tags | |
| get_user_overview conditional (1) | no tags | |
| get_users_by_country conditional (1) | no tags | |
| get_users_by_device conditional (1) | no tags | |
| get_trend_by_date conditional (1) | no tags | |
| get_realtime conditional (1) | no tags | |
| get_ga4_campaign_performance conditional (1) | no tags | |
| get_utm_breakdown conditional (1) | no tags | |
| compare_campaigns conditional (1) | no tags | |
| get_landing_page_performance conditional (1) | no tags | |
| get_conversions_by_event conditional (1) | no tags | |
| get_ecommerce_summary conditional (1) | no tags | |
| compare_periods conditional (1) | no tags | |
| get_metadata conditional (1) | no tags | |
| search_metadata conditional (1) | no tags | |
| list_categories conditional (1) | no tags | |
| gsc_list_sites conditional (2) | no tags | |
| gsc_query conditional (2) | no tags | |
| gsc_top_queries conditional (2) | no tags | |
| gsc_top_pages conditional (2) | no tags | |
| gsc_queries_by_page conditional (2) | no tags | |
| gsc_inspect_url conditional (2) | no tags | |
| gsc_list_sitemaps conditional (2) | no tags | |
| ads_list_campaigns conditional (3) | no tags | |
| ads_get_campaign_performance conditional (3) | no tags | |
| ads_get_search_terms conditional (3) | no tags | |
| ads_get_ad_group_performance conditional (3) | no tags | |
| ads_get_ad_performance conditional (3) | no tags | |
| ads_get_performance_by_device conditional (3) | no tags | |
| ads_get_performance_by_geo conditional (3) | no tags | |
| ads_get_budget_status conditional (3) | no tags | |
| ads_get_impression_share conditional (3) | no tags | |
| ads_get_quality_score conditional (3) | no tags | |
| ads_get_keyword_performance conditional (3) | no tags | |
| ads_get_account_summary conditional (3) | no tags | |
| get_roas_by_campaign conditional (3) | no tags | |
| get_click_session_gap conditional (3) | no tags | |
| get_new_vs_returning_by_campaign conditional (3) | no tags | |
| get_hourly_traffic_vs_budget conditional (3) | no tags | |
| get_utm_integrity_check conditional (3) | no tags | |
| get_campaign_product_revenue conditional (3) | no tags | |
| get_conversion_time_profile conditional (3) | no tags | |
| yt_list_my_channels conditional (4) | no tags | |
| yt_list_videos conditional (4) | no tags | |
| yt_video_stats conditional (4) | no tags | |
| yt_search_videos conditional (4) | no tags | |
| yt_resolve_channel conditional (4) | no tags | |
| yt_analytics_summary conditional (4) | no tags | |
| yt_analytics_report conditional (4) | no tags | |
| yt_traffic_sources conditional (4) | no tags | |
| yt_audience_retention conditional (4) | no tags | |
| yt_demographics conditional (4) | no tags | |
| yt_views_by_country conditional (4) | no tags | |
| yt_views_by_device conditional (4) | no tags | |
| yt_daily_trend conditional (4) | no tags | |
| yt_top_videos conditional (4) | no tags | |
| yt_search_terms conditional (4) | no tags | |
| yt_sharing_services conditional (4) | no tags | |
| yt_playlist_performance conditional (4) | 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 digestfd581b74fd4e5024
Scanned2026-10-14
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 0.4.3. Pin a release below and the command asks for exactly that one.
0.4.3
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 Google Marketing 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.