knowbe4
An MCP server for KnowBe4
claude mcp add --transport stdio mirage-security-knowbe4-mcp-server node /absolute/path/to/knowbe4-mcp-server/build/src/index.js \ --env KNOWBE4_REGION="us" \ --env KNOWBE4_API_KEY="your-api-key-here"
How to use
This MCP server exposes the KnowBe4 Reporting REST API through a modular set of tools that let an AI assistant interact with KnowBe4 data. It includes endpoints and tools for accounts, users, groups, phishing campaigns and tests, and training materials and enrollments. Once configured in Claude Desktop, you can query information such as account details, user lists and risk scores, group data, phishing campaign results, PST details, and training policies or enrollments. The tools are named clearly (e.g., get_account, get_users, get_phishing_campaigns, get_training_enrollments) so you can compose natural language prompts that map to specific API calls and filters. Environment variables control authentication and region, ensuring requests reach the correct KnowBe4 region and access scope.
How to install
Prerequisites:
- Node.js 18 or higher
- npm (comes with Node.js)
- KnowBe4 account with API access and a valid API key
Installation steps:
-
Clone or download the repository: git clone https://github.com/yourorg/knowbe4-mcp-server.git cd knowbe4-mcp-server
-
Install dependencies: npm install
-
Build the TypeScript code (if applicable): npm run build
-
Prepare environment variables (example):
- KNOWBE4_API_KEY=your-api-key
- KNOWBE4_REGION=us
-
Run the server (adjust path to your built index.js as needed): node build/src/index.js
-
Configure Claude Desktop (example):
- macOS: Edit ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: Edit %APPDATA%\Claude\claude_desktop_config.json Use the following config, replacing paths and keys: { "mcpServers": { "knowbe4": { "command": "node", "args": ["/absolute/path/to/knowbe4-mcp-server/build/src/index.js"], "env": { "KNOWBE4_API_KEY": "your-api-key-here", "KNOWBE4_REGION": "us" } } } }
Additional notes
Tips and common issues:
- Keep your KNOWBE4_API_KEY secure; do not commit to version control.
- If you encounter authentication errors, verify that KNOWBE4_API_KEY is valid and the region matches your account (us, eu, ca, uk, de).
- The API rate limits apply as documented by KnowBe4; implement appropriate throttling in your prompts if needed.
- When upgrading the MCP server, rebuild before restarting to pick up code changes.
- If you see 401 or 404 errors, double-check your API key and region, and ensure the permissions align with requested endpoints.
- Use environment variables to keep sensitive data out of configuration files.
Related MCP Servers
zen
Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage
MCP -Deepseek_R1
A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)
mcp-fhir
A Model Context Protocol implementation for FHIR
mcp
Inkdrop Model Context Protocol Server
mcp-appium-gestures
This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..
dubco -npm
The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.