Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Las reseñas y las cuentas llegarán en una etapa posterior.
PopNx MCPServidores MCP para quienes usan IA · explicados con palabras sencillas

ThreatLocker MCP

de servosityversión 0.3.13i★ –iSe ejecuta en tu computadora
Nombre en el registroio.github.Servosity/threatlocker-mcp

Instalar

Resumen

Descripción del creador (original en inglés)

Every ThreatLocker Portal API feature, plus the write operations the read-only tools lack and a

Los tres pilares de PopNx MCP

Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

  • Conexión: Se ejecuta en tu computadora
  • Transporte: stdio
  • Categoría: Otros
  • Debes completar: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_MCP_HTTP_TOKEN

Instalación

Elige la app de IA que usas y copia la configuración.

Antes de instalar

  • Revisiones básicas: 1 de 1 superadas
  • Se ejecuta en tu computadora con los permisos de tu usuario (archivos, red, apps).
  • Debes completar tú: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_BASE_URL, THREATLOCKER_ORG_ID, THREATLOCKER_USER_AGENT, THREATLOCKER_MCP_READ_ONLY, THREATLOCKER_NO_LOCAL_DATA, THREATLOCKER_MCP_HTTP_TOKEN

Los valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.

¿Qué app usas?

Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.

Descargar el archivo .mcpb del creador

El enlace lleva al archivo del propio creador; no lo alojamos ni lo reempaquetamos. Abre el archivo y Claude Desktop lo instalará.

Ejecuta esto en tu terminal

Completa los valores vacíos antes de ejecutarlo.

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.

Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

  • PRINTING_PRESS_CLIENT_PROFILE secreto obligatorio env
    Set the PRINTING_PRESS_CLIENT_PROFILE credential for the ThreatLocker MCP server.
  • THREATLOCKER_API_KEY secreto obligatorio env
    Portal API key (ThreatLocker portal: Settings > API Keys), sent as the Authorization header on every call.
  • THREATLOCKER_BASE_URL env
    Base URL for the ThreatLocker API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
  • THREATLOCKER_ORG_ID env
    Tenant GUID sent as ManagedOrganizationId (the --org flag overrides it). Most Portal API data calls answer 401/403 without it, so set it unless you pass --org on every call.
  • THREATLOCKER_USER_AGENT env
    Overrides the User-Agent the CLI sends on ThreatLocker requests. Leave blank to use the CLI's own built-in User-Agent.
  • THREATLOCKER_MCP_READ_ONLY env
    Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
  • THREATLOCKER_NO_LOCAL_DATA env
    Optional. Set to 1 to save no API data locally: sync and audit pull are refused, the response cache is off, and reads go to the API.
  • THREATLOCKER_MCP_HTTP_TOKEN secreto env
    Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub servosity, dueña del repo

  • … Aún sin revisar

    Sigue en mantenimiento

    Todavía no hemos leído este repo en GitHub

  • … Aún sin revisar

    Tiene licencia

    Todavía no hemos leído este repo en GitHub

  • – No aplica

    El endpoint responde

    Este se ejecuta en tu computadora; no hay endpoint en internet

  • – No aplica

    Inicio de sesión con OAuth

    Se ejecuta en tu computadora y usa ajustes locales en su lugar

  • … Aún sin revisar

    Sin instrucciones ocultas en las descripciones de herramientas

    Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet

Comparado con otros en Otrosi

  • Más estrellas que el 0% de los otros 32602 servidores de esta categoría
  • Publicado en el registro más recientemente que el 77% de los otros 32602 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 100% de los otros 32602 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro ThreatLocker MCP?

Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

Debes completar: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_MCP_HTTP_TOKEN

¿Se ejecuta en mi computadora o en la nube?

Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez –, y la última versión (0.3.13) llegó al registro hace 10 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.

¿Qué puedo usar en su lugar?

En la misma categoría: Spec Driven Development, Remote Desktop Commander, Rystic

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

Spec Driven Development

de formulahendry

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

Se ejecuta en tu computadora★ 440MITActualizado hace 14 meses
Instalar

Remote Desktop Commander

de desktop-commander

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

Se ejecuta en la nube★ 211Actualizado anteayer
Instalar

Rystic

de Rystic-Inc

Start, seed, clock, inspect and diff Rystic API simulators from your agent.

Se ejecuta en tu computadoraActualizado hoy
Instalar

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

ThreatLocker + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the ThreatLocker

API. Not affiliated with, endorsed by, or sponsored by ThreatLocker, Inc..

Full skill page - install, outcomes, safety model.

Every ThreatLocker Portal API feature, plus the write operations the read-only tools lack and a cross-tenant offline store no other ThreatLocker tool has. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

The six agents MSP owners actually use (self-serve, works today):

Your AI agentHow to install the ThreatLocker skill
Claude DesktopRun installer, then Settings > Extensions to register threatlocker-mcp (no JSON editing).
ChatGPT (desktop app)Run installer, then add threatlocker-mcp in Settings > MCP servers as a local (STDIO) server. ChatGPT on the web is not supported yet.
Codex CLIPaste the install prompt below.
Claude CodePaste the install prompt below.
Claude CoworkPaste the install prompt below.
GitHub Copilot (VS Code)Run installer, add threatlocker-mcp to mcp.json under the servers key, then pick Agent mode.

The ChatGPT desktop app runs threatlocker-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote server, which msp-skills does not support yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list. Setup steps: mcp-install.md.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

AgentWhat it takes
Microsoft 365 Copilot / Copilot StudioNot supported by msp-skills yet: it needs a remote server. A hosted gateway is the better pick; check that your AI app is on the gateway's setup list.
Google GeminiGemini CLI is local - same as Claude Code. See mcp-install.md. The Gemini app needs a remote server and is not supported by msp-skills yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Claude Desktop bundle: the .mcpb launches on macOS (Intel and Apple Silicon), Windows x64 and Linux x64. Every tool shells out to the companion threatlocker-cli. Releases cut from 2026-09-18 on ship that CLI inside the bundle; older bundles contain only the MCP server, so if yours lacks the companion, run the Path A or Path B installer below first (or set THREATLOCKER_CLI_PATH to an existing binary). Details: #331.

Download ThreatLocker MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every ThreatLocker release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install threatlocker@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the ThreatLocker Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.ps1 | iex. Then authenticate per the README and run threatlocker-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.sh)

The installer drops both threatlocker-cli (the CLI) and threatlocker-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

threatlocker-cli --version
Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/threatlocker/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update threatlocker@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/threatlocker --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/threatlocker --force

Hermes speaks MCP natively, so it can also use the threatlocker-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the threatlocker skill from https://github.com/servosity/msp-skills/tree/main/skills/threatlocker. The skill defines how its required CLI (threatlocker-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the credentials the CLI needs (from your ThreatLocker portal):

THREATLOCKER_API_KEY=<value> threatlocker-cli doctor

doctor confirms the credentials work before you run anything that touches data. It exits 0 even when the credential is rejected, so scripts should add --fail-on error.

What this skill does

Question your MSP keeps askingCommand
What application approvals are pending across all my clients right now?threatlocker-cli approvals triage --all-tenants
Approve this file hash everywhere it's pending, plan first?threatlocker-cli approvals approve-batch --hash --all-tenants --dry-run
Which clients are about to lose audit evidence to the 31-day retention cliff?threatlocker-cli audit retention-check
Save every client's blocked-file (deny) audit events locally before they age off?threatlocker-cli audit pull --since 30d
Export that saved audit log for a SIEM or an auditor?threatlocker-cli audit export --all-tenants --since 30d
What changed across all tenants this week, protection off, policy edits, maintenance?threatlocker-cli audit drift --since 7d --all-tenants
Which ThreatLocker agents are offline or stale across every client?threatlocker-cli devices health --all-tenants
Which tenants and endpoints asked to run this file, and which applications already trust it?threatlocker-cli applications hunt --hash
Which endpoints were left in maintenance mode?threatlocker-cli maintenance open --older-than 24h
Which tenant needs a look first?threatlocker-cli organizations posture

The audit rows read what audit pull saved, and the other rows read what sync saved: run threatlocker-cli sync and threatlocker-cli audit pull --since 30d first, and keep audit pull on a schedule shorter than 31 days.

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most ThreatLocker integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, because the Portal API is scoped one tenant at a time, so asking "show me every pending approval across all 40 clients, deduped by file hash" or "which clients are about to lose audit evidence this month" turns into a header-swap-and-re-query dance the AI burns context on, tenant by tenant.

This skill syncs ThreatLocker into a local SQLite mirror with full-text search. Aggregate questions become one local SQL join: instant, offline, and the AI sees the answer, not the raw data. Compound commands like approvals triage, applications hunt, and devices health join approval requests, applications, computers, and audit events across every tenant at once - work a stateless API wrapper can't do.

The pain this closes

ThreatLocker is default-deny, so every new or updated application becomes an approval request an admin has to clear. ThreatLocker's own MSP guide admits the volume: _"While you are onboarding your first few clients, your devices are learning and can be quite noisy"_ (Allowlisting for MSPs). Across a book of tenants the queue never goes quiet, and the Portal makes you clear it one tenant at a time. Then there's evidence: ThreatLocker's Help Center is explicit that _"by default, the Unified Audit retains data for 31 days. After 31 days, the information is permanently deleted and cannot be recovered"_ (Log Retention) - sho

Solo se muestra el principio; lee el resto en el repo

Pregunta a PopNx