Countly MCP integration for AI agents.
Connect AI agents to Countly through 6 structured actions, including get app details, get current user, and get dashboard analytics. Review authentication, i…
- ACTION CONTRACTS
- 6
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Countly integration exposes
The Countly Agent App exposes 6 provider-backed actions for data & analytics work. Its current contract lets an authorized agent retrieve countly application metadata and its user access lists, retrieve the countly user associated with the connected api key, and retrieve countly dashboard analytics for an application. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Countly account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Countly capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_app_detailsREADRetrieve Countly application metadata and its user access lists.
INPUTS: appId
get_current_userREADRetrieve the Countly user associated with the connected API key.
get_dashboard_analyticsREADRetrieve Countly dashboard analytics for an application.
INPUTS: appId
list_appsREADList Countly applications owned by the connected user.
list_event_analyticsREADRetrieve event analytics for one or more Countly event keys.
INPUTS: appId / event / events / segmentation / period
list_session_analyticsREADRetrieve session analytics data points for a Countly application and period.
INPUTS: appId / period
INPUT CONTRACTS
Know what the action needs before it runs.
get_app_details
appIdOPTIONAL- The Countly application ID.
get_dashboard_analytics
appIdOPTIONAL- The Countly application ID.
list_event_analytics
appIdREQUIRED- The Countly application ID.
eventOPTIONAL- A single Countly event key to query.
eventsOPTIONAL- Multiple Countly event keys to query.
segmentationOPTIONAL- The event segmentation key to break results down by.
periodOPTIONAL- The Countly period, such as month, 30days, 7days, yesterday, hour, or a JSON array of start and end timestamps.
list_session_analytics
appIdREQUIRED- The Countly application ID.
periodOPTIONAL- The Countly period, such as month, 30days, 7days, yesterday, hour, or a JSON array of start and end timestamps.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get App Details
Retrieve Countly application metadata and its user access lists. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_app_detailsVerify with Get Current User
Retrieve the Countly user associated with the connected API key. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_current_userSAFETY BOUNDARY
Operate Countly with explicit limits
- Authorize Countly with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Countly data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Countly rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Countly task completed successfully.
CONNECTION MODEL
API key
Countly account API key sent as the api_key query parameter. Find it in your Countly account Management menu: https://support.countly.com/hc/en-us/articles/360037092072-Server-API-Reference.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Countly.