clevertap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEVERTAP_REGION | No | Your CleverTap region (e.g., in1, us1, eu1) | in1 |
| CLEVERTAP_PASSCODE | Yes | Your CleverTap passcode | |
| CLEVERTAP_ACCOUNT_ID | Yes | Your CleverTap account ID |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_campaignA | Create a CleverTap campaign. Supports push, email, SMS, WhatsApp, webpush, webhook, and notification inbox. Set estimate_only=true to preview reach without sending. |
| stop_campaignB | Stop a scheduled or running CleverTap campaign by its ID. |
| get_campaign_reportC | Get message delivery reports for campaigns within a date range. |
| send_pushB | Send a push notification directly to specific users by identity or objectId. |
| send_emailC | Send an email directly to specific users. |
| send_smsC | Send an SMS directly to specific users. |
| send_whatsappB | Send a WhatsApp message directly to specific users via CleverTap. |
| upload_eventsC | Upload user events to CleverTap from an external system. Max 1000 events per call. |
| get_eventsB | Download user events from CleverTap for a date range. Returns a cursor for pagination. |
| get_events_pageA | Fetch the next page of events using a cursor returned by get_events. |
| get_event_countC | Get aggregate count of a specific event within a time period. |
| get_profileA | Get a single user profile by email, custom identity, or CleverTap objectId. |
| get_profilesC | Download a list of user profiles based on an event they performed. Returns a cursor. |
| get_profiles_pageA | Fetch the next page of profiles using a cursor from get_profiles. |
| upload_profilesC | Upload or update user profiles in CleverTap. |
| get_profile_countC | Get count of user profiles that performed a specific event. |
| get_realtime_countsB | Get real-time counts of users currently performing an event (live data). |
| get_top_property_valuesC | Get the top N values for an event property over a date range. |
| get_trendsB | Get event trends (day-by-day counts) over a date range, optionally grouped by a property. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action: profiles, events, campaigns, messaging channels, and analytics. Even similar tools like get_profile_count vs get_event_count are clearly differentiated by what they count (users vs events) and time context (live vs historical). No two tools appear to overlap in a way that would cause misselection.
All tool names follow a clear verb_noun pattern with consistent verbs: get, create, stop, send, upload. The object nouns are specific (profile, campaign, event, trends, etc.). Minor variations like get_realtime_counts vs get_event_count do not break the pattern; everything is snake_case and starts with a verb.
19 tools is on the higher end but justified for a customer engagement platform that spans profiles, events, campaigns, messaging channels, and analytics. Each tool addresses a distinct need, though the count could be slightly trimmed (e.g., merging pagination helpers). Still, it feels appropriately scoped and not bloated.
The surface covers the core lifecycle: profile creation/update/retrieval, event upload/query, campaign create/stop/report, and direct messaging across multiple channels. Minor gaps exist, such as no update_campaign or delete_profile/delete_event, but these are not critical for most workflows. Overall, the domain is well covered without dead ends.