Connectors / Analytics
Analytics MCP connectors for Claude, ChatGPT and Cursor
10+ Analytics connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Analytics connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
13 connectors
-
Allium Hosted sign-in 90 tools
-
Amplitude Hosted sign-in 58 tools
-
Artie Hosted sign-in 59 tools
-
Botify Hosted sign-in 48 tools
-
DoiT Hosted sign-in 129 tools
-
Google Analytics Hosted sign-in 66 tools
-
Helicone Hosted sign-in 46 tools
-
Langfuse Hosted sign-in 100 tools
-
Lenses Hosted sign-in 258 tools
-
Looker
Hosted sign-in
294
tools
-
Promptwatch Hosted sign-in 69 tools
-
Sigma Computing
Hosted sign-in
136
tools
-
StreetLight Data Hosted sign-in 24 tools
No Analytics connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Analytics connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
IT
-
Review who holds which Looker role
List every Looker user and role, spot people with more access than their job needs, and tighten a role without opening Looker.
-
Onboard a new engineer into Lenses
Create the Lenses user, drop them into the right groups and check their settings in one conversation. Update several profiles or group memberships at once when a whole cohort joins.
-
Audit who can open which workspace
Pull the list of Sigma Computing workspaces and their grants, then see which members and teams hold access before a security review.
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.
-
Find where a table actually lives
Search the Artie data catalog for the orders or customers table, pull its column detail, and answer the question without opening three separate consoles.
-
Keep the event taxonomy tidy
Ask which event types exist, group them into taxonomy categories, rename a category that no longer fits, and remove an empty one, all without opening the taxonomy screen.
Operations
-
Clean up stale alerts and allocations
Pull the full list of DoiT alerts and allocations, spot the ones tied to projects that have ended, and remove them once the owner has confirmed.
-
Clean up finished review work
Mark reviewed Langfuse queue items as done, remove stale assignments in bulk, and retire dataset items that no longer reflect the product.
-
Keep alert thresholds current
Update a Looker alert when a target changes, or trigger it right away to check the new threshold behaves as expected.
Finance
-
Check treasury wallet balances and holdings
Pull the current balances for the organization's wallets and see how holdings have shifted over the month before the close.
-
Check AI spend before the invoice lands
Read the Helicone dashboard figures for requests and cost by model or by property, and summarize them for the monthly budget review.
-
Follow revenue alerts without a Looker login
Follow or unfollow Looker alerts on the numbers you care about, and catch the notification the moment a figure crosses a line.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Analytics account you connected.
-
Show me the latest token price history for ETH.
-
List all Amplitude cohorts created this quarter.
-
Which Artie connectors pull tables from the warehouse database?
-
List orphan URLs from the latest analysis
-
List DoiT analytics alerts created this month.
-
Summarize last week's traffic across our GA4 properties.
-
Summarize Helicone requests with low feedback scores this week.
-
List open annotation queue items assigned to the eval team
The tools
What an agent can call in Analytics
- Connectors
- 10+
- Tools
- 1,377
- Hosted sign-in
- 13
in the Analytics catalog
callable the moment you connect
connect with nothing to register
Of those 1,377 tools, 11% delete something. Restricting an agent to reads is not a promise here, it is 589 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 43%
- 589 tools · list, get, search
- Write 30%
- 408 tools · create, update, send
- Delete 11%
- 153 tools · delete, remove, archive
- Other 16%
- 227 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Analytics connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| Looker | 294 | Hosted | |
| Lenses | 258 | Hosted | |
| Sigma Computing | 136 | Hosted | |
| DoiT | 129 | Hosted | |
| Langfuse | 100 | Hosted | |
| Allium | 90 | Hosted | |
| Promptwatch | 69 | Hosted | |
| Google Analytics | 66 | Hosted | |
| Artie | 59 | Hosted | |
| Amplitude | 58 | Hosted | |
| Botify | 48 | Hosted | |
| Helicone | 46 | Hosted | |
| StreetLight Data | 24 | Hosted |
FAQ
Frequently asked questions
How many Analytics connectors does Elaichi have?
10+ Analytics connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Analytics connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Analytics account once makes it reachable from every one of them.
Do Analytics connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Analytics connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Analytics connectors need me to bring my own OAuth app?
No. Every Analytics connector in the catalog connects through Elaichi's hosted sign-in, so there is nothing to register before you start.
Can I stop an agent from writing to Analytics tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Analytics connector is a matter of allowing the reads and leaving the writes out.
Nearby
Teams that connect Analytics usually connect these too
Put Analytics connectors in front of your team
14 days on Gold, no credit card. Connect one and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.