KnowBe4 MCP Server

An MCP server for the KnowBe4 Reporting API (v1), the security awareness training platform MSPs use to phish-test and train their clients' users. It lets an AI agent read the account and risk scores, users and groups, phishing campaigns with their security tests and per-recipient results, training campaigns and enrollments, purchased content and policies, and summaries across them. The API is read-only, so every tool is too.

• Transport: MCP Streamable HTTP at POST /mcp, health probe at GET /health

• Stateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; every tool is listed from the first tools/list

• Python 3.12, uv, FastMCP, httpx

• License: Apache-2.0, Copyright 2026 MSPbots.ai

MSPbots Connector

The MCP Gateway built for MSPs: visible, controlled, and your data stays where it belongs.

Get started at connect.mspbots.ai →

MSPbots Connector gives your AI clients one MCP URL to reach your entire MSP stack (RMM, PSA, documentation, security, finance), and gives you control over who can call which tool and a record of everything that was called.

Hosted service: connect.mspbots.ai · Free to use.

Why Connector

Quick start

1. Sign up at connect.mspbots.ai.

2. Connect your vendors. Pick from 150+ connectors and authorize each one on the vendor's own page, or bring your own API keys. No extra vendor accounts needed.

3. Set access. Create roles and decide which tools each role may call. Nothing is allowed until you allow it.

4. Add your MCP URL to your AI client. Copy the URL from your Connector dashboard into Claude, ChatGPT, Cursor, VS Code, Gemini, Codex, or any MCP-capable client.

5. Ask your AI to do real work, and watch every call appear in the audit log.

Features

Unified gateway

• One MCP URL for all your AI clients

• 150+ connectors across the MSP stack

• Custom MCP servers supported, free

• Authorization happens on each vendor's own page; the AI never sees passwords or tokens

• Bring your own credentials: use the vendor API keys you already have

• Multiple accounts per app; connect once, reuse across AI clients

• Tool search: finds the right action for the task

• One sign-in; vendor credentials are injected behind the scenes and OAuth tokens refresh automatically

Visibility

• Audit log for every tool call (who, which vendor, when)

• Usage dashboard: call volume, top vendors, error rate, per-user activity

• Export audit logs to CSV, or stream to Loki, Graylog, or LogScale (SIEM)

• Optional recording of tool arguments and result summaries (off by default, enabled per organization)

Control

• Per-role, per-tool allowlist, deny by default

• owner / admin / member roles

• SCIM provisioning with Entra ID, Okta, JumpCloud, and Google Workspace

Security

• Credentials encrypted one record at a time (AES-256-GCM, per-record key)

• AI clients authenticate with OAuth 2.1 + PKCE

• Vendor responses are scanned for prompt-injection patterns and returned as structured data. This is one layer of defense, not a guarantee against every attack.

• Static egress IP for customer firewall and API allowlisting

Pricing

Free.

Links: connect.mspbots.ai · mspbots.ai

Related MCP server: Inforcer MCP Server

Authentication headers

Where to get them: generate the key in the KnowBe4 console's Reporting API management page (User Event API keys are different and do not work here). The region is the server the console runs on: training.knowbe4.com is us, eu.knowbe4.com is eu, and so on.

How the key is sent: every call goes to https://{region}.api.knowbe4.com/v1/... with Authorization: Bearer <key>.

A request to /mcp without the key gets HTTP 401; an unknown region does not block the request, and tools return invalid_argument instead.

Tools

All tools return a JSON string. Lists take page (from 1) and per_page (default 50, max 200) and return {count, page, has_more, next_page, offset, next_offset}. They also take offset (record position from 0, overrides page): pass next_offset from the previous result to continue. When a page is too large for one response and is cut, next_offset starts right after the last record returned, so no record is skipped (KnowBe4 pages by number only, and the rest of a cut page is on no other page).

Errors come back as a JSON envelope instead of an exception:

{"error": {"code": "unauthorized", "message": "KnowBe4 returned HTTP 401 for v1/users", "retryable": false}}

code is one of not_configured, unauthorized, not_found, invalid_argument, rate_limited, upstream_error. Requests are retried with backoff on 429, 5xx and network errors. KnowBe4 allows 2,000 calls per day plus one per licensed user, at most 4 per second and 50 per minute in bursts.

Run locally

uv sync
uv run python -m knowbe4_mcp          # listens on 0.0.0.0:8080

or with Docker:

docker build --platform linux/amd64 -t knowbe4-mcp:dev .
docker run --rm -p 8080:8080 knowbe4-mcp:dev

Configuration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0), MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from the environment.

Testing example

# list tools
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-KnowBe4-API-Key: your-api-key" \
  -H "X-KnowBe4-Region: us" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

# phishing results across all security tests
curl -s http://localhost:8080/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-KnowBe4-API-Key: your-api-key" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"knowbe4_reporting_phishing_summary","arguments":{}}}'

Unit tests (no network access needed):

uv run pytest

Delivery notes

• Tool count (30). Kept as is because the tool names are an existing contract; every earlier parameter is still accepted. (The optional "lazy loading" meta-tools of older versions, off by default, are not included: every tool is listed directly.)

• API source. The official OpenAPI document behind KnowBe4's developer portal (https://developer.knowbe4.com/elvis-swagger.yml, Reporting API).

• Routes fixed. Store purchases are /v1/training/store_purchases and policies /v1/training/policies; older versions called /v1/store/purchases and /v1/policies.

• New optional parameters from the official API: full on the risk score histories, expand_groups on users, campaign_type: callback on the phishing tests, and the user / campaign / content / archived filters on enrollments.

• Summaries cover everything by default. The phishing and training summaries read every page (up to 2,000 records) unless page / per_page is passed; older versions summarised only the first page.

• Paging. KnowBe4 announced that the page parameter will be retired in November 2026 in favour of cursor paging; the tools still use page today, as the published reference does.

• Not included: the user "card" UI resource of older versions (an MCP Apps HTML view); the tools return the same data as JSON.

License

Apache License 2.0 - see LICENSE and NOTICE.