
KnowBe4
io.github.wyre-technology由 GitHub 帳號 wyre-technology 發布v1.1.4更新於 Oct 24, 2026
MCP server for KnowBe4 security awareness training — users, groups, training, phishing campaigns.
概覽
讓助理管理 KnowBe4 資安意識訓練:使用者、群組、訓練活動、釣魚模擬與風險報告。
- 可以做什麼
- 透過 KnowBe4 Reporting API 將支援 MCP 的助理連接到 KnowBe4 帳號。它提供帳號設定、使用者管理與風險評分、群組管理、釣魚模擬活動、訓練活動管理以及資安意識報告等領域。其中一個使用者查詢工具可在支援 MCP Apps 的主機中以唯讀互動卡片呈現,顯示風險評分、易受釣魚攻擊比例與趨勢。
- 適用情境
- 適合資安意識訓練管理員與託管服務供應商,希望直接在助理中查詢或管理 KnowBe4 的使用者、群組、訓練與釣魚活動,而不必登入網頁主控台。最適合已在使用 KnowBe4、希望在對話流程中完成報告與活動管理的團隊。
- 執行需求
- 以 stdio 本機程序執行,通常透過 npx 或容器映像啟動。需要 KnowBe4 Reporting API 權杖,以環境變數 KNOWBE4_API_KEY 提供,並需要連線至 KnowBe4 API 的網路。選用設定包括 KNOWBE4_REGION(us、eu、ca、uk、de)、KNOWBE4_BASE_URL、AUTH_MODE、MCP_TRANSPORT 與 LOG_LEVEL。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 KnowBe4,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
KnowBe4 MCP Server
A Model Context Protocol (MCP) server for KnowBe4 security awareness training. Enables AI assistants to manage phishing simulations, training campaigns, user risk scoring, and security awareness reporting.
This is a Model Context Protocol (MCP) server that connects Claude (or any MCP-compatible AI) to your KnowBe4 environment.
Part of the MSP Claude Plugins ecosystem — a growing suite of AI integrations for the MSP stack. Built by MSPs, for MSPs.
Installation
Configuration
Copy .env.example. Stdio and AUTH_MODE=env read the KnowBe4 variables. Gateway mode does not.
/health and /healthz stay unauthenticated and do 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.
In AUTH_MODE=gateway, /mcp also requires X-KnowBe4-API-Key (X-KnowBe4-Region is optional). That header is the only credential source for the request. A request missing it returns 401 and does not read KNOWBE4_API_KEY from the environment.
Usage
Running with Claude Desktop
Add to your Claude Desktop claude_desktop_config.json:
Running with Claude Code (CLI)
Docker
The image listens on 0.0.0.0 inside the container (MCP_HTTP_HOST) and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass a real S2S secret. In gateway mode, the KnowBe4 API key arrives on each request as X-KnowBe4-API-Key; it is not read from the environment.
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, does not set KNOWBE4_API_KEY or env_file, and publishes 127.0.0.1:8080:8080:
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses KNOWBE4_API_KEY:
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning. A non-loopback MCP_HTTP_HOST makes startup exit:
Available Domains
Account
Account information and settings
Groups
User group management
Phishing
Phishing simulation campaigns
Reporting
Security awareness reports
Training
Training campaign management
Users
User management and risk scoring
Interactive User Card (MCP Apps)
knowbe4_users_get renders as an interactive card in MCP Apps hosts
(Claude Desktop/web) showing the user's risk score, phish-prone percentage,
risk-score trend, and profile details; plain-JSON behavior is unchanged in
other hosts, and the card is read-only (no write round-trip). 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.
Development
Contributing
Contributions are welcome! Please see CONTRIBUTING.md if present, or open an issue to discuss changes.
License
Licensed under the Apache License, Version 2.0. See LICENSE for details.
來源:README.md,提交 6edb819
工具
0版本歷史
1- v1.1.4最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分