Ictpbx Mcp

io.github.ictinnovations由 GitHub 账号 ictinnovations 发布v0.1.1更新于 Oct 26, 2026

Read ICTPBX state: extensions, DID numbers, SIP trunks, tenants and live PBX statistics.

概览

AI 生成的概览

只读 MCP 服务器,让助手查看 ICTPBX(ICTCore)电话系统:分机、DID 号码、SIP 中继、租户和 PBX 统计。

可以做什么
  • 通过分机、设备、振铃组、队列、IVR、语音信箱、会议和网关的数量了解 PBX 整体状况
  • 列出 SIP 分机及其用户名、名称、租户和账户 ID
  • 列出 DID 呼入号码及其启用状态、所属租户和绑定联系人
  • 列出 SIP 中继提供商及其名称、主机和租户
  • 列出多租户 PBX 上的租户(客户组织)及其公司、联系人和限额
适用场景
适合管理或支持多租户 ICTPBX 部署的场景:希望助手回答有哪些分机、呼入号码、中继和租户,或在不打开管理界面的情况下快速了解服务器状态。
运行要求
通过 npx 或全局 npm 安装后在本地运行,需要 Node.js 18 或更高版本。需要 ICTCore REST 基础地址(通常以 /api 结尾,变量 ICTPBX_BASE_URL)、API 账户邮箱(ICTPBX_USERNAME)及其密码(ICTPBX_PASSWORD);可选请求超时(ICTPBX_TIMEOUT_MS)和跳过 TLS 校验(ICTPBX_TLS_INSECURE)。需要能访问 PBX 服务器的网络。
安装前请注意
账户密码通过 ICTPBX_PASSWORD 环境变量传入,请勿写入共享配置或代码仓库。服务器会用该账户凭据登录并在会话中保存 JWT 令牌。ICTPBX_TLS_INSECURE 会关闭证书校验,仅应用于自签名的测试服务器。工具虽标为只读,但实际可访问范围仍受该账户自身权限限制。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Ictpbx Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

ictpbx-mcp

A Model Context Protocol server for ICTPBX, the multi-tenant, white-label IP-PBX built on the ICTCore framework by ICT Innovations.

It lets an AI assistant read your PBX state — extensions, DID numbers, SIP trunk providers, tenants and live statistics — over the ICTCore REST API. It is read-only: it never places a call or changes configuration.

Install

bash
npx -y ictpbx-mcp      # no installnpm install -g ictpbx-mcp

Requires Node.js 18 or newer.

Configure

VariableRequiredDefault
ICTPBX_BASE_URLyesICTCore REST base, normally ending in /api, e.g. https://your-ictpbx/api
ICTPBX_USERNAMEyesAPI account email (ICTCore logs in by email)
ICTPBX_PASSWORDyesPassword for that account
ICTPBX_TIMEOUT_MSno30000Per-request timeout
ICTPBX_TLS_INSECUREnofalseSkip TLS verification — self-signed test servers only

Claude Desktop example

json
{  "mcpServers": {    "ictpbx": {      "command": "npx",      "args": ["-y", "ictpbx-mcp"],      "env": {        "ICTPBX_BASE_URL": "https://your-ictpbx/api",        "ICTPBX_USERNAME": "[email protected]",        "ICTPBX_PASSWORD": "your-password"      }    }  }}

Tools

ToolWhat it does
ictpbx_pbx_statisticsCounts of extensions, devices, ring groups, queues, IVRs, voicemails, conferences, gateways
ictpbx_list_extensionsSIP extensions with username, name, tenant
ictpbx_list_didsDID (inbound) numbers, active state and tenant
ictpbx_list_providersSIP trunk providers (upstream carriers)
ictpbx_list_tenantsTenants (customer organizations) on the PBX

How it connects

ICTPBX runs on ICTCore, which authenticates with a JWT from POST /authenticate (login by email) and reads it back from the Authorization: Bearer header. The server fetches the token on first use and refreshes it automatically.

About

Built by Tahir Almas at ICT Innovations — the team behind ICTPBX, ICTContact, ICTDialer, ICTFax and the ICTCore framework these products share. Learn more at ictpbx.com.

MIT licensed. Issues and PRs welcome at github.com/ictinnovations/ictpbx-mcp.

来源:README.md,提交 e5ee340

工具

5

ictpbx_pbx_statistics

PBX statistics

Counts across the PBX: extensions, devices, ring groups, call queues, IVR menus, voicemails, conferences and gateways. Use this first for a quick health picture of the server.

无需输入参数。

ictpbx_list_extensions

List extensions

List SIP extensions on the PBX with their username, name, tenant and account id. Use this to answer 'what extensions exist' or to find an extension's tenant.

无需输入参数。

ictpbx_list_dids

List DID numbers

List DID (inbound phone) numbers on the PBX: the number, whether it is active, its tenant and the contact it is tied to.

无需输入参数。

ictpbx_list_providers

List SIP trunk providers

List the SIP trunk providers (upstream carriers) configured on the PBX: name, host and tenant.

无需输入参数。

ictpbx_list_tenants

List tenants

List the tenants (customer organizations) on this multi-tenant PBX: company, contact and limits. Use this to see who the white-label PBX is serving.

无需输入参数。

版本历史

2
  1. v0.1.1最新Oct 26, 2026
  2. v0.1.0Sep 16, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分