Skip to main content
Glama
Sign In
gambot-mcp

gambot-mcp

Official
by gambot-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gambot-mcp

No user-submitted related servers found.

    Related Servers

    • ConverZAP MCP server

      ConverZAP MCP serverofficial

      ConverZAP
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and agents to work with WhatsApp through the official WhatsApp Business Platform (Meta Cloud API), exposing tools to search contacts, read conversations, send messages and approved templates, manage CRM deals, run campaigns, enroll contacts in automations and pull reports. All actions run through a hosted public API, so they honor the account's existing roles, scopes and rate limits, with write operations supporting dry-run validation and confirmation for destructive calls.
      1
      MIT

    • ApiEnvios

      Otavio1661
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage WhatsApp instances, send messages and campaigns, handle incoming messages, webhooks, members, and metrics through 30 authenticated tools, with an optional WhatsApp-to-assistant bridge.
      Apache 2.0
    • zapzap-mcp

      zapzap-mcpofficial

      zapzapapi
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to send and read WhatsApp messages, manage instances, chats, groups, media, polls, buttons, and webhooks through a managed WhatsApp API with 25 curated tools.
      25
      MIT

    • DataCrazy

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage omnichannel CRM data (WhatsApp, Instagram, Facebook) via the official API, including leads, deals, pipelines, activities, tags, products, conversations, lists, attachments, and notes.
      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

    C2.9/5.0

    Scored across 78 tools

    Disambiguation4/5

    Most tools are cleanly separated by resource and action, so an agent can usually pick the right one. The main ambiguity is around the campaign/messaging cluster: gambot_send_campaign, gambot_run_campaign, gambot_test_campaign, gambot_send_campaign_from_excel, and gambot_send_template could be confused, though the descriptions do draw useful boundaries.

    Naming Consistency5/5

    All tool names follow the gambot_<verb>_<object> snake_case pattern with consistent verbs like get, list, create, update, delete, send, run, and test. Even longer names like get_signature_link and send_campaign_from_excel are predictable extensions of the same convention.

    Tool Count1/5

    78 tools is far beyond a practical MCP surface and beyond the 50+ calibration threshold. The server merges many products (CRM, campaigns, documents, signatures, billing, onboarding, payments) into one namespace, which will likely overwhelm agent context and select a request. Consolidating related tools into smaller servers or higher-level operations would be far more appropriate.

    Completeness2/5

    The surface is broad but has significant lifecycle gaps: no list_contacts, no delete/update for many templates, no deletion for quotes/invoices/orders/tasks/leads/cases, and form/document/signature tools are mostly read/link-only rather than fully managed. These gaps will typically cause agent failures when users attempt standard cleanups or changes.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources