Skip to main content
Glama
jetapi

jetapi-mcp-server

Official
by jetapi

Related Servers

Alternatives to jetapi-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      D
      maintenance
      MCP server for ManyContacts WhatsApp Business CRM that enables AI agents to manage contacts, send messages, run campaigns, and configure auto-replies through comprehensive CRM operations.
      55
      55 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Kirimi WhatsApp API, enabling AI agents to send messages, broadcast, manage devices, and contacts.
      19
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for interacting with the official Meta WhatsApp Business Platform/Cloud API, enabling sending messages, managing contacts, templates, and handling webhook callbacks.
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      Enables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.
      18
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server for Leporis WhatsApp Business platform, enabling AI agents to send and read WhatsApp messages through exposed REST API tools.
      -
    • A
      license
      B
      quality
      C
      maintenance
      MCP server that enables AI agents to operate WhatsApp via Visto Azul API: send text, media, PIX charges, manage campaigns and contacts, and configure webhooks using natural language.
      11
      9 npm
      MIT

    TDQS

    A4.3/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action (balance vs account vs delivery vs webhooks). The only potential confusion is get_balance vs get_account, but the descriptions explicitly differentiate them, and send_message vs send_bulk vs send_file are well delineated.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: get_*, send_*, create_*, list_*, update_*, delete_*. The verbs are predictable and the nouns clearly indicate the resource, making the API surface easy to navigate.

    Tool Count5/5

    14 tools is well within the ideal range for a messaging API server. Each tool covers a distinct operation: account info, messaging (single, bulk, file), delivery tracking, phone lookup, and webhook management. No tool feels redundant or unnecessary.

    Completeness4/5

    The tool surface covers the core messaging lifecycle well: send (message/bulk/file), track (get_delivery_status), and delete (delete_delivery). Webhook CRUD is complete. Minor gaps include no explicit tool for listing sent messages or managing contacts, but these are not essential for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues