Skip to main content
Glama
eyalbarash

@cig-chat/mcp

by eyalbarash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @cig-chat/mcp

No user-submitted related servers found.

    Related Servers

    • MCP-manychat

      vdloureiro
      F
      license
      A
      quality
      D
      maintenance
      MCP server for ManyChat API integration that enables Claude and other AI assistants to manage subscribers, tags, custom fields, flows, and send messages through natural language.
      17
      -

    • mautic-mcp

      Discret-Digital
      F
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that connects Claude AI to Mautic marketing automation, enabling contact management, email sending, campaign operations, and analytics via natural language.
      1
      -

    • WhatsApp Desktop MCP

      srijonbasak
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that connects WhatsApp Web to AI tools like Gemini and Claude, providing chat reading, messaging, and a local CRM with draft-and-approve workflows.
      MIT

    • WAHA MCP

      Ap0c123
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      A self-hosted MCP server that connects AI clients to WhatsApp via the WAHA HTTP API. It enables users to manage sessions, search contacts, and send or receive messages and media directly through natural language interfaces.
      18 npm
      -
    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

    C2.9/5.0

    Scored across 256 tools

    Disambiguation3/5

    Many tools share similar purposes, especially the broadcast/send families (e.g., broadcast_by_tag vs broadcast_by_user_id vs broadcast_to_list) and the integration get/set/clear triplets. The distinctions are real (by tag vs by user id vs list), but the sheer volume of near-identical names makes misselection likely, especially when an agent is not deeply familiar with the domain.

    Naming Consistency3/5

    All tools share the 'cigchat_' prefix, and most follow a domain_action_entity pattern (e.g., flow_create_user_field, subscriber_add_tag). However, there are inconsistencies: list endpoints sometimes omit the verb (e.g., flow_user_fields vs flow_create_user_field), and some tools use noun-first naming (e.g., flow_ai_task_info, flow_summary). The pattern is readable but not strictly uniform.

    Tool Count1/5

    256 tools is an extreme count, far beyond any reasonable MCP surface. Even for a broad customer-messaging platform, this volume overwhelms an agent's tool-selection context and makes it hard to discover the right tool. The calibration for 50+ tools is '1', and this server has 5x that.

    Completeness5/5

    The tool set provides comprehensive CRUD coverage across subscribers, tags, fields, products, orders, discounts, locations, templates, integrations, and workspace settings. It includes list, get, create, update, and delete operations for nearly every entity, plus broadcast/send capabilities and a catch-all api_call tool for anything not explicitly exposed. There are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources