Skip to main content
Glama
BigfootBytes

threatlocker-mcp-server

by BigfootBytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to threatlocker-mcp-server

No user-submitted related servers found.

    Related Servers

    • threatlocker-mcp

      Space-C0wboy
      A
      license
      C
      quality
      D
      maintenance
      An MCP server that connects AI assistants to the ThreatLocker Portal API with 44 tools for managing computers, approvals, action logs, tags, maintenance mode, and more across single-org and multi-tenant setups.
      44
      1
      MIT
    • DelineaMCP by DelineaXPM

      DelineaMCPofficial

      DelineaXPM
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Delinea Secret Server and Platform APIs, enabling AI agents to manage secrets, users, groups, folders, roles, and access requests through natural language commands.
      46
      MIT

    • trmm-mcp

      shin2344234
      A
      license
      B
      quality
      A
      maintenance
      MCP server that gives AI assistants read-only access to TacticalRMM fleet data (agents, checks, alerts, services, processes, etc.) and, with explicit approval, lets them run commands on managed machines.
      20
      2
      AGPL 3.0

    • LegacyMCP

      Marco-Lelli
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI-powered assessment of Active Directory on-premises environments by exposing AD data as queryable tools for LLMs like Claude.
      MIT

    • threatlocker-mcp

      WYRE-AI
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for ThreatLocker — zero-trust application allowlisting, approval requests, audit logs
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool maps to a distinct ThreatLocker domain—computers, groups, applications, policies, logs, approvals, organizations, reports, maintenance, scheduling, tags, storage/network policies, versions, online devices, saved searches, and upload requests. Potential overlaps like system_audit vs action_log and policies vs storage_policies/network_access_policies are clearly differentiated by both naming and description.

    Naming Consistency5/5

    All tools follow the same snake_case resource-noun pattern: computers, computer_groups, applications, policies, action_log, maintenance_mode, storage_policies, etc. While actions are passed via an 'action' parameter rather than verb-prefixed tool names, the convention is uniform and easy to predict.

    Tool Count4/5

    18 tools is above the ideal 3-15 range, but the count is justified by the breadth of the ThreatLocker platform—each tool covers a distinct functional area. It feels slightly heavy rather than bloated, and there are no redundant tools that could be merged.

    Completeness3/5

    Core lifecycle coverage is strong for applications and policies (create/update/delete/deploy), and there are solid querying tools for logs, approvals, and computers. However, several areas are read-only or lack management operations: computer_groups cannot be created/edited/deleted, storage_policies and network_access_policies are read-only, maintenance_mode is history-only, and scheduled_actions cannot be created or cancelled.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources