Loading
ThreatLocker MCP
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpbCredentials from the publisher
- PRINTING_PRESS_CLIENT_PROFILE — Set the PRINTING_PRESS_CLIENT_PROFILE credential for the ThreatLocker MCP server.
- THREATLOCKER_API_KEY — Portal API key (ThreatLocker portal: Settings > API Keys), sent as the Authorization header on every call.
- THREATLOCKER_BASE_URL — Base URL for the ThreatLocker API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
- THREATLOCKER_ORG_ID — 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 — 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 — Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
- THREATLOCKER_NO_LOCAL_DATA — 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 — Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
PRINTING_PRESS_CLIENT_PROFILE=<secret> THREATLOCKER_API_KEY=<secret> THREATLOCKER_BASE_URL=<value> THREATLOCKER_ORG_ID=<value> THREATLOCKER_USER_AGENT=<value> THREATLOCKER_MCP_READ_ONLY=<value> THREATLOCKER_NO_LOCAL_DATA=<value> THREATLOCKER_MCP_HTTP_TOKEN=<secret> claude mcp add io.github.servosity-threatlocker-mcp -- mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpbRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.servosity-threatlocker-mcp": { "command": "mcpb", "args": [ "https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpb" ], "env": { "PRINTING_PRESS_CLIENT_PROFILE": "<secret>", "THREATLOCKER_API_KEY": "<secret>", "THREATLOCKER_BASE_URL": "<value>", "THREATLOCKER_ORG_ID": "<value>", "THREATLOCKER_USER_AGENT": "<value>", "THREATLOCKER_MCP_READ_ONLY": "<value>", "THREATLOCKER_NO_LOCAL_DATA": "<value>", "THREATLOCKER_MCP_HTTP_TOKEN": "<secret>" } } }}claude_desktop_config.json
Local · mcpbPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Local- Transport
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ