In this demo deployment, eleven people work with Countly from their own assistants, under rules an admin set once.
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.
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?”
“Build a cohort of drivers who stopped charging in the app.”
“Set up Countly in this app.”
“What did we ship to push last month, and how did it do?”
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.
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.
- 01Default
Off until you turn it on
A new server has MCP off, and every connection is read only until an admin allows changes.
- 02Every call
Acts as the person
An assistant gets the projects and rights of the person who approved it, never more, checked on every call.
- 03Sign-in
No keys to leak
People sign in with their usual login and approve on a consent screen that names the assistant.
- 04Lifetime
Connections expire
After 7, 30 or 90 days, or when revoked, up to the longest an admin allows. Revoking cuts access at once.
- 05Admin
Limit who can connect
Choose the people and groups, the assistant hosts allowed, and whether unknown assistants may register.
- 06Audit
Every change on record
Changes made through an assistant appear in the audit log under the person, with the assistant they came through.
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 featuresData 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 privacyBring 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.
*Countly Ltd. is a TISAX® Participant. TISAX® is a registered trademark of and governed by ENX Association. Learn more at enx.com/tisax