Google Analytics MCP connector
The Google Analytics connector brings your accounts, properties, custom dimensions, user access and change history into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so your team can review and tidy Google Analytics setup by asking in plain language.
- Connects over OAuth
- Free 14-day trial
- No credit card
Summarize last week's traffic across our GA4 properties.
Working in Google Analytics with Elaichi
-
List all Google Analytics accounts
-
Get single Google Analytics account by ID
-
List all Google Analytics account user
How to connect Google Analytics to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Google Analytics MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Google Analytics MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Google Analytics MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Google Analytics MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Google Analytics MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Google Analytics to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Google Analytics through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Google Analytics is logged.
-
Marketing
Set up a property for a new site
When a campaign site or new brand goes live, create the Google Analytics property, add the custom dimensions the team needs to track, and confirm it landed in the right account, all from one conversation.
-
Analytics
Keep custom dimensions clean
Ask for every custom dimension across a property, spot the ones nobody uses or that duplicate each other, then rename what should stay and archive what should not.
-
IT
See who has access to each account
List the people bound to a Google Analytics account, pull an access report for a property, and find the ex-contractor or old agency login that should have been removed months ago.
-
Compliance
Find out who changed a setting
When a property suddenly looks different, search the change history to see who edited what and when, and get a plain summary rather than reading through the admin screens.
-
Agency
Take stock of every client account
Pull account summaries across all the Google Analytics accounts you manage, list the properties under each, and update names or settings that have drifted out of your naming standard.
-
Web
Review data sharing before launch
Before a new property goes live, check its account's data sharing settings and confirm they match what legal signed off, then fix anything that does not.
Try asking
- “Summarize last week's traffic across our GA4 properties.”
- “Which accounts have new access bindings this month?”
- “List change history for the marketing property.”
What connecting Google Analytics gets you
6 screens from Elaichi, each doing one job for your Google Analytics account.
Ask Elaichi to work across your apps.
Summarize last week's traffic across our GA4 properties.
Which accounts have new access bindings this month?
List change history for the marketing property.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about properties, get answers from live reports.
Type a question in plain language and read it back from Google Analytics.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Connect any MCP client over OAuth, with no SDK and no shared API key.
Tool catalog
66 Google Analytics tools, no custom code.
Browse accounts, properties, access bindings and change history by tool name, resource and method.
Toolboxes
Every team gets its own toolbox.
Growth, marketing and finance each see a curated set of Google Analytics tools.
Shared connections
Teammates use accounts without seeing credentials.
Each connection shows who added it and which teams and members share it.
Audit log
Answer who ran which report, and when.
Every Google Analytics call is logged with actor, event, type and resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Google Analytics digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Google Analytics
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Google Analytics
Queued
Automations
A schedule fires, a digest posts back.
Six steps fetch and group properties, draft a digest, then wait for approval.
Google Analytics health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
Accounts
1,284 ↓ 12%
Properties
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Accounts created
Last 14 days
By team
Share of activity
Growth 34%
Marketing EMEA 27%
Web platform 21%
Data engineering 18%
Collections and dashboards
Property health numbers, computed on a schedule.
Four metrics, 14 days of reports created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Google Analytics
All three can connect Google Analytics to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Google Analytics tools | Allow or restrict single Google Analytics tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Google Analytics call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Google Analytics tools for your AI agents
66 tools are ready to call through Elaichi's MCP endpoint the moment you connect Google Analytics, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Google Analytics to Claude?
Connect Google Analytics in Elaichi first: you sign in with your Google account and approve access, the same way you would sign in to Google Analytics itself. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and Google Analytics is ready to use.
Does Google Analytics work with ChatGPT and Cursor as well as Claude?
Yes. Once Google Analytics is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Google Analytics once and every client you use picks it up.
What can an AI agent actually do with my Google Analytics data?
With Google Analytics connected, an agent can list your accounts and properties, create or rename a property, add, update or archive custom dimensions, show who has access to an account, review data sharing settings, and search the change history to explain who changed what. Because Google Analytics has a large set of actions, short concrete asks like "archive the unused dimensions on the store property" work better than long paragraphs.
Does connecting Google Analytics give the AI access to every account and property?
No. The agent sees exactly the Google Analytics accounts and properties the signed-in person can already see, with the same viewer, editor or administrator level Google has given them. Elaichi can narrow that further, for example to read-only or to a single team's properties, but it can never widen it beyond what the person holds in Google Analytics.
Can I stop an agent from deleting or changing things in Google Analytics?
Yes. Restrictions in Elaichi apply per action, so you can allow listing accounts and properties while restricting property deletion, dimension archiving or any update. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT or any other client cannot run it, whatever the prompt says.
What happens to a Google Analytics connection when someone leaves?
When you offboard a person in Elaichi their access to Google Analytics through Elaichi ends immediately, in every client they had set up. If the Google Analytics connection was shared with a team, it keeps working for everyone else. If you disconnect Google Analytics in Elaichi entirely, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at once.
Does the Google Analytics MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Google Analytics is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Google Analytics?
Yes. Both let Claude, ChatGPT or Cursor use Google Analytics. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Google Analytics call.
How is Elaichi different from Composio for Google Analytics?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Google Analytics: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Google Analytics in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot