Is this an official KnowBe4 MCP server?

No. It is Memtro's MCP server with Memtro's KnowBe4 connector behind it: the connector reads KnowBe4 through its API with the credentials you connect on Dashboard → Connections, and KnowBe4 publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in KnowBe4?

Not yet. Today every KnowBe4 tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Engineering and operations

KnowBe4 MCP server

KnowBe4 in any MCP client, through Memtro: KnowBe4 does not publish this server. Memtro's KnowBe4 connector reads KnowBe4 through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only KnowBe4 security awareness reporting: users and groups, phishing campaigns and tests with aggregate results (never a named person's result), training campaigns with completion, and who has completed which training.

Reads

knowbe4_usersPeople enrolled in KnowBe4: name, email, job title, department, location, status and groups.
knowbe4_groupsGroups in KnowBe4 with member count, type, status and the group's own risk score (an aggregate).
knowbe4_phishing_campaignsSimulated phishing campaigns in KnowBe4: name, status, target groups, last run, the last phish-prone percentage across the campaign…
knowbe4_phishing_testsPhishing security tests (each send of a campaign) in KnowBe4 with aggregate results: delivered, opened, clicked, replied, data entered…
knowbe4_training_campaignsTraining campaigns in KnowBe4: name, status, groups, modules, start and end, auto-enrolment.
knowbe4_training_enrollmentsTraining enrolments in KnowBe4, per person: who, module, campaign, status (Not Started, In Progress, Passed, Past Due…), when enrolled…

Connect it

First connect KnowBe4 on Dashboard → Connections, then add Memtro to your client once. The KnowBe4 tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared KnowBe4 connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How did the October phishing test go?
› Who is past due on security training?
› Which groups have the highest risk score?
› What was the phish-prone percentage on the finance team's last campaign?
› Has Dan Fletcher completed this year's security training?

Questions

Is this an official KnowBe4 MCP server?: No. It is Memtro's MCP server with Memtro's KnowBe4 connector behind it: the connector reads KnowBe4 through its API with the credentials you connect on Dashboard → Connections, and KnowBe4 publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in KnowBe4?: Not yet. Today every KnowBe4 tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.