Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

ThreatLocker

by wyre-technologyversion 1.3.6i★ –iRuns on your computer
Registry nameio.github.wyre-technology/threatlocker-mcp

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other
  • You need to fill in: THREATLOCKER_API_KEY, THREATLOCKER_ORGANIZATION_ID

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: THREATLOCKER_API_KEY, THREATLOCKER_ORGANIZATION_ID, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "threatlocker": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "THREATLOCKER_API_KEY",
        "-e",
        "THREATLOCKER_ORGANIZATION_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
      ],
      "env": {
        "THREATLOCKER_API_KEY": "your-value",
        "THREATLOCKER_ORGANIZATION_ID": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add threatlocker --env THREATLOCKER_API_KEY=your-value --env THREATLOCKER_ORGANIZATION_ID=your-value --env MCP_TRANSPORT=your-value --env AUTH_MODE=your-value --env LOG_LEVEL=your-value -- docker run -i --rm -e THREATLOCKER_API_KEY -e THREATLOCKER_ORGANIZATION_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "threatlocker": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "THREATLOCKER_API_KEY",
        "-e",
        "THREATLOCKER_ORGANIZATION_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
      ],
      "env": {
        "THREATLOCKER_API_KEY": "your-value",
        "THREATLOCKER_ORGANIZATION_ID": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "threatlocker": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "THREATLOCKER_API_KEY",
        "-e",
        "THREATLOCKER_ORGANIZATION_ID",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "AUTH_MODE",
        "-e",
        "LOG_LEVEL",
        "ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6"
      ],
      "env": {
        "THREATLOCKER_API_KEY": "your-value",
        "THREATLOCKER_ORGANIZATION_ID": "your-value",
        "MCP_TRANSPORT": "your-value",
        "AUTH_MODE": "your-value",
        "LOG_LEVEL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • THREATLOCKER_API_KEY secret required env
    ThreatLocker API key
  • THREATLOCKER_ORGANIZATION_ID required env
    ThreatLocker organization ID
  • MCP_TRANSPORT env
    Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE env
    Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL env
    Log verbosity: debug, info, warn, error

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account wyre-technology, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 18600 servers in this category
  • Published to the registry more recently than 27% of the other 18600 servers in this category
  • Basic checks equal to or better than 100% of the other 18600 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ThreatLocker safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: THREATLOCKER_API_KEY, THREATLOCKER_ORGANIZATION_ID

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.3.6) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, alalanet — check before you pay

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer
Install

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated 3 days ago

Runs in the cloud✓ desktopcommander.app
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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
Audit Log
  • threatlocker_audit_search - Search audit log entries with filters
  • threatlocker_audit_get - Get one audit log entry by eActionLogId from a search row (deprecated alias: actionLogId)
  • threatlocker_audit_file_history - Get audit history for a file. Requires fullPath and either hostname or computerId
Organizations
  • threatlocker_organizations_list_children - List child organizations
  • threatlocker_organizations_get_auth_key - Get organization auth key
  • threatlocker_organizations_for_move_computers - Get organizations for computer moves

Configuration

Environment Variables
Stdio Mode (Direct API Access)
THREATLOCKER_API_KEY=your_api_key_here

THREATLOCKER_ORGANIZATION_ID=your_org_id_here MCP_TRANSPORT=stdio

Gateway Mode (Multi-tenant)
AUTH_MODE=gateway

MCP_TRANSPORT=http MCP_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= ,v1= ). 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
LOG_LEVEL=debug|info|warn|error  # Default: info

Local Development

  1. Clone the repository:
git clone https://github.com/WYRE-AI/threatlocker-mcp.git

cd threatlocker-mcp

  1. Install dependencies:
npm install
  1. Set environment variables:
cp .env.example .env

Edit .env with your ThreatLocker credentials

  1. Build and run:
npm run build

npm start

Or for development with hot reload:

npm run dev

  1. Test the server:
# Stdio mode

echo '{"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:http curl http://127.0.0.1:8080/health

Docker

Using Docker Compose
# 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 locally

docker compose -f docker-compose.dev.yml up --build

Using Docker directly
# 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 mode

docker 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.

Ask PopNx