KnowBe4

io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.1.6Updated Oct 24, 2026

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

Overview

AI-generated overview

Local MCP server that connects an AI assistant to KnowBe4 security awareness training for users, groups, training, phishing campaigns and reporting.

What you can do
Manage users and view risk scores, including an interactive user card in MCP Apps hosts (read-only).
When to use it
Use it when an assistant should work with a KnowBe4 account: looking up users and risk scores, reviewing groups, training campaigns, phishing simulations and security awareness reports, or administering them.
Requirements
Runs locally over stdio, typically via npx or the container image. Needs a KnowBe4 Reporting API token in KNOWBE4_API_KEY for stdio and AUTH_MODE=env, plus an optional region (us, eu, ca, uk, de) or base URL. HTTP mode additionally requires CONDUIT_S2S_SECRET and per-request gateway headers.
Before you install
The KnowBe4 API token is a credential; keep it out of committed files. The server covers user management, training and phishing campaigns, so assistant actions may create or change data in your KnowBe4 tenant. HTTP mode needs CONDUIT_S2S_SECRET, and the insecure dev bypass should stay local only.

Installation

In SourceWeft

  1. Open KnowBe4 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 6edb819

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.1.6LatestOct 14, 2026
  2. v1.1.5Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts