---
title: "MCP server: connect Claude and ChatGPT to analytics"
description: "Connect Claude, ChatGPT, Codex, Claude Code, Cursor, VS Code or Gemini CLI to Countly."
url: https://countly.com/feature/mcp
last_modified: 2026-11-11
---

MCP Server

# Your AI assistant, with your analytics behind it

Connect Claude, ChatGPT, Codex, Claude Code, Cursor, VS Code or Gemini CLI to Countly. Ask about your data, build reports, even set up Countly in your app from your editor. The assistant acts as the person who approved it, with no API key to hand out.

In this demo deployment, eleven people work with Countly from their own assistants, under rules an admin set once.

Part of AI

## Ask the assistant you already use

Countly becomes one of its tools, so the answer comes from your projects, in the conversation you are already having.

“Why did signups drop on Android last week?” Analysis The assistant queries events, funnels, retention and crashes in the projects you can see, and answers with the numbers.

“Build a cohort of drivers who stopped charging in the app.” Changes With change access, it creates cohorts, funnels, dashboards and more, as you, in your projects.

“Set up Countly in this app.” Implementation In a coding assistant, it plans the events with you, writes the SDK code and checks the data arrives.

“What did we ship to push last month, and how did it do?” Engagement Campaigns, journeys and their results, read in the same conversation as the analytics behind them.

From your editor

## From an empty app to verified analytics

Four commands in a coding assistant such as Claude Code, Cursor or VS Code take an app from questions to a working, checked implementation.

- 01 Plan It asks about your product, reads what the app already sends, writes a plan into the repository, and stops for your approval.
- 02 Implement analytics It writes the SDK setup, consent, identity, sessions, views, events, user properties and crash reporting from the approved plan.
- 03 Implement experience It wires the SDK for journeys, in-app content, feedback, remote config, experiments and push, and builds what the plan asks for.
- 04 Verify It checks the planned data arrives, sets the planned events live, and builds the funnels, cohorts and dashboards the plan lists.
Set up once

## Connect in a minute. Govern it for good.

Each person connects their own assistant. An admin decides who may, what assistants may do, and for how long.

- Connect in a minute Copy the MCP URL, follow your assistant’s steps, sign in and approve. No API key, no token to paste.
- Decide who and how much Everyone, or the people and groups you choose. Read only, read and change, or full admin for administrators.
- See every connection Who connected which assistant, with what access, when it was last used and when it expires. Revoke any of them.
- See how it is used Every tool call recorded as an event: how many, by whom, through which assistant, and how often it succeeds.
For your security review

## Access you can explain to your security team

An assistant is another way for a person to use Countly, never a way around their rights.

- 01 Off until you turn it on A new server has MCP off, and every connection is read only until an admin allows changes. Default
- 02 Acts as the person An assistant gets the projects and rights of the person who approved it, never more, checked on every call. Every call
- 03 No keys to leak People sign in with their usual login and approve on a consent screen that names the assistant. Sign-in
- 04 Connections expire After 7, 30 or 90 days, or when revoked, up to the longest an admin allows. Revoking cuts access at once. Lifetime
- 05 Limit who can connect Choose the people and groups, the assistant hosts allowed, and whether unknown assistants may register. Admin
- 06 Every change on record Changes made through an assistant appear in the audit log under the person, with the assistant they came through. Audit
Works with

## MCP Server, with the rest of Countly

Every feature reads the same live data, so an answer in MCP Server doesn’t stop there. These are the handoffs built in.

[All features](https://countly.com/platform/features)

Audit Logs

Every change an assistant makes is recorded under the person, with the assistant it came through.

Open

[(Audit Logs Every change an assistant makes is recorded under the person, with t](https://countly.com/feature/audit-logs)

AI Agent Cee

Cee is the analyst built into Countly. MCP brings the same data to the assistant you already use.

Open

[(AI Agent Cee Cee is the analyst built into Countly. MCP brings the same data to](https://countly.com/feature/ai-agent-cee)

Drill

Assistants run Drill queries and saved queries, within the person’s projects.

Open

[(Drill Assistants run Drill queries and saved queries, within the person’s proje](https://countly.com/feature/drill)

Data Manager

An implementation plan is kept on the server as planned events, set live once the data arrives.

Open

[(Data Manager An implementation plan is kept on the server as planned events, se](https://countly.com/feature/data-manager)

Enterprise Access

Who may connect an AI assistant, and at what level, is set in Users & groups.

Open

[(Enterprise Access Who may connect an AI assistant, and at what level, is set in](https://countly.com/feature/access-control)

Data ownership

## Choose the model your data goes to.

Whatever an assistant reads from Countly is read by the model behind it. MCP is an open standard, so that model can be one you run yourself.

[Data privacy](https://countly.com/platform/data-privacy)

### Bring your own model

Connect an assistant on a model you host, or one deployed privately for your organization. Any MCP client that signs in the standard way can connect, and you can allow only your own hosts.

### Keep it on your network

An assistant running inside your network reaches a Countly server that is not exposed to the internet. Only cloud assistants such as Claude and ChatGPT need a public address.

### Or leave it out entirely

A build of Countly without the AI features has no MCP server at all, for deployments where no assistant may connect.

ISO 27001 Certified

ISO 27017 Certified

ISO 27018 Certified

SOC 2 Type II examined

TISAX® Participant*

*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at [enx.com/tisax](https://enx.com/tisax)
