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.

已验证STDIO仅桌面安全与监控商业与电商

概览

AI 生成的概览

让助手管理 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。
安装前请注意
该服务器持有 KnowBe4 API 令牌(KNOWBE4_API_KEY),可访问你的安全意识租户,请将其保存在客户端配置中,不要外泄。根据所用工具,它可能修改用户、群组、培训分配和钓鱼活动,执行写操作前应先行确认。在网关模式下,凭据预期由外部网关以请求头方式注入。

安装

在 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 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.1.4最新Sep 16, 2026

评分

已满足适用检查项的 50%

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

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

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

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分