ThreatLocker

io.github.WYRE-AIPublished by GitHub account WYRE-AIv1.4.2Updated Nov 21, 2026

MCP server for ThreatLocker — zero-trust endpoint protection, allowlisting, and policies.

Overview

AI-generated overview

Connects an assistant to the ThreatLocker Portal API to inspect computers, approval requests, audit logs and organizations for zero-trust endpoint protection.

What you can do
  • Navigate domains and check API connection status
  • List and inspect computers, their checkin history, and computer groups
  • List, inspect and count approval requests, including permit application details
  • Search audit log entries, fetch single entries and view a file's audit history
  • List child organizations, get an organization's installation auth key, and list organizations for computer moves
When to use it
Useful for security or IT admins who already run ThreatLocker and want to query endpoint inventory, pending approvals and audit history in natural language instead of clicking through the portal.
Requirements
Runs locally over stdio (Docker image or Node.js build from source). Needs a ThreatLocker API key in THREATLOCKER_API_KEY and an organization ID in THREATLOCKER_ORGANIZATION_ID, plus network access to the ThreatLocker API. Gateway/HTTP mode additionally needs AUTH_MODE=gateway and CONDUIT_S2S_SECRET, with credentials supplied per request via headers.
Before you install
Requires a ThreatLocker API key, a sensitive credential; the organization auth key tool returns an installation key that grants enrollment. Approval and audit tools only work if the API user's role has the right portal permissions. Gateway mode accepts credentials via headers and rejects requests without a valid X-Gateway-S2S proof; do not use MCP_ALLOW_INSECURE_DEV outside local development.

Installation

In SourceWeft

  1. Open ThreatLocker in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ThreatLocker MCP Server

A Model Context Protocol (MCP) server that provides AI assistants with access to the ThreatLocker Portal API. Manage computers, approval requests, audit logs, and organizations through natural language interactions.

Features

  • Stateless Architecture: No session state required, fresh connections per request
  • Decision-Tree Navigation: Navigate domains with threatlocker_navigate
  • Gateway Mode: Multi-tenant support via HTTP headers
  • Elicitation Support: Interactive prompts for missing parameters
  • Comprehensive Error Handling: Detailed error messages and logging
  • Docker Support: Production-ready containerization

Tools

Navigation

  • threatlocker_navigate - Navigate to a domain to see available tools
  • threatlocker_status - Check API connection status and available domains

Computers

  • threatlocker_computers_list - List computers with filters (search, group, pagination)
  • threatlocker_computers_get - Get detailed computer information
  • threatlocker_computers_get_checkins - Get computer checkin history

Computer Groups

  • threatlocker_computer_groups_list - List computer groups with filters
  • threatlocker_computer_groups_dropdown - Get computer groups for dropdown selection

Approval Requests

  • threatlocker_approvals_list - List approval requests with status filters
  • threatlocker_approvals_get - Get detailed approval request information
  • threatlocker_approvals_pending_count - Get count of pending approvals
  • threatlocker_approvals_get_permit_application - Get permit application details

Troubleshooting: if approval tools return an HTTP 401 / "Authentication failed" while audit tools work with the same key, the ThreatLocker API user/role lacks Approval Center permissions. An admin must grant them in the ThreatLocker portal; retrying will not help.

Audit Log

  • threatlocker_audit_search - Search audit log entries with filters. searchText is a path filter (ThreatLocker fullPath), not free text: it matches the file path and also each row's process path and created-by path, so a program's path also finds what that program did. Give a full path or use * wildcards (*\setup.msi). Filter by computer with hostname. Pass childOrganizations: true for computers in child organizations. Filter by result with actionId (1 Permit, 2 Deny, 3 Deny with option to request, 6 Ringfenced, 99 Any Deny; onlyTrueDenies / simulateDeny split enforced from monitor-only denies) and by actionType (execute, install, network, ...). groupBys counts rows by one or two fields, so actionId: 2, groupBys: [6, 9] breaks denies down by policy name and action type. These filters need the SDK release that adds them; older SDKs send only actionType
  • threatlocker_audit_get - Get one audit log entry; pass eActionLogId, sourceTableId and organizationId straight from the threatlocker_audit_search row (organizationId is required for rows from child organizations; deprecated alias: actionLogId). HTTP 500 is reported as an actionable error: re-search and pass all three fields from the same row
  • threatlocker_audit_file_history - Get audit history for a file. Requires fullPath and either hostname or computerId. For a computer in a child organization also pass organizationId (from its threatlocker_computers_list row); without it the result is empty. Needs @wyre-ai/node-threatlocker with getFileHistory({ organizationId }) support

Organizations

  • threatlocker_organizations_list_children - List child organizations
  • threatlocker_organizations_get_auth_key - Get the installation auth key for the organization the configured credentials are scoped to. The result is a sensitive key and is never logged. Reports an explicit error instead of {} when ThreatLocker returns no JSON key, and returns text bodies with SDK 3.0.2
  • threatlocker_organizations_for_move_computers - Get organizations for computer moves

Configuration

Environment Variables

Stdio Mode (Direct API Access)
bash
THREATLOCKER_API_KEY=your_api_key_hereTHREATLOCKER_ORGANIZATION_ID=your_org_id_hereMCP_TRANSPORT=stdio
Gateway Mode (Multi-tenant)
bash
AUTH_MODE=gatewayMCP_TRANSPORT=httpMCP_HTTP_PORT=8080# Required. The HTTP server exits non-zero if this is empty.CONDUIT_S2S_SECRET=gateway-provisioned-secret# Optional. Unset binds 127.0.0.1. The container image sets 0.0.0.0.# MCP_HTTP_HOST=127.0.0.1

CONDUIT_S2S_SECRET is required for the HTTP transport. The process logs an error and exits non-zero when it is unset. For local development only, MCP_ALLOW_INSECURE_DEV=1 starts the server anyway and logs a loud warning; do not set that flag in production. The secret is never written to the logs.

When MCP_HTTP_HOST is unset, the server binds 127.0.0.1. The Dockerfile sets MCP_HTTP_HOST=0.0.0.0 so the process listens inside the container; publish that port on localhost.

Gateway Mode Headers

When running in gateway mode, include these headers with each request:

  • X-Gateway-S2S: Service-to-service proof from the gateway (t=<unix>,v1=<hmac>). Requests without a valid header are rejected with 401 when CONDUIT_S2S_SECRET is set.
  • X-Threatlocker-Api-Key: Your ThreatLocker API key (required). A request without it is rejected with 401 and does not fall back to THREATLOCKER_API_KEY.
  • X-Threatlocker-Organization-Id: Your organization ID (optional; the API defaults to the key's primary organization)

/health and /healthz stay unauthenticated and do not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

Logging

bash
LOG_LEVEL=debug|info|warn|error  # Default: info

Local Development

  1. Clone the repository:
bash
git clone https://github.com/WYRE-AI/threatlocker-mcp.gitcd threatlocker-mcp
  1. Install dependencies:
bash
npm install
  1. Set environment variables:
bash
cp .env.example .env# Edit .env with your ThreatLocker credentials
  1. Build and run:
bash
npm run buildnpm start
# Or for development with hot reload:npm run dev
  1. Test the server:
bash
# Stdio modeecho '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}' | npm start
# HTTP mode. CONDUIT_S2S_SECRET is required unless you set# MCP_ALLOW_INSECURE_DEV=1 (local development only; logs a loud warning).# The server binds 127.0.0.1 unless MCP_HTTP_HOST is set.MCP_TRANSPORT=http AUTH_MODE=gateway CONDUIT_S2S_SECRET=dev-secret npm run start:httpcurl http://127.0.0.1:8080/health

Docker

Using Docker Compose

bash
# Required. Compose will not start if this is unset or empty.export CONDUIT_S2S_SECRET=gateway-provisioned-secret
# Pull and run latest image. The published port is 127.0.0.1:8080.docker compose up -d
# Or build locallydocker compose -f docker-compose.dev.yml up --build

Using Docker directly

bash
# Gateway mode (recommended). The container listens on 0.0.0.0 inside# the network namespace; publish it on localhost only. The process# exits if CONDUIT_S2S_SECRET is empty.docker run -d \  --name threatlocker-mcp \  -p 127.0.0.1:8080:8080 \  -e AUTH_MODE=gateway \  -e CONDUIT_S2S_SECRET=gateway-provisioned-secret \  ghcr.io/wyre-ai/threatlocker-mcp:latest
# Stdio modedocker run -d \  --name threatlocker-mcp \  -e THREATLOCKER_API_KEY=your_key \  -e THREATLOCKER_ORGANIZATION_ID=your_org_id \  -e MCP_TRANSPORT=stdio \  ghcr.io/wyre-ai/threatlocker-mcp:latest

Architecture

Directory Structure

src/├── domains/           # Domain-specific handlers│   ├── computers.ts│   ├── computer_groups.ts│   ├── approval_requests.ts│   ├── audit_log.ts│   ├── organizations.ts│   ├── navigation.ts│   └── index.ts├── utils/             # Utilities│   ├── client.ts      # ThreatLocker API client│   ├── logger.ts      # Structured logging│   ├── types.ts       # TypeScript types│   ├── server-ref.ts  # Server reference for elicitation│   └── elicitation.ts # Interactive prompts├── server.ts          # MCP server creation├── index.ts           # Stdio transport entry└── http.ts            # HTTP transport entry

Design Patterns

  • Domain Handlers: Each API area has its own handler with getTools() and handleCall()
  • Lazy Loading: Domain handlers are imported on-demand
  • Fresh Connections: New server instance per HTTP request for stateless operation
  • Credential Invalidation: Client is reset when credentials change
  • Elicitation Framework: Interactive prompts for missing parameters

License

Apache-2.0 - see LICENSE for details.

Source: README.md at commit af389e2

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

8
  1. v1.4.2LatestNov 21, 2026
  2. v1.4.1Nov 14, 2026
  3. v1.4.0Nov 12, 2026
  4. v1.3.14Nov 11, 2026
  5. v1.3.12Oct 10, 2026
  6. v1.3.11Oct 9, 2026
  7. v1.3.10Sep 24, 2026
  8. v1.3.9Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.