Skip to content

Connectors / Analytics

Analytics MCP connectors for Claude, ChatGPT and Cursor

20+ 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.

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.

Marketing

  • Check which campaign cohorts grew this week

    List the cohorts tied to campaigns, compare them against last week, and get a plain summary of which audiences moved.

  • Check this week's AI visibility before standup

    Ask how often your brand appeared in AI responses for your tracked prompts over the last date range, and which topics moved. The answer comes from live AthenaHQ data, not a screenshot someone exported on Friday.

  • Build a segment for a launch

    Describe the audience in plain words, such as enterprise accounts that have not touched reporting, and have the segment created in Pendo ready for a guide or an email.

Product

  • Check what is waiting for review

    Ask how many items are still open in a Langfuse annotation queue and who they are assigned to before the weekly quality meeting.

  • Look up token prices and price history

    Get the current price of a token, its price history over a range, and a quick stat like average or high before a launch decision.

  • Check a funnel without opening Mixpanel

    Ask how signup to activation looked this week and get the numbers from a live query, then pull the saved report when someone wants the detail.

Analytics

  • Find out why an alert fired

    Search Looker alerts, read the notifications behind a threshold breach, and follow the ones that matter to your dashboards.

  • Set up a new analyst on day one

    Create the person as a Sigma Computing member, add them to the right team, and grant them access to the workspaces their group uses, all from one request.

  • 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.

Data

  • See how eval scores are distributed

    Ask how a Helicone eval is scoring across the last week, spot the requests that fall at the bottom, and compare against the models in use.

  • Line up an identity after a change

    When someone changes email or merges accounts, update the identity in Heap so their sessions sit under one person instead of two.

  • Tidy up actions nobody owns anymore

    Pull every action, find duplicates and stale definitions, and update or delete them with a clear note of what changed.

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.

    Allium

  • List all Amplitude cohorts created this quarter.

    Amplitude

  • Which Artie connectors pull tables from the warehouse database?

    Artie

  • Which prompts mentioned our competitors more than us this week?

    AthenaHQ

  • List orphan URLs from the latest analysis

    Botify

  • Which trackers drove the most calls this week?

    CallRail

  • What was our MRR last month and how did it change?

    ChartMogul

  • List DoiT analytics alerts created this month.

    DoiT

The tools

What an agent can call in Analytics

Connectors
20+

in the Analytics catalog

Tools
2,218

callable the moment you connect

Hosted sign-in
8

connect with nothing to register

Of those 2,218 tools, 7% delete something. Restricting an agent to reads is not a promise here, it is 785 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 35%
785 tools · list, get, search
Write 21%
474 tools · create, update, send
Delete 7%
165 tools · delete, remove, archive
Other 36%
794 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. API key and App credentials mean an admin pastes them once, with nothing to register.

Analytics connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
PostHog 482 Hosted
Looker 294 App credentials
Lenses 258 API key
Sigma Computing 136 App credentials
DoiT 129 API key
Langfuse 100 API key
AthenaHQ 94 Hosted
Allium 90 API key
Pendo 87 Hosted
Promptwatch 69 API key
Google Analytics 66 Hosted
Mixpanel 64 Hosted
Amplitude 59 API key
Artie 59 API key
CallRail 59 API key
Botify 48 API key
Helicone 46 API key
Fullstory 33 Hosted
StreetLight Data 24 API key
Supermetrics 14 Hosted
Heap 7 API key
ChartMogul Hosted

FAQ

Frequently asked questions

How many Analytics connectors does Elaichi have?

20+ 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 or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. 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. 8 of the Analytics connectors use Elaichi's hosted sign-in, with nothing to register. 14 connect with an API key or app credentials that an admin pastes once, with no app to register. Nothing in this category asks you to register an OAuth app 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 left out of the model's tool list and cannot be called. Read-only access to a Analytics connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Analytics connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

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
Claude ChatGPT Cursor 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.