
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
概览
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。
安装
在 SourceWeft 中
- 打开 控制台中的 JetAPI,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
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
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
- Download
jetapi-mcp-server.mcpbfrom the latest release. - Double-click it (or drag it into Claude Desktop → Settings → Extensions).
- 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:
Restart Claude Desktop.
Claude Code
The server needs JETAPI_TOKEN, so pass it when adding:
Cursor
Add to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):
VS Code
Add to .vscode/mcp.json — VS Code will prompt for the token and keep it out of the file:
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:
Configuration
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.
Usage examples
Ask Claude in plain language:
Behaviour
- Parameters are sent as URL query parameters, as the JetAPI API expects;
send_fileuploads the file asmultipart/form-data. - Incompatible parameters (e.g. a Telegram
usernamewithout thetdlibchannel, orscheduled_atin 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.orValidation error: text: the text cannot be empty. - All logs go to stderr; stdout is reserved for the MCP protocol.
Development
Releasing
- Bump the version in
package.json,server.json(bothversionfields) andmanifest.json, and add aCHANGELOG.mdentry. - Merge to
main, then push a tag:git tag v1.2.3 && git push origin v1.2.3. - The Release workflow publishes to npm (trusted publishing with provenance), creates a GitHub release with the
.mcpbbundle 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).
- JetAPI MCP Server privacy policy — what the extension handles, stores and shares
- JETAPI LLC Privacy Policy — how the JetAPI service processes personal data
Questions: [email protected]
License
来源:README.md,提交 49b0c14
工具
0版本历史
2- v1.0.3最新Sep 23, 2026
- v1.0.2Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分