Which integrations are available for this server?

Supports push notification management for Android devices through CleverTap's platform, including device token registration and test push sending to Android devices. Supports push notification management for iOS devices through CleverTap's platform, including device token registration and test push sending to iOS devices. Provides TypeScript-based tools for programmatic interaction with CleverTap's API, including type-safe operations for events, profiles, campaigns, and reports.

How do I use clevertap-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@clevertap-mcp show me the performance report for my winter sale campaign" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

clevertap-mcp

by ralphcorleone

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

clevertap-mcp

A Model Context Protocol (MCP) server for the CleverTap REST API. Exposes CleverTap's user profiles, events, campaigns, and reports as tools that any MCP-compatible AI assistant (Claude, Cursor, etc.) can call directly.

Features

Multi-project — manage multiple CleverTap accounts from a single server instance
Guided setup — if no project is configured, clevertap_configure walks you through the process
Full API coverage — events, profiles, campaigns, and reports
Async polling — long-running operations (event/profile counts) are polled automatically

Related MCP server: Mixpanel MCP Server

Tools

Events

Tool	Description
`clevertap_upload_events`	Upload one or more events for a user
`clevertap_get_events`	Query event data with filters
`clevertap_get_events_cursor`	Fetch the next page of event results via cursor
`clevertap_get_event_count`	Get the total count of an event (with async polling)

Profiles

Tool	Description
`clevertap_upload_profiles`	Create or update user profiles
`clevertap_get_profile`	Look up a single user by identity, email, or objectId
`clevertap_get_profiles_by_event`	Get profiles of users who performed an event
`clevertap_get_profiles_cursor`	Fetch the next page of profile results via cursor
`clevertap_delete_profile`	Delete a user profile
`clevertap_upload_device_token`	Register a push token for a user
`clevertap_get_profile_count`	Count profiles matching a segment
`clevertap_demerge_profiles`	Split merged profiles apart
`clevertap_subscribe`	Subscribe/unsubscribe a user to channels
`clevertap_disassociate_phone`	Remove a phone number from a profile

Campaigns

Tool	Description
`clevertap_get_campaigns`	List campaigns within a date range
`clevertap_get_campaign_report`	Get delivery and engagement stats for a campaign
`clevertap_stop_campaign`	Stop a running campaign
`clevertap_create_campaign`	Create and launch a campaign

Reports

Tool	Description
`clevertap_get_message_report`	Message-level delivery report
`clevertap_get_top_property_count`	Top property value counts for an event
`clevertap_get_event_trend`	Daily/weekly/monthly trend for an event
`clevertap_get_dau`	Daily active users trend
`clevertap_get_uninstall_report`	Uninstall trend report
`clevertap_get_real_time_counts`	Real-time active user counts

Generic

Tool	Description
`clevertap_request`	Make any raw REST API request
`clevertap_poll`	Poll a pending async request by `req_id`

Web / Browser

Tool	Description
`clevertap_web_login`	Open a Chromium window and capture the dashboard session cookie + CSRF token after manual login (supports SSO and 2FA)
`clevertap_web_session_status`	Check whether a web session has been captured for a project, and when it was obtained
`clevertap_web_request`	Make an authenticated request to any CleverTap dashboard endpoint using the captured session
`clevertap_get_campaigns_ui`	List campaigns from the dashboard UI API — richer data than the REST API (status, sent, impressions, clicks, edit URL)
`clevertap_send_test_push`	Send a test push notification to a specific device token. Accepts the push token from `clevertap_get_profile` (`platformInfo[].push_token`), the target platform (`ios`/`android`), the push channel name, and an optional deep link URL.

Prerequisite for web tools: install the Playwright Chromium binary once after npm install:
npx playwright install chromium

Installation

git clone https://github.com/your-org/clevertap-mcp.git
cd clevertap-mcp
npm install
npx playwright install chromium   # required for web/browser tools
npm run build

Configuration

The server reads project credentials from the CLEVERTAP_PROJECTS environment variable — a JSON array of project objects:

[
  {
    "name": "My App - Production",
    "account_id": "XXX-XXX-XXXX",
    "passcode": "YYY-YYY-YYYY",
    "region": "us1"
  },
  {
    "name": "My App - Staging",
    "account_id": "AAA-AAA-AAAA",
    "passcode": "BBB-BBB-BBBB",
    "region": "us1"
  }
]

Supported regions: in1, us1, eu1, sg1, aps3, mec1

Single-project fallback

You can also use individual environment variables for a single project:

CLEVERTAP_ACCOUNT_ID=XXX-XXX-XXXX
CLEVERTAP_PASSCODE=YYY-YYY-YYYY
CLEVERTAP_REGION=us1

Adding to Claude Desktop

In your claude_desktop_config.json (or ~/.claude.json):

{
  "mcpServers": {
    "clevertap": {
      "command": "node",
      "args": ["/absolute/path/to/clevertap-mcp/dist/index.js"],
      "env": {
        "CLEVERTAP_PROJECTS": "[{\"name\":\"My App\",\"account_id\":\"XXX-XXX-XXXX\",\"passcode\":\"YYY-YYY-YYYY\",\"region\":\"us1\"}]"
      }
    }
  }
}

Important: CLEVERTAP_PROJECTS must be a serialized JSON string (not a native JSON object) inside the env block.

Development

npm run build      # compile TypeScript → dist/
npm run dev        # watch mode
npm start          # run compiled server

Project structure

src/
  index.ts          # MCP server entry point, project config, tool registration
  client.ts         # CleverTap REST API HTTP client
  tools/
    events.ts       # Event upload and query tools
    profiles.ts     # Profile management tools
    campaigns.ts    # Campaign tools
    reports.ts      # Analytics and report tools
    generic.ts      # Raw request / poll tools
    web.ts          # Browser session tools via Playwright (login, campaigns UI, test push)

License

MIT

Available Tools

1 tool

clevertap_configureA

CleverTap MCP has no project configured yet. Call this tool with your CleverTap credentials and it will return the exact configuration snippet to paste into your MCP settings — then restart the server to activate all tools.

ParametersJSON Schema

Name	Required	Description	Default
`account_id`	Yes	CleverTap Account ID — found in the CleverTap dashboard under Settings → Accounts
`passcode`	Yes	CleverTap Passcode — found in the CleverTap dashboard under Settings → Accounts
`region`	No	Data residency region: in1 (India), us1 (US), eu1 (Europe), sg1 (Singapore), aps3 (Asia-Pacific), mec1 (Middle East)	in1
`project_name`	No	Label for this project. Use any short name (e.g. "production", "staging"). Defaults to "default".	default

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly explains that this tool returns a configuration snippet rather than performing the configuration directly, which is valuable behavioral context. It also mentions the need to restart the server afterward. However, it doesn't disclose potential authentication requirements beyond credentials, rate limits, or error behaviors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is perfectly concise with two sentences that each serve a clear purpose: the first establishes the context and action, the second explains the outcome and next steps. There's zero wasted language, and it's front-loaded with the essential information about when and why to use the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a configuration tool with no annotations and no output schema, the description provides good context about the tool's purpose and usage flow. It explains what happens (returns configuration snippet) and what needs to happen next (restart server). However, it doesn't describe the format of the returned snippet or potential error conditions, leaving some gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description doesn't add any additional parameter semantics beyond what's in the schema descriptions. It mentions 'credentials' generally but doesn't elaborate on specific parameters. This meets the baseline expectation when schema coverage is complete.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action: 'Call this tool with your CleverTap credentials and it will return the exact configuration snippet to paste into your MCP settings.' It explicitly addresses the initial setup scenario ('no project configured yet') and distinguishes this as a one-time configuration tool. The verb 'configure' is specific and the resource is the CleverTap MCP project setup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool: 'CleverTap MCP has no project configured yet.' It also specifies the follow-up action required: 'then restart the server to activate all tools.' Since there are no sibling tools mentioned, the description appropriately focuses on the specific use case without needing to differentiate from alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updatev1.0.0Apr 13, 2026
- First observedclevertap_configure

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored 2026-04-13 08:05 across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The tool's purpose is clearly defined as a configuration setup step.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'clevertap_configure' follows a clear verb_noun pattern, and there are no other tools to create inconsistency.

Tool Count2/5

A single tool is too few for a server intended to interact with CleverTap, as it suggests the server is not yet fully functional or lacks operational capabilities. This is a significant mismatch for the apparent scope of a CleverTap integration.

Completeness1/5

The tool set is severely incomplete for a CleverTap MCP server, as it only provides a configuration tool and no actual operational tools for interacting with CleverTap data or features. This leaves obvious gaps in the domain coverage.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

anotherai
dev.anotherai
MCP server for building and testing AI agents with multi-model experimentation and insights.
Agent Orchestration Autonomous Agents Testing & QA Tools
2
Artificial Wit AIOAuth
com.artificialwit
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
ERP Systems CRM Knowledge & Memory
2
OneSchema MCP Server
co.oneschema
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Data Platforms App Automation
1
ZapierOAuth
com.zapier
Hosted MCP server connecting AI assistants to 9,000+ apps and 40,000+ actions via Zapier.
App Automation Workplace & Productivity
2297

Related MCP Servers

ActiveCampaign MCP Server
Customer Data Platforms Marketing App Automation
mmarqueti
A
license
B
quality
D
maintenance
An MCP server that enables AI tools to interact with ActiveCampaign API, allowing contact management and tracking event analysis through natural language queries.
Updated a year ago (2025-07-06 14:38 UTC)
5
1
MIT
Mixpanel MCP Server
Monitoring Databases Search
T-Campbell18
A
license
B
quality
D
maintenance
An MCP server that provides access to the Mixpanel REST API, enabling AI agents to query events, funnels, retention data, and user profiles. It allows users to perform complex analytics tasks and export raw event data through natural language prompts.
Updated 6 months ago (2026-03-13 03:28 UTC)
16
5 npm
MIT
ClickUp MCP
Project Management Workplace & Productivity
sebastienheyd
A
license
Not graded
quality
B
maintenance
MCP server enabling AI assistants to interact with ClickUp workspaces, including task management, comments, time tracking, and document operations.
Updated a month ago (2026-08-17 09:52 UTC)
12 npm
MIT
CleverTap MCP
Customer Data Platforms Marketing
YASH-YADAV-dynamo
F
license
Not graded
quality
C
maintenance
Read-only AI analytics assistant for CleverTap via MCP, enabling querying of events, profiles, campaigns, and realtime data without write endpoints.
Updated 2 months ago (2026-07-13 18:17 UTC)
10 npm
-

Tool	Description
`clevertap_configure`	Guided setup to add a project or generate the `CLEVERTAP_PROJECTS` config
`clevertap_list_projects`	List all configured projects and their regions

clevertap-mcp

Features

Tools

Meta

Events

Profiles

Campaigns

Reports

Generic

Web / Browser

Installation

Configuration

Single-project fallback

Adding to Claude Desktop

Development

Project structure

License

Available Tools

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

ActiveCampaign MCP Server

Mixpanel MCP Server

ClickUp MCP

CleverTap MCP