Integration

KnowBe4 integration

KnowBe4 Reporting API, a read-only view of a KnowBe4 security awareness (KSAT) console: the account and its risk score history, users and groups with their risk scores, phishing campaigns, phishing security tests and per-recipient results, training campaigns, enrollments, uploaded policies and Store Purchases. Available on Platinum, Diamond, SAT Foundation and SAT Advanced subscriptions; limited to 2,000 requests per day plus the number of licensed users, 4 requests per second and 50 per minute in bursts. User phone numbers, office location, comments and custom fields, and recipients' IP address, geolocation, browser and operating system are not returned; the cursor pagination mode is not exposed (page and per_page are). Pushing events is the separate KnowBe4 User Events integration. Authentication is a Reporting API key (KnowBe4 console, Account Settings, API) sent as a Bearer token, plus the server region of the account.

Connect KnowBe4 How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in KnowBe4.Built from the 24 KnowBe4 tools below, on the connection you add once.

What you can do with KnowBe4

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Campaign, 4 operations

get_phishing_campaignGet phishing campaignGETReturns one phishing campaign by campaign_id (from list_phishing_campaigns), with its groups, status, schedule settings and the phishing security tests it ran. Pass campaign_type=callback for a callback campaign.
get_training_campaignGet training campaignGETReturns one training campaign by campaign_id (from list_training_campaigns): groups, content (Store Purchases and policies), status, start and end dates, enrollment settings and completion percentage.
list_phishing_campaignsList phishing campaignsGETLists phishing campaigns with targeted groups, last phish-prone percentage, status, schedule, difficulty and the phishing security tests (psts) they ran. Paginate with page and per_page.
list_training_campaignsList training campaignsGETLists training campaigns with groups, content, status, dates and completion percentage. Pass exclude_percentages=true for full pages: otherwise KnowBe4 caps the response at 10 campaigns.

Risk score history, 3 operations

list_account_risk_score_historyList account risk score historyGETReturns the account's risk score history as a list of {risk_score, date}. The last six months by default; pass full=true for the entire history.
list_group_risk_score_historyList group risk score historyGETReturns one group's risk score history as a list of {risk_score, date}. The last six months by default; pass full=true for the entire history.
list_user_risk_score_historyList user risk score historyGETReturns one user's risk score history as a list of {risk_score, date} (up to 1000 records). The last six months by default; pass full=true for the entire history.

Security test, 3 operations

get_phishing_security_testGet phishing security testGETReturns one phishing security test by pst_id (from list_phishing_security_tests): status, groups, template, categories, phish-prone percentage and the per-outcome user counts.
list_campaign_security_testsList campaign security testsGETLists the phishing security tests run by one phishing campaign (campaign_id from list_phishing_campaigns), with the same counts as list_phishing_security_tests. Paginate with page and per_page.
list_phishing_security_testsList phishing security testsGETLists phishing security tests (PSTs) with campaign, status, groups, template, categories and counts of users scheduled, delivered, opened, clicked, replied, reported and bounced. Paginate with page and per_page.

Enrollment, 2 operations

get_training_enrollmentGet training enrollmentGETReturns one training enrollment by enrollment_id (from list_training_enrollments): user, module or policy name, campaign name, dates, status, time spent and policy acknowledgement.
list_training_enrollmentsList training enrollmentsGETLists training enrollments: user, module or policy, campaign name, enrollment, start and completion dates, status and time spent. Filter by campaign_id, store_purchase_id or user_id; paginate with page and per_page.

Group, 2 operations

get_groupGet groupGETReturns one group by id (from list_groups): name, group type, member count, current risk score and status (active or archived).
list_groupsList groupsGETLists the account's groups with id, name, type (console_group, smart_group, provisioning_managed_group), member count, risk score and status. Filter by status; paginate with page and per_page.

Policy, 2 operations

get_training_policyGet training policyGETReturns one uploaded policy by policy_id (from list_training_policies): title, minimum review time in minutes, default language and status (0 draft, 1 published, 2 archived).
list_training_policiesList training policiesGETLists the policies uploaded to the account for users to review, with title, minimum review time, default language and status (0 draft, 1 published, 2 archived). Paginate with page and per_page.

Recipient, 2 operations

get_security_test_recipientGet security test recipientGETReturns one recipient's results for a phishing security test (pst_id and recipient_id from list_security_test_recipients): the user, template and the time of each action taken.
list_security_test_recipientsList security test recipientsGETLists the recipients of one phishing security test (pst_id) with the user, the template received and when they were delivered, opened, clicked, replied, entered data or reported it. Paginate with page and per_page.

Store purchase, 2 operations

get_store_purchaseGet store purchaseGETReturns one Store Purchase (training content bought from the ModStore) by id from list_store_purchases: name, type, duration, publisher, dates and retirement status.
list_store_purchasesList store purchasesGETLists the training content bought from the KnowBe4 ModStore (Store Purchases): name, type, duration in minutes, publisher, publish and purchase dates and retirement status. Paginate with page and per_page.

User, 2 operations

get_userGet userGETReturns one user by id (from list_users): name, email, job title, department, division, manager, groups, phish-prone percentage, risk score, status and sign-in dates.
list_usersList usersGETLists users of the KnowBe4 account with name, email, job title, department, manager, groups, phish-prone percentage and risk score. Filter by status or group_id; paginate with page and per_page (max 500).

Account, 1 operation

get_accountGet accountGETReturns the KnowBe4 account: organization name, account type, allowed domains, admins (name and email), subscription level and end date, number of seats and current risk score.

Member, 1 operation

list_group_membersList group membersGETLists the users who are members of one group (group_id from list_groups), with the same fields as list_users. Paginate with page and per_page (max 500).

Use KnowBe4 from Claude Code, Cursor or Codex

Connect KnowBe4 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its KnowBe4 operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect KnowBe4

Create your workspace
Sign up free. Nothing to install.
Connect KnowBe4 once
Add your KnowBe4 connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.