InnerVault

ThreatLocker MCP

Stale Official MCP Registry, io.github.Servosity

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

Open the source (opens github.com) https://github.com/servosity/msp-skills

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_MCP_HTTP_TOKEN. Use a key with the least access you can.

What it is

MCP servers from io.github.Servosity.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

mcpb package (stdio)

https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.17/threatlocker-mcp.mcpb@0.3.17

From the server's entry in the official MCP Registry

Settings it asks for

  • PRINTING_PRESS_CLIENT_PROFILE secret required · Set the PRINTING_PRESS_CLIENT_PROFILE credential for the ThreatLocker MCP server.
  • THREATLOCKER_API_KEY secret required · 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…
  • 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 secret · Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.

Related

  1. ThreatLocker

    MCP servers

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

    Stale Official MCP Registry, io.github.WYRE-AI Updated 3 days ago 2 notes

    ghcr.io/wyre-ai/threatlocker-mcp:v1.4.1
  2. ThreatLocker

    MCP servers

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

    Stale Official MCP Registry, io.github.wyre-technology Updated 2 months ago 2 notes

    ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
  3. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  4. Apify MCP server

    MCP servers

    Lets an agent run Apify's ready-made scrapers to pull data from websites, search engines, maps and social platforms.

    Hand-checked InnerVault (hand-checked), Apify 16.0k ★MIT

  5. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  6. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0