claude skills / MCP Kit for Marketers / mcp-connections-setup / en français

MCP connections setup.

Five read-only connections, tested one by one: Claude reads your numbers instead of your exports.

See what it produces
  • Claude Code
  • Claude Desktop
  • Claude.ai
  • Google Search Console
  • Google Analytics 4
  • Google Ads
  • Shopify
  • Notion
5connections ready: Search Console, GA4, Google Ads, Shopify, Notion
0write tools active by default, everything starts read-only
1test query per tool, logged before you rely on it

orders of magnitude, depending on your volume

the problem

What gets in the way today.

  • 01Every month, someone exports Search Console, GA4 and Google Ads into a spreadsheet before anyone can ask a single question.
  • 02MCP tutorials contradict each other, server names change and the connection breaks at the first authentication error.
  • 03Nobody remembers where each key is stored, or which tool is allowed to write to your accounts.

input, output

You give this. You get this.

What you give Claude: your Claude client, your tools, your roles and your machine

Company: Halden Tile Co. (online tile shop)
Client: Claude Code (desktop app)
Tools: GA4, Google Ads, Search Console, Shopify, Notion
Google Cloud: new project "halden-reporting", I can enable APIs
My roles: admin in GA4 and Google Ads, owner in Search Console
Machine: macOS, pipx, uv and Node installed
Scope: my machine only
Goal: monthly reporting without exports, no write actions

$ claude "Connect Claude Code to our GA4, Google Ads, Search Console, Shopify and Notion accounts, read-only, and give me the setup log."

MCP setup log, excerptexample

MCP setup log: Halden Tile Co.

Date: 2026-11-19 | Client: Claude Code (desktop app) | Scope: user, marketing lead's machine only

CONNECTIONS

GA4 | analytics-mcp (Google) | ADC, analytics.readonly | write tools off | Working

Google Ads | google-ads-mcp, pinned release (Google) | ADC, Read only user | write off and denied in client | Working

Search Console | community server | OAuth desktop client | manage_sitemaps denied | Working

Shopify | Shopify connector | store sign-in | all write tools and customer tools denied | Working

Notion | Notion remote MCP | OAuth, member account "reporting" | create and update denied | Working

TEST QUERIES

GA4: sessions and key events, last 28 days > Answered. Purchase is the key event, not generate_lead

Google Ads: cost and conversions by campaign, October > Answered after fix. First call failed with CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION, access requested, retried next day

Search Console: clicks, impressions, CTR, position, 28 days vs previous > Answered. Last 3 days excluded (final data only)

Shopify: orders and sales, October, top 5 products > Answered, matches the admin report

CREDENTIALS (locations only, never values)

GA4, Google Ads: ADC in the default gcloud folder, owner marketing lead

Search Console: OAuth client JSON in ~/secrets/gsc/, outside any repository

NOT SET UP

Shopify Dev MCP: no theme or app work planned.

NEXT REVIEW

2027-02-19: check each connection is still used, re-read the five READMEs for new write tools.

the method

What Claude does, in order.

  1. step 1Map the need

    For each tool, Claude notes the questions it must answer, the account it reads and whether a write action is really needed. For reporting, almost never.

  2. step 2Choose the server

    The vendor's official server first. A community server only as a fallback, flagged as such, with the date its README was read.

  3. step 3Configure without secrets

    The configuration is written with empty placeholders, keys stay in files outside the repository, write tools are turned off on the server and denied in the client.

  4. step 4Test and log

    One connection at a time: authentication, a real test query, result recorded. Then the full log, with the date of the next review.

demo in French / click, try it

Your turn.

An interactive demo of the skill. It is in French, the pack works in any language: ask Claude to answer in English.

GA4

the film / 44 seconds, with sound

The pack film.

the pack film

In 8 seconds.

the guardrails

What the skill never does.

  • Read-only by default: a write tool is only turned on for a named task, then turned off again.
  • No secrets in the conversation: Claude writes placeholders like PATH_TO_CREDENTIALS_JSON and never asks you to paste a key.
  • The server's README on the day of setup is the reference: every difference with the skill is noted in the log.
  • A connection is only trusted after a real test query, with its result logged.

Questions

Do I need to know how to code?

No, but you need to be able to run a few commands. Claude writes the configuration and guides you step by step, from the Google Cloud project to the test query.

Why do I need a Google Cloud project?

Three of the five connections (Search Console, GA4, Google Ads) go through Google APIs. The skill explains how to enable them and create read-only credentials.

Does it work with Claude.ai and Claude Desktop?

Yes. The setup differs by client, so the skill asks which one you use before writing any configuration.

What happens when a server changes?

The skill re-reads the README before each setup and notes the differences. The log is then your starting point when a connection breaks.

the pack

In the pack: MCP Kit for Marketers.