ThreatLocker
Rank #8,172io.github.WYRE-AI/threatlocker-mcp
MCP server for ThreatLocker — zero-trust endpoint protection, allowlisting, and policies.
What you can do with ThreatLocker
ThreatLocker is a Model Context Protocol (MCP) server published by wyre-technology. It ranks #8,172 of 144,396 active servers on MCP Toplist, and its repository has 1 GitHub stars. ThreatLocker is listed across 3 registries — Official MCP, PulseMCP and Glama, with 17 tracked versions. It was first listed on May 18, 2026 and most recently updated on Oct 10, 2026.
Not verifiedMCP Toplist has not yet written a checked profile for this server, so the paragraph above is assembled from registry data only. The repository README is the authority on what it does.
What ThreatLocker can and cannot do
Not verifiedMCP Toplist has not catalogued this server's tools or limitations. The repository README lists them.
What you need before using ThreatLocker
The registry listing declares no required environment variables or authentication. This is declared metadata, not a verified install — the repository README is the authority.
Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
- THREATLOCKER_API_KEY · required
- THREATLOCKER_ORGANIZATION_ID · required
- MCP_TRANSPORT · optional
- AUTH_MODE · optional
- LOG_LEVEL · optional
Connect ThreatLocker and confirm it works
claude mcp add threatlocker-mcp -e "THREATLOCKER_API_KEY=<your THREATLOCKER_API_KEY>" -e "THREATLOCKER_ORGANIZATION_ID=<your THREATLOCKER_ORGANIZATION_ID>" -e "MCP_TRANSPORT=<your MCP_TRANSPORT>" -e "AUTH_MODE=<your AUTH_MODE>" -e "LOG_LEVEL=<your LOG_LEVEL>" -- docker run -i --rm ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12Replace each placeholder with your own value before saving.
[mcp_servers.threatlocker-mcp]
command = "docker"
args = ["run", "-i", "--rm", "ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"]
[mcp_servers.threatlocker-mcp.env]
THREATLOCKER_API_KEY = "<your THREATLOCKER_API_KEY>"
THREATLOCKER_ORGANIZATION_ID = "<your THREATLOCKER_ORGANIZATION_ID>"
MCP_TRANSPORT = "<your MCP_TRANSPORT>"
AUTH_MODE = "<your AUTH_MODE>"
LOG_LEVEL = "<your LOG_LEVEL>"Add to ~/.codex/config.toml. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"
],
"env": {
"THREATLOCKER_API_KEY": "<your THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<your THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<your MCP_TRANSPORT>",
"AUTH_MODE": "<your AUTH_MODE>",
"LOG_LEVEL": "<your LOG_LEVEL>"
}
}
}
}Add to claude_desktop_config.json (Settings → Developer → Edit Config). Replace each placeholder with your own value before saving.
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"
],
"env": {
"THREATLOCKER_API_KEY": "<your THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<your THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<your MCP_TRANSPORT>",
"AUTH_MODE": "<your AUTH_MODE>",
"LOG_LEVEL": "<your LOG_LEVEL>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project). Replace each placeholder with your own value before saving.
{
"servers": {
"threatlocker-mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"
],
"env": {
"THREATLOCKER_API_KEY": "<your THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<your THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<your MCP_TRANSPORT>",
"AUTH_MODE": "<your AUTH_MODE>",
"LOG_LEVEL": "<your LOG_LEVEL>"
}
}
}
}Save as .vscode/mcp.json in your workspace. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"
],
"env": {
"THREATLOCKER_API_KEY": "<your THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<your THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<your MCP_TRANSPORT>",
"AUTH_MODE": "<your AUTH_MODE>",
"LOG_LEVEL": "<your LOG_LEVEL>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json. Replace each placeholder with your own value before saving.
{
"mcpServers": {
"threatlocker-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/threatlocker-mcp:v1.3.12"
],
"env": {
"THREATLOCKER_API_KEY": "<your THREATLOCKER_API_KEY>",
"THREATLOCKER_ORGANIZATION_ID": "<your THREATLOCKER_ORGANIZATION_ID>",
"MCP_TRANSPORT": "<your MCP_TRANSPORT>",
"AUTH_MODE": "<your AUTH_MODE>",
"LOG_LEVEL": "<your LOG_LEVEL>"
}
}
}
}Replace each placeholder with your own value before saving.
After adding the config, ask your client to list this server's tools. A tool list confirms the connection; an empty list or an error means the server did not start or needs credentials.
When to choose another server
- Autotask#736
- ConnectWise Manage#1,574
- NinjaOne#1,726
- IT Glue#2,089
- CIPP#3,001
- HaloPSA#4,242
- Syncro#4,451
- Datto RMM#4,596
- SuperOps#5,267
- Hudu#5,405
- Action1#5,748
- QuickBooks Online#5,839
No task-specific alternatives are catalogued for ThreatLockeryet; the list above is its publisher's other servers.
What changed, and when this was checked
- First listed
- May 18, 2026
- Latest version published
- Oct 10, 2026
- Version history
- 17 versions tracked (below)
- Requirements evidence
- Declared by Glama, last synced Oct 16, 2026. Not independently verified by MCP Toplist.
- Profile checked
- Not yet — purpose, capabilities and requirements above come from registry data only
- Ranking data as of
- Oct 16, 2026
- PulseMCP ↗listed since May 23, 2026 · still listed
- Glama ↗listed since May 27, 2026 · delisted, last seen Aug 26, 2026
- Official MCP ↗listed since Jul 24, 2026 · still listed
- Official MCP ↗listed since Aug 27, 2026 · still listed
- Glama ↗listed since Sep 4, 2026 · still listed
Do you maintain ThreatLocker? to correct or enrich this profile.
Available versions (17)
| Version | Published |
|---|---|
| 1.3.12 | Oct 10, 2026 |
| 1.3.11 | Oct 9, 2026 |
| 1.3.10 | Sep 24, 2026 |
| 1.3.9 | Sep 8, 2026 |
| 1.3.8 | Aug 26, 2026 |
| 1.3.6 | Aug 20, 2026 |
| 1.3.5 | Aug 20, 2026 |
| 1.3.4 | Aug 13, 2026 |
| 1.3.3 | Aug 13, 2026 |
| 1.3.2 | Aug 10, 2026 |
| 1.3.1 | Aug 10, 2026 |
| 1.3.0 | Aug 10, 2026 |
| 1.2.5 | Jul 22, 2026 |
| 1.2.4 | Jul 19, 2026 |
| 1.2.3 | Jul 18, 2026 |
| 1.2.2 | May 22, 2026 |
| 1.2.1 | May 22, 2026 |
Ranks ahead of 136,224 of 144,396 servers on MCP Toplist.
Show your rank
Maintain this server? Add the live rank badge to your README — it updates automatically as the leaderboard changes.
[](https://mcptoplist.com/server/io.github.WYRE-AI%2Fthreatlocker-mcp)<a href="https://mcptoplist.com/server/io.github.WYRE-AI%2Fthreatlocker-mcp"><img src="https://mcptoplist.com/badge/io.github.WYRE-AI%2Fthreatlocker-mcp.svg" alt="MCP Toplist: Top 10% of 144,396" /></a>Variants: append ?metric=score or ?metric=stars to the image URL.
Frequently asked questions
- Who maintains ThreatLocker?
- ThreatLocker is maintained by wyre-technology, which publishes 60 MCP servers (872 total versions) tracked on MCP Toplist.
- Is ThreatLocker listed on the Official MCP Registry?
- Yes — ThreatLocker is listed on the Official MCP Registry, alongside PulseMCP and Glama.
- How many versions does ThreatLocker have?
- MCP Toplist tracks 17 versions of ThreatLocker, most recently published on Oct 10, 2026.
- Where can I find the source code for ThreatLocker?
- The source code for ThreatLocker is hosted at github.com/wyre-technology/threatlocker-mcp.
Do you run this server?
Community projects list the MCP servers behind real agents and apps. Publish yours and this page will link to it.