Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Runs in the cloud★ 15,812BSD-3-ClauseUpdated 8 days ago
Install
Google E-commerce (GA4, Search Console, Merchant Center, Ads)
Overview
Description from the maker (original English)
Multi-client read and controlled write (off by default): GA4, GSC, Merchant, GTM, ad platforms.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: PAGESPEED_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
GA4_PROPERTY_ID,GSC_SITE_URL,MERCHANT_ACCOUNT_ID,GTM_CONTAINER_ID,PAGESPEED_API_KEY,GEM_CLIENT,GEM_WRITE,GOOGLE_TOKEN_FILE
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"google-ecommerce": {
"command": "uvx",
"args": [
"google-ecommerce-mcp"
],
"env": {
"GA4_PROPERTY_ID": "your-value",
"GSC_SITE_URL": "your-value",
"MERCHANT_ACCOUNT_ID": "your-value",
"GTM_CONTAINER_ID": "your-value",
"PAGESPEED_API_KEY": "your-value",
"GEM_CLIENT": "your-value",
"GEM_WRITE": "your-value",
"GOOGLE_TOKEN_FILE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add google-ecommerce --env GA4_PROPERTY_ID=your-value --env GSC_SITE_URL=your-value --env MERCHANT_ACCOUNT_ID=your-value --env GTM_CONTAINER_ID=your-value --env PAGESPEED_API_KEY=your-value --env GEM_CLIENT=your-value --env GEM_WRITE=your-value --env GOOGLE_TOKEN_FILE=your-value -- uvx google-ecommerce-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"google-ecommerce": {
"command": "uvx",
"args": [
"google-ecommerce-mcp"
],
"env": {
"GA4_PROPERTY_ID": "your-value",
"GSC_SITE_URL": "your-value",
"MERCHANT_ACCOUNT_ID": "your-value",
"GTM_CONTAINER_ID": "your-value",
"PAGESPEED_API_KEY": "your-value",
"GEM_CLIENT": "your-value",
"GEM_WRITE": "your-value",
"GOOGLE_TOKEN_FILE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"google-ecommerce": {
"type": "stdio",
"command": "uvx",
"args": [
"google-ecommerce-mcp"
],
"env": {
"GA4_PROPERTY_ID": "your-value",
"GSC_SITE_URL": "your-value",
"MERCHANT_ACCOUNT_ID": "your-value",
"GTM_CONTAINER_ID": "your-value",
"PAGESPEED_API_KEY": "your-value",
"GEM_CLIENT": "your-value",
"GEM_WRITE": "your-value",
"GOOGLE_TOKEN_FILE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
GA4_PROPERTY_IDenvGA4 numeric property idGSC_SITE_URLenvSearch Console property, sc-domain:example.com or https://www.example.com/MERCHANT_ACCOUNT_IDenvMerchant Center account idGTM_CONTAINER_IDenvTag Manager container id, GTM-XXXXXXX- PageSpeed Insights API key (optional)
GEM_CLIENTenvPin this server process to one client of the client registry (clients.json)GEM_WRITEenvSet to 1 to allow writing at all (off by default; each client and platform must also be enabled)GOOGLE_TOKEN_FILEenvStore the OAuth token in this file instead of the OS keyring
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account MoonEyes, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 2538 servers in this category
- Published to the registry more recently than 67% of the other 2538 servers in this category
- Basic checks equal to or better than 100% of the other 2538 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Google E-commerce (GA4, Search Console, Merchant Center, Ads) safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: PAGESPEED_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.6.0) reached the registry 17 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
by stripe
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
Runs in the cloud★ 2,043MITUpdated 12 months ago
Install
MCP Cn Commerce
by TonyWang-hub
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
Runs on your computer★ 96MITUpdated 28 days ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
google-ecommerce-mcp
One MCP server for the data an online shop decides from, for one shop or for many clients: GA4, Search Console, Merchant Center, Tag Manager, Indexing API, PageSpeed, the ad platforms Google Ads, Meta Ads and ChatGPT Ads, and the Meta pixel, catalog, Instagram and Page. It reads by default, and can also prepare controlled changes that you approve (pause a campaign, change a budget, submit a sitemap, add a tag in a workspace).
Ask your AI assistant "how much organic traffic did we get this month?", "which products are disapproved in Merchant Center?", "is GA4 loaded twice on my site?" or "what did each ad platform claim last month, and what does GA4 say?" and it answers from your own accounts. Out of the box it reads and reports and changes nothing. If you turn writing on for a client, the assistant can propose a change as a plan; nothing is sent until you approve it, and anything that costs money needs your approval in a terminal, outside the chat.
Built by MoonEyes, a small French shop selling 3D-printed tabletop terrain, because no existing MCP server covered GA4, Search Console and Merchant Center together.
Writing is off by default and has never been tested on a real account. The write tools exist in this version, but they were checked offline only, against fake answers written from each platform's documentation. Turning them on is opt-in per client and per platform, creations are always paused, and some risks cannot be removed (for example a Google Ads token or a ChatGPT Ads key cannot be limited to reading). Read docs/SECURITY.md and docs/WRITE.md before you turn it on, and try it first on a test account. New here? [docs/QUICKSTART.md](https://github.com/MoonEyes/google-ecommerce-mcp/blob/main/docs/QUICKSTART.md): your first client in 10 minutes.
The paid media connectors are new and tested offline only. The Google Ads, Meta Ads and ChatGPT Ads tools were checked against fake responses written from each platform's documentation. They have not been run against real ad accounts yet: compare the first figures with each platform's own interface. Details: docs/ADS.md.
Documentation
| Page | What is in it |
|---|---|
| Quickstart | Your first client in 10 minutes: four commands |
| Several clients | The client registry clients.json, secrets per client, isolation, an agency example |
| Reading pilot | A pilot with one client and writing left off: access checklist, steps, how to check writing is off, how to revoke |
| Writing: plan, approve, apply | Turn writing on in 5 steps, three full examples, every lock, every refusal and its fix |
| Architecture | Components, the write path, a tool call step by step, design choices, sequence diagrams |
| Tool reference | Every tool (82): parameters, output, example questions |
| Setup, one service at a time | Which services you need, access checklist and e-mail template for a client, install order with doctor checks, revocation |
| Client reporting | Monthly report plan, KPI formulas, the report command and its input contract |
| Guided install prompts | A prompt to paste into Claude to be guided step by step (French) |
| Third-party notices | Code ported from OpenGSC (MIT); ideas credited to other open-source projects (no code copied) |
| Easy setup guide for ad platforms | Google Ads, Meta Ads, ChatGPT Ads: client e-mail, numbered steps, ids, checks, revocation |
| Paid media guide | Google Ads, Meta Ads, ChatGPT Ads: prerequisites step by step, GAQL rules, errors, what is untested |
| Google Cloud setup | OAuth client, APIs to enable, where to find each id |
| Security model | What writing changes, the real guardrails, the known limits, scopes, token storage, how to revoke |
| Troubleshooting | Every error we have met and its fix |
| Example prompts | Questions that work well, by use case |
| Client configs | Claude Desktop (one or two shops), Claude Code |
Why this one
- One server for the whole picture. Traffic and sales (GA4), organic search (Search Console), the product feed (Merchant Center), the tracking setup (Tag Manager), site speed, and what the ad platforms say they delivered. Other MCP servers cover one or two of these.
- Several clients, kept apart. An agency registers each client once (ids in a file, secrets in the OS keyring). Every call names its client, a foreign account id is refused, and one server process can be pinned to one client.
- Read by default, controlled writing on request. Reading uses a per-platform allow-list with no write endpoint. Writing is off until you enable it per client and per platform, and then goes through one path only: plan (diff, dry run, signed token), your approval (in a terminal for anything that costs money, is irreversible or touches personal data), apply, and a journal. Creations are paused; there is no activation, deletion or publishing in this version.
- Secrets kept out of the way. The Google token goes to your OS keyring (Windows Credential Manager, macOS Keychain or Secret Service). The Google Ads token is a separate keyring entry because its scope can write. Meta and ChatGPT Ads secrets go to the OS keyring from a hidden prompt (an environment variable also works), never on the command line or in a URL.
- Answers a model can read correctly. Reports return the top rows plus totals over everything, the unit and definition of each metric, dates resolved in the account's timezone with a flag when the last days can still change, and the attribution windows each ad platform used.
- Honest about what it does not know. Ad platforms count conversions their own way. The tools say so in every answer instead of adding up numbers that should not be added.
- No third party. Requests go straight from your machine to Google, Meta and OpenAI. Nothing goes through a MoonEyes server.
How it compares
Checked on 2026-10-18 from each project's public page; they change fast, so check before you decide.
| Project | License | Scope | Writing |
|---|---|---|---|
| googleanalytics/google-analytics-mcp (official) | Apache-2.0 | GA4 | reads only |
| googleads/google-ads-mcp (official) | Apache-2.0 | Google Ads | reads only |
| Meta Ads MCP (official, hosted by Meta, beta) | closed | Meta Ads | yes, hosted by Meta |
| pipeboard-co/meta-ads-mcp | BUSL | Meta Ads | yes |
| stape-io/google-tag-manager-mcp-server | Apache-2.0 | Tag Manager | read and write |
| RoyAzran/mcp-ads | MIT | 12+ ad and analytics platforms | see its docs |
| This project | MIT | GA4, Search Console, Merchant Center, Tag Manager, PageSpeed, Google Ads, Meta Ads, ChatGPT Ads | off by default, plan, approval, journal, rollback; never tested on a real account |
Where this one fits: you run several shops or clients from one self-hosted server and want every change shown as a diff and approved before it is sent. If you need one Google product only, or a hosted service with nothing to install, the official servers above are the better choice.
What you can ask
Each case gives the question, the tools the assistant usually calls, what you learn, and the decision it supports. The decision stays yours: by default the server shows data and changes nothing, and any change it prepares needs your approval. Ready-to-paste prompts are in examples/PROMPTS.md.
Traffic, search, feed, tracking
- Where do visits and sales come from? *"Sessions, purchases and revenue by channel, this month vs. last month."* Tools:
ga4_report. You learn which channels bring revenue and which only bring visits. Decision: where to put the next hour or euro. - Which searches are one push away from page one? *"Queries ranking 5 to 15 with more than 100 impressions, and their landing page."* Tools:
gsc_performance. You learn which pages already earn impressions but few clicks. Decision: which titles, descriptions and internal links to rewrite first. - Which disapproved products still get visits? *"Products disapproved in Merchant Center that still receive organic clicks."* Tools:
merchant_product_issues,gsc_performance. You learn which feed errors hit pages people still visit. Decision: fix those products before the rest. - Is the tracking trustworthy? *"Is GA4 loaded twice? Does the purchase tag fire once? Is the workspace the same as the live version?"* Tools:
gtm_inventory,ga4_realtime. You learn whether purchases or page views may be double counted and whether unpublished changes exist. Decision: publish, remove a duplicate tag, or leave it. - Preparing a redesign. *"Which landing pages earn money and organic clicks, which will need a 301, and what is today's speed baseline?"* Tools:
ga4_report(dimensionlandingPage),gsc_performance,gsc_moves,gsc_opportunities,gsc_inspect_url,pagespeed. You learn which URLs to preserve, which redirects to plan, and the before-numbers to compare with after. Decision: the redirect map and what must not change.
Paid media (needs the c
Only the beginning is shown; read the rest in the repo