JetAPI

io.github.jetapi由 GitHub 帳號 jetapi 發布v1.0.3更新於 Oct 24, 2026

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

已驗證STDIO僅桌面效率與工作流溝通與協作

概覽

AI 產生的概覽

JetAPI 讓助理透過 JetAPI 帳號傳送 WhatsApp、Telegram、簡訊、VK/OK 與 MAX 訊息、檔案及大量群發,並管理投遞 webhook。

可以做什麼
  • 透過 WhatsApp、Telegram(個人帳號或機器人)、簡訊、VK/OK 與 MAX 傳送文字訊息,支援通道串接、排程、優先順序與回覆
  • 一次對多個手機號碼傳送相同訊息,並從本機路徑、URL 或 base64 傳送文件、圖片、音訊或影片
  • 以白話查詢投遞狀態,在收件者裝置上刪除已送達的 WhatsApp/Telegram 訊息,查詢手機號碼的國家與電信業者
  • 讀取帳號資訊、餘額、分派路由、寄件者名稱與 UTM 標籤
  • 建立、列出、檢視、更新與刪除 webhook,用於接收訊息、WhatsApp 狀態與登入/登出事件
適用情境
適合想讓 AI 助理實際透過訊息通道向客戶送出通知、訂單更新、提醒或大量公告,或透過 webhook 把收到的訊息接進自有服務的情境,前提是已有 JetAPI 帳號。
執行需求
以 stdio 方式透過 npx 在本機執行(需 Node.js 18.17 或更新版本),或使用 Claude Desktop 擴充套件安裝。需要 JetAPI 帳號,並在 JETAPI_TOKEN 提供 bearer 權杖;透過 WhatsApp 或 Telegram 傳送前,須先在 JetAPI 控制台連接該通道。可選用 JETAPI_BASE_URL 與 JETAPI_DEBUG。需能連線至 JetAPI API。
安裝前請注意
傳送訊息、群發與檔案會消耗帳戶餘額並觸及真實收件者,除 WhatsApp/Telegram 可透過 delete_delivery 刪除外,訊息送出後無法收回。webhook 工具會建立、變更與刪除訂閱。JETAPI_TOKEN 是可存取帳號的 bearer 憑證,請勿寫入共用設定檔。訊息內容、檔案與手機號碼會傳送至 JetAPI 服務。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 JetAPI,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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

來源:README.md,提交 49b0c14

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

2
  1. v1.0.3最新Sep 23, 2026
  2. v1.0.2Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分