ThreatLocker MCP server
MCP server for ThreatLocker — zero-trust endpoint protection, allowlisting, and policies.
1 stars
Reviews
Write oneNobody has reviewed ThreatLocker yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ThreatLocker tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
How ThreatLocker compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Install ThreatLocker in Claude Code, Cursor or VS Code
claude mcp add threatlocker-mcp -- docker run -i --rm ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
What the publisher says
From the ThreatLocker repository's README, as published. We do not edit it. Read it on GitHub
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
- threatlockercomputerslist - List computers with filters (search, group, pagination)
- threatlockercomputersget - Get detailed computer information
- threatlockercomputersget_checkins - Get computer checkin history
Computer Groups
- threatlockercomputergroups_list - List computer groups with filters
- threatlockercomputergroups_dropdown - Get computer groups for dropdown selection
Approval Requests
- threatlockerapprovalslist - List approval requests with status filters
- threatlockerapprovalsget - Get detailed approval request information
- threatlockerapprovalspending_count - Get count of pending approvals
- threatlockerapprovalsgetpermitapplication - Get permit application details
Audit Log
- threatlockerauditsearch - Search audit log entries with filters
- threatlockerauditget - Get detailed audit log entry
- threatlockerauditfile_history - Get audit history for specific file
Organizations
- threatlockerorganizationslist_children - List child organizations
- threatlockerorganizationsgetauthkey - Get organization auth key
- threatlockerorganizationsformovecomputers - 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=stdioGateway Mode (Multi-tenant)
AUTH_MODE=gateway
MCP_TRANSPORT=http
MCP_HTTP_PORT=8080
MCP_HTTP_HOST=0.0.0.0Gateway Mode Headers
When running in gateway mode, include these headers with each request:
- X-Threatlocker-Api-Key: Your ThreatLocker API key
- X-Threatlocker-Organization-Id: Your organization ID
Logging
LOG_LEVEL=debug|info|warn|error # Default: infoLocal Development
- Clone the repository:
git clone https://github.com/WYRE-AI/threatlocker-mcp.git
cd threatlocker-mcp- Install dependencies:
npm install- Set environment variables:
cp .env.example .env
# Edit .env with your ThreatLocker credentials- Build and run:
npm run build
npm start
# Or for development with hot reload:
npm run dev- Test the server:
# Stdio mode
echo '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}' | npm start
# HTTP mode
curl http://localhost:8080/healthDocker
Using Docker Compose
# Pull and run latest image
docker compose up -d
# Or build locally
docker compose -f docker-compose.dev.yml up --buildUsing Docker directly
# Gateway mode (recommended)
docker run -d \
--name threatlocker-mcp \
-p 8080:8080 \
-e AUTH_MODE=gateway \
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:latestArchitecture
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
ThreatLocker: common questions
- Is ThreatLocker MCP server safe?
- Mostly: it is graded B (75/100). Read the ThreatLocker safety report
- How do I install ThreatLocker?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does ThreatLocker need an API key?
- Yes. The registry entry asks for
THREATLOCKER_API_KEY. - Is ThreatLocker maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.3.6.
- How does ThreatLocker compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.