Kaseya BMS

io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.1.7更新於 Nov 22, 2026

MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.

概覽

AI 產生的概覽

針對 Kaseya BMS PSA 的 MCP 伺服器,讓助理列出並檢視工單、客戶、聯絡人、合約、工時記錄,並搜尋知識庫。

可以做什麼
  • 列出並檢視工單,支援選用篩選條件,未指定時提示選擇狀態
  • 建立工單並在工單附加內部備註,執行前會要求確認
  • 依時間範圍列出工時記錄,以及客戶、聯絡人與合約
  • 列出服務目錄項目並搜尋知識庫
  • 在支援 MCP Apps 的宿主中將工單顯示為互動卡片,並可在卡片內新增備註
適用情境
適合讓助理在 Kaseya BMS PSA 租戶內回答問題或處理日常作業,例如查詢某客戶的工單、檢視近期工時記錄,或直接建立工單並附加備註,不必切換到 BMS 網頁介面。
執行需求
以本機 stdio 程序執行(容器映像或本機 npm 建置)。AUTH_MODE=env 時需要 KASEYA_BMS_TENANT_SUBDOMAIN,以及 KASEYA_BMS_API_TOKEN 或 KASEYA_BMS_K1_TOKEN 其中之一。HTTP 模式另需 CONDUIT_S2S_SECRET 與 X-Gateway-S2S 簽章;gateway 模式改由請求標頭取得租戶與權杖。
安裝前請注意
需要 BMS API 權杖或 Kaseya One SSO 權杖,可存取租戶資料,切勿寫入日誌或提交到程式碼庫。建立工單與新增備註會寫入 PSA 系統,執行前應先確認。HTTP 模式需要真實的 CONDUIT_S2S_SECRET;不安全的開發開關會停用標頭驗證,僅限本機使用。

安裝

在 SourceWeft 中

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

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

其他 MCP 客戶端

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

README

Kaseya BMS MCP Server

[Release] [License: Apache 2.0]

Model Context Protocol (MCP) server for the Kaseya BMS PSA API. Exposes tickets, accounts, contacts, contracts, time entries, the service catalog, and the knowledge base to AI assistants.

Tools

ToolDescription
kaseya_bms_list_ticketsList tickets. Optional $filter; status pick if omitted.
kaseya_bms_get_ticketGet a ticket by id.
kaseya_bms_create_ticketCreate a new ticket (destructive — confirmation required).
kaseya_bms_add_ticket_noteAppend a note to a ticket (destructive — confirmation required).
kaseya_bms_list_time_entriesTime entries by date range (24h / 7d / 30d / custom / all).
kaseya_bms_list_accountsAccounts (clients).
kaseya_bms_list_contactsContacts.
kaseya_bms_list_contractsContracts.
kaseya_bms_list_service_catalogService catalog items.
kaseya_bms_search_knowledge_baseKnowledge base search.

When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.

Interactive Ticket Card (MCP Apps)

kaseya_bms_get_ticket renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip via kaseya_bms_add_ticket_note (always posted internal-only); plain-JSON behavior is unchanged in other hosts. The card is neutral by default and brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) — no rebuild needed. After editing ui/, regenerate the embedded bundle with npm run build:ui.

Configuration

Copy .env.example. Stdio and AUTH_MODE=env read the Kaseya BMS variables. Gateway mode does not.

VariableRequiredDescription
KASEYA_BMS_TENANT_SUBDOMAINFor stdio and AUTH_MODE=envTenant subdomain (e.g. yourcompany)
KASEYA_BMS_API_TOKENOne of, for stdio and AUTH_MODE=envBMS API token
KASEYA_BMS_K1_TOKENOne of, for stdio and AUTH_MODE=envKaseya One SSO token
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENoenv (default) or gateway. Gateway mode requires X-Kaseya-BMS-Tenant-Subdomain plus X-Kaseya-BMS-API-Token or X-Kaseya-BMS-K1-Token on each /mcp request and never falls back to KASEYA_BMS_*.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder. Compose will not start without it. Never commit a real value. Generate one with openssl rand -hex 32.
MCP_ALLOW_INSECURE_DEVNoSet to 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST refuses startup. A known placeholder secret is still refused.
MCP_HTTP_HOSTNoBind address when a real CONDUIT_S2S_SECRET is set. Unset keeps 0.0.0.0, which is what the container image sets, so container deploys stay on every interface inside the container. Without a secret the dev bypass binds 127.0.0.1 instead.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.

/health stays unauthenticated and does not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The value is t=<unix seconds>,v1=<hex>, where v1 is HMAC-SHA256 of the exact string t=<unix seconds> keyed by CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never written to logs.

js
import { createHmac } from "node:crypto";
const t = Math.floor(Date.now() / 1000);const v1 = createHmac("sha256", process.env.CONDUIT_S2S_SECRET)  .update(`t=${t}`)  .digest("hex");const xGatewayS2s = `t=${t},v1=${v1}`;

In AUTH_MODE=gateway, /mcp also requires X-Kaseya-BMS-Tenant-Subdomain and either X-Kaseya-BMS-API-Token or X-Kaseya-BMS-K1-Token. Those headers are the only credential source for that request. A request missing them returns 401 and does not read KASEYA_BMS_* from the environment. Each request creates a fresh server instance with isolated credentials.

Docker Compose

The checked-in Compose service is gateway mode. It publishes 127.0.0.1:8080:8080, requires CONDUIT_S2S_SECRET, and does not set KASEYA_BMS_TENANT_SUBDOMAIN, KASEYA_BMS_API_TOKEN, KASEYA_BMS_K1_TOKEN, or env_file. The image build reads GitHub Packages credentials from the npmrc build secret (the repo .npmrc only sets the registry).

bash
CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" docker compose up --build

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses KASEYA_BMS_*:

bash
docker build -t kaseya-bms-mcp .docker run --rm \  -e CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" \  -e AUTH_MODE=env \  -e KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \  -e KASEYA_BMS_API_TOKEN=... \  -p 127.0.0.1:8080:8080 \  kaseya-bms-mcp

Local development

bash
npm installnpm run buildKASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \  KASEYA_BMS_API_TOKEN=... \  npm start

HTTP refuses to start until CONDUIT_S2S_SECRET is a real secret:

bash
MCP_TRANSPORT=http CONDUIT_S2S_SECRET="$(openssl rand -hex 32)" npm startcurl http://127.0.0.1:8080/health

Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

License

Apache-2.0

來源:README.md,提交 3ad28d3

工具

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

版本歷史

3
  1. v1.1.7最新Nov 21, 2026
  2. v1.1.6Oct 14, 2026
  3. v1.1.5Sep 16, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

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

  • 已宣告認證方式10 分

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

  • 已列出工具15 分

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

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