KnowBe4

io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.1.6更新於 Oct 24, 2026

MCP server for KnowBe4 security awareness training — users, groups, training, phishing campaigns.

已驗證STDIO僅桌面效率與工作流安全與監控

概覽

AI 產生的概覽

本機 MCP 伺服器,將 AI 助理連接到 KnowBe4 資安意識訓練,用於使用者、群組、訓練、釣魚演練和報告。

可以做什麼
管理使用者並檢視風險分數,在 MCP Apps 主機中顯示唯讀的互動式使用者卡片。
適用情境
當助理需要操作 KnowBe4 帳戶時使用:查詢使用者與風險分數、檢視群組、訓練活動、釣魚演練和資安意識報告,或進行管理。
執行需求
透過 stdio 在本機執行,通常使用 npx 或容器映像。stdio 和 AUTH_MODE=env 需要 KNOWBE4_API_KEY 中的 KnowBe4 Reporting API 權杖,可選區域(us、eu、ca、uk、de)或自訂基礎 URL。HTTP 模式另需 CONDUIT_S2S_SECRET 及每次請求的閘道標頭。
安裝前請注意
KnowBe4 API 權杖屬於憑證,不要寫入提交的檔案。伺服器涉及使用者管理、訓練和釣魚活動,助理操作可能建立或變更 KnowBe4 租用戶中的資料。HTTP 模式需要 CONDUIT_S2S_SECRET,不安全的開發繞過僅限本機使用。

安裝

在 SourceWeft 中

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

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

其他 MCP 客戶端

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

README

KnowBe4 MCP Server

[License] [Node.js]

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

bash
npm install @wyre-ai/knowbe4-mcp

Configuration

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

VariableRequiredDescription
KNOWBE4_API_KEYFor stdio and AUTH_MODE=envKnowBe4 API key
KNOWBE4_REGIONNoAPI region: us (default), eu, ca, uk, or de
KNOWBE4_BASE_URLNoCustom base URL (overrides region)
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENoenv (default outside the image) or gateway. The container image and Compose default to gateway. Gateway mode requires X-KnowBe4-API-Key on each /mcp request (X-KnowBe4-Region is optional) and never falls back to KNOWBE4_*.
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 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.

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-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:

json
{  "mcpServers": {    "knowbe4-mcp": {      "command": "npx",      "args": ["@wyre-ai/knowbe4-mcp"],      "env": {        "KNOWBE4_API_KEY": "your-knowbe4-api-key"      }    }  }}

Running with Claude Code (CLI)

bash
claude mcp add knowbe4-mcp \  -e KNOWBE4_API_KEY=your-value \  -- npx -y @wyre-ai/knowbe4-mcp

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.

bash
docker build -t knowbe4-mcp .docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  knowbe4-mcp

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:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

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

bash
docker run \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e KNOWBE4_API_KEY=your-value \  -e KNOWBE4_REGION=us \  -p 127.0.0.1:8080:8080 \  knowbe4-mcp

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:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm start

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

bash
# Clone the repositorygit clone https://github.com/WYRE-AI/knowbe4-mcp.gitcd knowbe4-mcp
# Install dependenciesnpm install
# Buildnpm run build
# Run testsnpm test

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
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

2
  1. v1.1.6最新Oct 14, 2026
  2. v1.1.5Sep 16, 2026

評分

已滿足適用檢查項的 50%

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

  • 近 30 天內可連通25 分

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

  • 已宣告認證方式10 分

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

  • 已列出工具15 分

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

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