Skip to main content
Glama
jetapi-mcp-server

jetapi-mcp-server

Official
by jetapi

JetAPI MCP Server

npm CI MCP Registry License: MIT

Official MCP server for JetAPI — send WhatsApp, Telegram, SMS and MAX messages, files and bulk mailings from AI agents like Claude, Cursor and VS Code.

Tools

Tool

Description

get_account

Full account info: balance, dispatch routing, sender names, subscription, WhatsApp/Telegram session status (token is masked)

get_balance

Balance, customer ID, dispatch routing channels and registered sender names

get_utm_tags

List UTM tags used to track dispatches

send_message

Send a text via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK or MAX — with cascade, scheduling, priority, reply-to and callbacks

send_bulk

Send the same message to many phone numbers at once

get_delivery_status

Status and details of a delivery, with the status explained in plain words

delete_delivery

Delete a delivered WhatsApp/Telegram message on all recipient devices

get_phone_info

Country, operator and normalized format of a phone number

send_file

Send a document, image, audio or video from a local path, URL or base64 (up to 100 MB)

create_webhook

Subscribe a URL to events: incoming messages, WhatsApp statuses, login/logout

get_webhook

Details of one webhook

list_webhooks

All registered webhooks

delete_webhook

Delete a webhook

update_webhook

Change a webhook's URL and/or event types

Related MCP server: lingtai-whatsapp

Get a token

Sign up at jetapi.io and copy the API token from the dashboard. To send through WhatsApp or Telegram, connect the messenger in the dashboard first.

Installation

Claude Desktop — one click

  1. Download jetapi-mcp-server.mcpb from the latest release.

  2. Double-click it (or drag it into Claude Desktop → Settings → Extensions).

  3. Paste your JetAPI token when asked. It is stored securely by Claude Desktop.

Claude Desktop — config file

Requires Node.js 18.17 or newer. Open Settings → Developer → Edit Config (claude_desktop_config.json) and add:

{
  "mcpServers": {
    "jetapi": {
      "command": "npx",
      "args": ["-y", "jetapi-mcp-server"],
      "env": { "JETAPI_TOKEN": "your_token_here" }
    }
  }
}

Restart Claude Desktop.

Claude Code

claude mcp add jetapi -- npx -y jetapi-mcp-server

The server needs JETAPI_TOKEN, so pass it when adding:

claude mcp add jetapi --env JETAPI_TOKEN=your_token_here -- npx -y jetapi-mcp-server

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "jetapi": {
      "command": "npx",
      "args": ["-y", "jetapi-mcp-server"],
      "env": { "JETAPI_TOKEN": "your_token_here" }
    }
  }
}

VS Code

Add to .vscode/mcp.json — VS Code will prompt for the token and keep it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "jetapi_token", "description": "JetAPI token", "password": true }
  ],
  "servers": {
    "jetapi": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "jetapi-mcp-server"],
      "env": { "JETAPI_TOKEN": "${input:jetapi_token}" }
    }
  }
}

MCP Registry

The server is listed in the official MCP Registry as io.github.jetapi/jetapi-mcp-server, so clients and catalogs that read the registry can install it directly.

Other MCP clients

Any client that supports stdio servers:

{
  "command": "npx",
  "args": ["-y", "jetapi-mcp-server"],
  "env": { "JETAPI_TOKEN": "your_token_here" }
}

Configuration

Variable

Required

Default

Description

JETAPI_TOKEN

yes

—

Bearer token from the JetAPI dashboard

JETAPI_BASE_URL

no

https://api.jetapi.io

API host

JETAPI_DEBUG

no

0

1 logs every request to stderr

Channels

dispatch_routing is an ordered list of channels. JetAPI tries them one by one and moves to the next channel only if delivery through the previous one fails. Without it, the default routing from your JetAPI dashboard is used.

Value

Channel

Recipient

whatsapp

WhatsApp

phone or whatsapp_lid

tdlib

Personal Telegram account

phone, username or tdlib_user_id (negative ID = group chat)

telegram

Telegram Bot

phone

sms

SMS

phone

notify

VK / OK notifications

phone

max

MAX messenger

phone

Usage examples

Ask Claude in plain language:

Say

Tool

"Show my JetAPI account — is WhatsApp connected?"

get_account

"How much money is left on JetAPI?"

get_balance

"Which UTM tags do I have?"

get_utm_tags

"Send a WhatsApp message to +7 999 123-45-67: Your order has shipped."

send_message

"Message @john_doe on Telegram that the meeting moved to 3 pm."

send_message (tdlib)

"Try WhatsApp first, then SMS: Your code is 4821."

send_message (cascade)

"Remind 79991234567 tomorrow at 09:00 UTC about the appointment."

send_message (scheduled)

"Send 'Sale starts today!' to 79991234567, 79997654321 and 995598464533."

send_bulk

"Was message 94396942 delivered?"

get_delivery_status

"Delete message 94396942."

delete_delivery

"Which operator is +995 598 464 533?"

get_phone_info

"Send ~/Documents/invoice.pdf to 79991234567 on WhatsApp."

send_file

"Send incoming WhatsApp messages to https://example.com/hook."

create_webhook

"Show webhook 57."

get_webhook

"List my webhooks."

list_webhooks

"Delete webhook 57."

delete_webhook

"Point webhook 57 to https://example.com/new-hook."

update_webhook

Behaviour

  • Parameters are sent as URL query parameters, as the JetAPI API expects; send_file uploads the file as multipart/form-data.

  • Incompatible parameters (e.g. a Telegram username without the tdlib channel, or scheduled_at in the past) are rejected before any request is sent.

  • HTTP 429 is retried up to 3 times with exponential backoff, honouring Retry-After.

  • 5xx responses are retried twice after 1 s — except for requests that send messages or create webhooks (send_message, send_bulk, send_file, create_webhook), so nothing is sent twice.

  • Requests time out after 30 seconds.

  • Errors are returned as readable tool errors, e.g. Invalid JetAPI token. Check your JETAPI_TOKEN. or Validation error: text: the text cannot be empty.

  • All logs go to stderr; stdout is reserved for the MCP protocol.

Development

git clone https://github.com/jetapi/jetapi-mcp-server.git
cd jetapi-mcp-server
npm install
cp .env.example .env   # put your token in .env
npm run build
npm start

Script

What it does

npm run dev

Run the TypeScript source directly

npm run inspector

Open the MCP Inspector with all tools

npm run check

Verify versions in package.json / server.json / manifest.json and that the server exposes all 14 tools

npm run build:mcpb

Build the Claude Desktop extension into build/jetapi-mcp-server.mcpb

Releasing

  1. Bump the version in package.json, server.json (both version fields) and manifest.json, and add a CHANGELOG.md entry.

  2. Merge to main, then push a tag: git tag v1.2.3 && git push origin v1.2.3.

  3. The Release workflow publishes to npm (trusted publishing with provenance), creates a GitHub release with the .mcpb bundle and updates the MCP Registry.

Privacy Policy

The extension runs locally, collects no analytics or telemetry, and sends data only to the JetAPI API to perform the actions you request. Your API token is stored by your MCP client (Claude Desktop keeps it in secure storage).

Questions: support@jetapi.io

License

MIT

Available Tools

14 tools
create_webhookCreate webhookA

Register a webhook URL to receive real-time notifications for specific JetAPI events (e.g. whatsapp_log_out, delivery status updates, incoming messages). Use it when the user wants their server, CRM or automation (n8n, Make, Zapier) to receive replies or react to WhatsApp/Telegram events.

Inputs: url (required), types (required).

delete_deliveryDelete deliveryA
DestructiveIdempotent

Delete a sent message from WhatsApp or Telegram (tdlib). Only works for messages with final 'Delivered' status. Deletion occurs on all recipient devices.

Only messages sent through JetAPI via the tdlib or whatsapp channels can be deleted; SMS cannot. Use it when the user asks to unsend or recall a message.

Inputs: delivery_id (required).

delete_webhookDelete webhookA
DestructiveIdempotent

Delete a webhook by ID. The webhook will stop receiving notifications.

Inputs: id (required).

get_accountGet accountA
Read-only

Get full JetAPI account information including token, balance, dispatch routing, sender names, subscription status and Telegram/WhatsApp sessions count. Use it to verify the token works, check whether the subscription is active, or diagnose undelivered messages (e.g. WhatsApp or Telegram not authorized). For just the balance use get_balance.

Inputs: no named parameters.

get_balanceGet balanceA
Read-only

Get JetAPI account balance, customer ID, available dispatch routing channels, and registered sender names. Use it when the user asks how much money is left, before a large mailing, or to find a valid sender_name for SMS.

Inputs: no named parameters.

get_delivery_statusGet delivery statusA
Read-only

Get the current status and full details of a specific message delivery by its ID. Returns status, operator info, phone, scheduled time, costs and more. Use it after send_message or send_file when the user asks whether a message was delivered or read, or why it failed — the status is explained in plain words.

Inputs: id (required).

get_phone_infoGet phone infoA
Read-only

Look up phone number information including country, mobile operator name and brand. Useful before sending to verify the number and determine routing. Also returns the number normalized to international format, e.g. when the user wrote it with spaces or brackets.

Inputs: phone (required).

get_utm_tagsGet UTM tagsA
Read-only

Get list of all UTM tags (utm_marks) configured in the JetAPI account for tracking message dispatches. Use it to reuse an existing label as utm_mark in send_message, send_bulk or send_file, so statistics stay grouped.

Inputs: no named parameters.

get_webhookGet webhookA
Read-only

Get details of a specific webhook by its ID: the URL it posts to and the event types it subscribes to.

Inputs: id (required).

list_webhooksList webhooksA
Read-only

List all registered webhooks for this JetAPI account. Use it to see where events are delivered or to find a webhook ID before updating or deleting it.

Inputs: no named parameters.

send_bulkSend bulk messageA

Send the same message to multiple phone numbers at once. Supports scheduling, UTM marks, dispatch routing cascade, Telegram usernames and tdlib user IDs.

Use it for announcements, campaigns or reminders to a list of recipients. For one recipient, or when a delivery ID is needed for tracking, use send_message.

Inputs: text (required), phones_numbers (required), utm_mark, usernames, +4 more.

send_fileSend fileA

Send a file (document, image, audio, video, contact) to a recipient via WhatsApp or Telegram. File is uploaded as multipart/form-data. Images under 10MB sent natively, larger files as download links active for 7 days.

Use it when the user wants to share a document, photo, voice message, video or contact card. Provide the file as exactly one of: file_path (local file), file_url (downloaded by the server) or file_base64 (with file_name).

Supported: pdf, doc, docx, ppt, pptx, xls, xlsx, zip, 7z; ogg, opus, mp3, aac, amr, 3gp; jpeg, png, webp; mp4; vcf. Max 100 MB. Recipient rules are the same as send_message.

Inputs: type, phone, caption, file_url, +15 more.

send_messageSend messageA

Send a text message via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK (notify), or MAX (max), with optional cascade fallback between channels. Supports scheduling, priority, reply-to, typing simulation, and delivery callbacks.

Use it when the user asks to text, message, notify or reply to one person or group chat. For many phone numbers use send_bulk; for documents, images, audio or video use send_file.

Recipient: phone is required, except for personal Telegram (dispatch_routing ["tdlib"]) where username or tdlib_user_id can be used instead, and WhatsApp where whatsapp_lid can be used.

Returns the delivery ID for get_delivery_status and delete_delivery.

Inputs: text (required), phone, priority, username, +10 more.

update_webhookUpdate webhookA
Idempotent

Update an existing webhook — change its URL or the list of event types it subscribes to. Pass only what should change; types replaces the whole list.

Inputs: id (required), url, types.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    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

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP 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
      85 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
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Kirimi WhatsApp API, enabling AI agents to send messages, broadcast, manage devices, and contacts.
      20
      232 npm
      MIT

    Appeared in Searches