Skip to main content
Glama
Saiswrp7

clevertap-mcp

by Saiswrp7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to clevertap-mcp

No user-submitted related servers found.

    Related Servers

    • Klaviyo MCP Server

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Klaviyo for email marketing, including listing subscriber lists and retrieving campaign details via natural language.
      16 npm
      MIT
    • Mailjet MCP Server by mailgun

      Mailjet MCP Serverofficial

      mailgun
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to interact with Mailjet's contact, campaign, segmentation, statistics, and workflow APIs for managing email marketing operations through natural language.
      80 npm
      11
      Apache 2.0

    • OneSignal MCP Server

      chansearrington
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage OneSignal push notifications, email, SMS, and user management through natural language. Supports multi-channel messaging, segmentation, templates, analytics, and iOS Live Activities with 50+ tools for complete OneSignal API coverage.
      1
      -

    • GoHighLevel API v2 MCP Server

      kbgphp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage GoHighLevel sub-account CRM data, including contacts, custom fields, tags, workflows, and calendar configurations through natural language.
      20 npm
      MIT
    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

    B3.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources