JetAPI

io.github.jetapiPublished by GitHub account jetapiv1.0.3Updated Oct 24, 2026

Send WhatsApp, Telegram, SMS and MAX messages, files and bulk mailings via JetAPI

VerifiedSTDIODesktop onlyProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

JetAPI lets an assistant send WhatsApp, Telegram, SMS, VK/OK and MAX messages, files and bulk mailings, and manage delivery webhooks, through a JetAPI account.

What you can do
  • Send text messages over WhatsApp, Telegram (personal account or bot), SMS, VK/OK and MAX, with channel cascade, scheduling, priority and reply-to
  • Send the same message to many phone numbers at once, and send documents, images, audio or video from a local path, URL or base64
  • Check delivery status in plain words, delete a delivered WhatsApp/Telegram message on recipients' devices, and look up a phone number's country and operator
  • Read account details, remaining balance, dispatch routing, sender names and UTM tags
  • Create, list, inspect, update and delete webhooks for incoming messages, WhatsApp statuses and login/logout events
When to use it
Useful when you want an AI assistant to actually deliver notifications, order updates, reminders or bulk announcements to customers over messaging channels, or to wire incoming messages into your own endpoint via webhooks, using an existing JetAPI account.
Requirements
Runs locally over stdio via npx (Node.js 18.17 or newer) or as a Claude Desktop extension bundle. Requires a JetAPI account and a bearer token in JETAPI_TOKEN; WhatsApp or Telegram must be connected in the JetAPI dashboard before sending through them. Optional JETAPI_BASE_URL and JETAPI_DEBUG. Network access to the JetAPI API.
Before you install
Sending messages, bulk mailings and files spends the account balance and contacts real recipients, and messages cannot be recalled except via delete_delivery for WhatsApp/Telegram. Webhook tools create, change and delete subscriptions. The JETAPI_TOKEN is a bearer credential that grants access to the account; keep it out of shared config files. Message content, files and phone numbers are sent to the JetAPI service.

Installation

In SourceWeft

  1. Open JetAPI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

ToolDescription
get_accountFull account info: balance, dispatch routing, sender names, subscription, WhatsApp/Telegram session status (token is masked)
get_balanceBalance, customer ID, dispatch routing channels and registered sender names
get_utm_tagsList UTM tags used to track dispatches
send_messageSend a text via WhatsApp, Telegram (tdlib), Telegram Bot, SMS, VK/OK or MAX — with cascade, scheduling, priority, reply-to and callbacks
send_bulkSend the same message to many phone numbers at once
get_delivery_statusStatus and details of a delivery, with the status explained in plain words
delete_deliveryDelete a delivered WhatsApp/Telegram message on all recipient devices
get_phone_infoCountry, operator and normalized format of a phone number
send_fileSend a document, image, audio or video from a local path, URL or base64 (up to 100 MB)
create_webhookSubscribe a URL to events: incoming messages, WhatsApp statuses, login/logout
get_webhookDetails of one webhook
list_webhooksAll registered webhooks
delete_webhookDelete a webhook
update_webhookChange a webhook's URL and/or event types

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:

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

Restart Claude Desktop.

Claude Code

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

The server needs JETAPI_TOKEN, so pass it when adding:

bash
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):

json
{  "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:

json
{  "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:

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

Configuration

VariableRequiredDefaultDescription
JETAPI_TOKENyes—Bearer token from the JetAPI dashboard
JETAPI_BASE_URLnohttps://api.jetapi.ioAPI host
JETAPI_DEBUGno01 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.

ValueChannelRecipient
whatsappWhatsAppphone or whatsapp_lid
tdlibPersonal Telegram accountphone, username or tdlib_user_id (negative ID = group chat)
telegramTelegram Botphone
smsSMSphone
notifyVK / OK notificationsphone
maxMAX messengerphone

Usage examples

Ask Claude in plain language:

SayTool
"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

bash
git clone https://github.com/jetapi/jetapi-mcp-server.gitcd jetapi-mcp-servernpm installcp .env.example .env   # put your token in .envnpm run buildnpm start
ScriptWhat it does
npm run devRun the TypeScript source directly
npm run inspectorOpen the MCP Inspector with all tools
npm run checkVerify versions in package.json / server.json / manifest.json and that the server exposes all 14 tools
npm run build:mcpbBuild 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: [email protected]

License

MIT

Source: README.md at commit 49b0c14

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.3LatestSep 23, 2026
  2. v1.0.2Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts