Countly MCP for AI. Query User Behavior Using Natural Language
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Countly lets you monitor user behavior and app performance by connecting your analytics data directly to your AI agent. Track every user session, log custom actions, and run deep queries on behavioral metrics without leaving your chat window.
What your AI can do
Begin session
Starts tracking a new session for a specific user.
End session
Stops the current recorded user session.
Read drill
Runs complex filtering and deep analysis on your data, typically for enterprise use cases.
Start and stop tracking a user's activity to measure how long they stay engaged in the app.
Record custom events—like a purchase or clicking 'save'—with details about what happened and who did it.
Retrieve standard metrics, such as total sessions, number of unique users, or regional breakdowns.
Run advanced filters to isolate specific user groups or complex behavioral patterns within your dataset.
Modify core user information, like names or emails, directly in the analytics record.
Ask an AI about this
Waiting for input…
Countly: 8 Tools
Use these eight tools to manage the entire lifecycle of your product data—from starting a session to running complex segment reports.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Countly on VinkiusBegin Session
Starts tracking a new session for a specific user.
End Session
Stops the current recorded user session.
Read Drill
Runs complex filtering and deep analysis on your data, typically for enterprise use...
Read Events
Pulls specific records related to custom user actions or events that occurred in the...
Read Metrics
Retrieves general, high-level metrics like total sessions, unique users, or country...
Record Events
Logs specific actions that happen inside the application, including custom data keys and counts.
Update Session
Extends an existing session to keep the user active in the tracking system.
Update User Details
Modifies stored information about a specific user, such as their name or email...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Countly, then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Countly. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 8 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The Manual Data Audit Nightmare
Right now, figuring out why a feature isn't being adopted means navigating through three different dashboard tabs: one for user totals, one for event logs, and another for segment breakdowns. You end up exporting five separate CSV files and spending an hour in Excel just trying to match the data points.
With this MCP, you skip the clicking entirely. Instead, you simply ask your agent: 'Show me all users who saw the dashboard but never clicked the export button.' The answer comes back immediately, giving you a clear list of insights without ever opening a spreadsheet.
The Power of Specific Event Logging with record_events
Before this MCP, logging specific user actions meant writing complex tracking code for every single button. If you wanted to know how many times someone clicked 'download PDF' versus 'view pricing,' you had to build a whole new dashboard just for those two things.
Now, you just tell the agent to track it. You use `record_events`, and that action is logged instantly and permanently. Your data is immediately richer because you captured the precise moment and context of the user's interaction.
What your AI can actually do with this
Need to know why users are dropping off? This MCP connects your Countly instance, letting you query product behavior using simple conversation. Instead of digging through complex dashboards or exporting CSVs, you just ask your agent about user activity. You can track when a session starts and ends, log specific actions like button clicks or feature views, and even update user profiles on the fly.
This ability to turn raw analytics data into conversational answers is huge. Through Vinkius, you get access to this tool alongside thousands of others, making it your central hub for all data sources. It’s about getting immediate insights—figuring out which features are used most often or finding exactly where users struggle.
019e5d0d-8f97-7006-b03f-8ea03fe587ea Here's how it actually works
The bottom line is that your AI agent talks directly to your analytics backend, so you get answers without opening a separate dashboard.
First, subscribe to this MCP and provide your Countly Server URL along with the necessary API keys (App Key, App ID).
Next, you talk to your AI client using natural language. You ask questions like 'What were the total sessions last week?' or 'Record a purchase event for user X.'
The MCP runs those instructions against Countly and sends back structured, conversational data about what happened.
Who is this actually for?
Product Managers who need quick KPIs and Growth Teams tracking funnels. This MCP solves the pain of having to jump between dashboards and spreadsheets just to answer 'why' or 'how many.'
Monitors key performance indicators (KPIs) and feature adoption rates without navigating complex, multi-tabbed dashboards.
Performs quick audits or segmentations by asking the agent to pull specific data points using natural language queries.
Tracks conversion funnels and user profile updates to pinpoint where marketing efforts are succeeding or failing.
What Changes When You Connect
You get real-time session visibility. Use begin_session and end_session to track engagement duration instantly, so you never lose track of an active user flow.
Pinpoint feature usage with custom logging. The record_events tool lets you log specific actions (like 'downloaded PDF' or 'used filter') for granular analysis.
Bypass surface-level reports using read_metrics. You can ask the agent for aggregate data—total sessions by country, for example—without opening a single dashboard tab.
Isolate niche user groups with precision. The read_drill tool lets you run complex filters to analyze deep segments that standard reporting tools miss.
Maintain clean user records using update_user_details. You can keep your data accurate by letting the agent update names or emails when they change.
Keep sessions running smoothly. If a user is active for a long time, use update_session to extend their tracked time without manually refreshing anything.
See it in action
Investigating sudden drop-off points
A PM notices usage dropped after the last release. They ask the agent: 'What were the recorded events immediately before users stopped logging in?' The agent uses read_events to pull a list of actions, helping them identify if a specific required step broke.
Auditing onboarding completion
A Growth Marketer needs to know how many new users actually reached the final stage of signup. They ask the agent to check 'successful signups' metrics, triggering read_metrics for a clean count.
Tracking complex user roles
A Data Analyst needs to filter all data only for users who are both in California and used the premium feature. They ask the agent to run an advanced query, using read_drill to get a precise segment count.
Simulating user interaction flow
A tester wants to map out the full journey of a new user. They instruct their AI client to simulate a path: 'Begin session, record event for viewing dashboard, update user details with test email.' The agent runs begin_session, then record_events, and finally update_user_details.
The honest tradeoffs
Confusing general stats with specific actions
Asking 'How many times did users click the save button?' and getting only a general session count, because standard reporting tools can't drill down to that action.
You need to use read_events or record_events. These tools are built specifically to log and retrieve data for discrete user actions like 'click save,' giving you the exact count you need.
Using simple queries for deep analysis
Running a basic query that only aggregates total users, missing out on critical filters like device type or specific region grouping.
Don't rely just on read_metrics. For complex filtering across multiple variables, you must call the specialized read_drill tool to get truly deep-dive analysis.
Assuming a single API call handles everything
Thinking that one command will both extend a session and log an event. The system requires separate instructions for each action.
Remember the lifecycle: Use update_session to extend time, but always use record_events separately if you want to capture a specific user action during that time.
When It Fits, When It Doesn't
Use this MCP when your business problem is behavioral. If you need to know how users moved through the product or why they abandoned something, this tool is necessary. It handles the complexity of session state and event logging. Don't use it if you just need a simple count (e.g., 'How many total signups today?'). For that basic query, general analytics platforms are fine. However, if those basic counts aren't detailed enough—if you can't segment by custom action or time-bound behavior—then this MCP is the right choice.
Questions you might have
How does Countly MCP help me track a session? +
You start tracking with begin_session when the app loads. You can keep it active using update_session and stop it with end_session once the user leaves.
Can I use read_metrics for detailed event data? +
No, they do different things. Use read_metrics for broad numbers (like total users). If you need to know about a specific action, like 'purchase,' you must use read_events.
What if I need to update user data mid-flow? +
You can modify records using the update_user_details tool. This allows you to change a user's name or email address directly from your chat conversation, keeping your dataset current.
Is read_drill better than read_metrics? +
Yes, generally. read_metrics gives simple counts; read_drill lets you run much more advanced, complex filtering across multiple data dimensions for deeper analysis.
When should I use `update_session` instead of letting time pass? +
You use update_session when you need to confirm user activity and extend the session duration actively. This is crucial for accurate tracking, especially if your app has periods of inactivity but the user remains engaged. It prevents premature session termination reported by the system.
How do I properly use `record_events` when my action has multiple key-value pairs? +
You pass custom keys and corresponding values as structured data points within the record_events call. This allows you to track detailed context, like grouping an event by both a user ID and a specific feature version simultaneously. It makes your analytics much richer.
If I run into issues using `read_metrics`, what should I check first? +
First, confirm the API Key and App ID you provided to this MCP are current and active in Countly. Most metric retrieval failures come down to expired or revoked credentials. Re-verify your connection details before assuming a data issue.
Does using `read_drill` require special licensing or setup? +
Yes, accessing advanced filtering via the read_drill tool requires an Enterprise Edition license for Countly. If you get an error related to scope or permission, it means your account needs that specific upgrade to perform deep-dive analysis.
How can I retrieve aggregated data like total sessions or user counts? +
You can use the read_metrics tool. Simply specify the method (e.g., 'sessions' or 'users') to get the aggregated analytics data from your Countly instance.
Can I record custom user actions with metadata? +
Yes! Use the record_events tool. You can provide a device ID and an array of event objects containing keys, counts, and segmentation details to track specific interactions.
Does this server support advanced filtering for Enterprise users? +
Yes, if you have the Enterprise Edition, you can use the read_drill tool to perform complex queries and segmentation using the Drill API.
We've already built the connector for Countly. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 8 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.