clevertap-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEVERTAP_REGION | No | CleverTap Region (used for single-project configuration if CLEVERTAP_PROJECTS is not provided). Supported regions: in1, us1, eu1, sg1, aps3, mec1. | |
| CLEVERTAP_PASSCODE | No | CleverTap Passcode (used for single-project configuration if CLEVERTAP_PROJECTS is not provided). | |
| CLEVERTAP_PROJECTS | No | A serialized JSON string representing an array of project objects. Each object must include name, account_id, passcode, and region. Example: [{"name":"My App","account_id":"XXX","passcode":"YYY","region":"us1"}] | |
| CLEVERTAP_ACCOUNT_ID | No | CleverTap Account ID (used for single-project configuration if CLEVERTAP_PROJECTS is not provided). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
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 1 tool
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.
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.
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.
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.