MCP server for ThreatLocker โ zero-trust endpoint protection, allowlisting, and policies.
Connect Runs on your machine
claude mcp add threatlocker-mcp -e THREATLOCKER_API_KEY=<THREATLOCKER_API_KEY> -e THREATLOCKER_ORGANIZATION_ID=<THREATLOCKER_ORGANIZATION_ID> -e MCP_TRANSPORT=<MCP_TRANSPORT> -e AUTH_MODE=<AUTH_MODE> -e LOG_LEVEL=<LOG_LEVEL> -- docker run -i --rm ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
],
"env": {
"THREATLOCKER_API_KEY": "<THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"AUTH_MODE": "<AUTH_MODE>",
"LOG_LEVEL": "<LOG_LEVEL>"
}
}
}
}
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
],
"env": {
"THREATLOCKER_API_KEY": "<THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"AUTH_MODE": "<AUTH_MODE>",
"LOG_LEVEL": "<LOG_LEVEL>"
}
}
}
}
{
"servers": {
"threatlocker-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
],
"env": {
"THREATLOCKER_API_KEY": "<THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<MCP_TRANSPORT>",
"AUTH_MODE": "<AUTH_MODE>",
"LOG_LEVEL": "<LOG_LEVEL>"
}
}
}
}
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server runs locally, so its tools are listed by your MCP client once it starts.
Environment variables
| Name | Description |
|---|---|
THREATLOCKER_API_KEYRequired, secret | ThreatLocker API key |
THREATLOCKER_ORGANIZATION_IDRequired | ThreatLocker organization ID |
MCP_TRANSPORTOptional | Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. |
AUTH_MODEOptional | Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway. |
LOG_LEVELOptional | Log verbosity: debug, info, warn, error |
Details
| Package | ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6 (OCI, stdio) |
| First published | 20 Aug 2026 |
| Last updated | 20 Aug 2026 |
| Registry name | io.github.wyre-technology/threatlocker-mcp |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
