Before you start — what to prepare

Send this page to whoever owns each platform. Everything here happens inside your own accounts; nothing is shared with anyone. Items marked ⏳ involve an approval by Google or LinkedIn and can take days — start them first.

1. A server and a name (IT — 30 min)

• A Linux server (Ubuntu/Debian, 1 CPU, 2 GB RAM) with a public IP, ports 80 and 443 open.
• A hostname for it, e.g. mcp.yourcompany.com — a DNS A record pointing at the server.
• Someone who can SSH into it to run one install command.

2. Google — Ads, Analytics 4, Search Console, Keyword Planner (Google admin — 30 min + ⏳)

• A Google Cloud project with these APIs enabled: Google Ads API, Google Analytics Data API, Google Analytics Admin API, Google Search Console API.
• OAuth consent screen set to Internal (if you use Google Workspace) — or External + Publish app. ⚠️ Not "Testing": testing apps are disconnected by Google every 7 days.
• An OAuth client of type Web application (the redirect URI is shown on the setup page; add it there). Keep the Client ID and Client secret.
• ⏳ Google Ads developer token from a Manager (MCC) account → Tools → API Center → apply for Basic access (say "internal reporting tool"). 1–3 business days, sometimes more.
• The Google user who will click "Connect" must have access to the ad accounts, the GA4 property and the Search Console site.

3. Meta Ads — Facebook / Instagram (Meta Business admin — 15 min)

• A Meta app with the Marketing API product (developers.facebook.com → Create app → Business).
• A system user in Business Settings with your ad accounts assigned.
• A system-user token with ads_read (add ads_management only if you want Claude to be able to pause campaigns / change budgets), expiry Never.

4. LinkedIn Ads (LinkedIn page admin — 20 min + ⏳)

• A LinkedIn developer app associated with your Company Page (page verified).
• ⏳ Advertising API product requested and approved by LinkedIn (days to weeks).
• The app's Client ID and Client Secret; the redirect URL from the setup page added under Auth.
• A LinkedIn user with access to the ad accounts, to click "Connect".

5. Shopify (store owner — 10 min)

• A custom app (Settings → Apps → Develop apps) with scopes read_orders, read_all_orders, read_products, read_customers, installed.
• Its Admin API access token (shown once — copy it) and your *.myshopify.com domain.

6. Salesforce (Salesforce admin — 20 min)

• A Connected App with OAuth enabled and Client Credentials Flow turned on.
• A Run As integration user with read access to Leads and Opportunities.
• The Consumer Key, Consumer Secret, and your instance URL (https://yourorg.my.salesforce.com).
• Optional: a note on which LeadSource values mean Google Ads / Meta / LinkedIn / organic, and which Lead statuses count as "won".

7. Claude (Claude admin — 5 min on the day)

• Which Claude plan the team uses. Pro / Max: each person adds the connector themselves. Team / Enterprise: an Owner adds it once in Organization settings → Connectors, then each member connects to it. (The Free plan allows only one custom connector.)

8. From your vendor

• License key (MMP-XXXX-XXXX-XXXX) and the registry login for the installer.

9. Decide

• Which accounts to connect: every Google Ads, Meta and LinkedIn ad account you need (several per platform are fine), plus one GA4 property and one Search Console site per installation — tell us before installation day if you need more than one.
• Reporting currency and number format (e.g. USD / international).
• Whether Claude may change anything (write tools) — off by default.
• Who gets the Claude connector URL (it is a key — share via a password manager).

When the boxes are ticked, installation + connecting everything takes about an hour. Step-by-step instructions: Install, then Connect your data sources.