Skip to main content
Glama
gambot-ai

gambot-mcp

Official
by gambot-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to gambot-mcp

No user-submitted related servers found.

    Related Servers

    • whatsapp-mcp-server

      FredShred7
      A
      license
      A
      quality
      D
      maintenance
      Connects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.
      18
      11 npm
      23
      MIT

    • WhatsApp MCP Server

      Malaccamaxgit
      A
      license
      Not graded
      quality
      C
      maintenance
      Integrates WhatsApp with AI agents, enabling message sending, chat search, media sharing, approval workflows, and activity summaries via any MCP client.
      1
      Apache 2.0

    • WhatsApp Business MCP Server

      EvandroSchechtel
      A
      license
      A
      quality
      Not graded
      maintenance
      Connects AI agents to the WhatsApp Business Cloud API, allowing them to send messages, manage templates, and retrieve account analytics. It facilitates automated customer interaction and marketing campaign management through the Model Context Protocol.
      16
      -
    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources