eset-protect-mcp

ESET PROTECT MCP Server

A Model Context Protocol (MCP) server for ESET PROTECT — supports both On-Prem and Cloud (ESET Connect).

Manage devices, policies, detections, incidents, quarantine, executables, installers, EDR rules, automation tasks, and more through natural language with GitHub Copilot, Claude Desktop, or any MCP client.

npx -y eset-protect-mcp

Features

Shared Tools (On-Prem + Cloud) — 18 tools

Category	Tools
Devices	list_devices, get_device, batch_get_devices, move_device, rename_device
Device Groups	list_device_groups, list_devices_in_group
Policies	list_policies, get_policy, create_policy, build_endpoint_policy_clone_with_mutation, create_endpoint_policy_clone_with_mutation, delete_policy
Policy Assignments	list_policy_assignments, get_policy_assignment, assign_policy, unassign_policy, update_policy_assignment_ranking

Cloud-Only Tools (ESET Connect) — 78 additional tools

Category	Tools
Devices (extra)	batch_import_devices
Asset Management	create_group, delete_group, move_group, rename_group
Automation	list_device_tasks, create_device_task, get_device_task, delete_device_task, list_device_task_runs, update_device_task_targets, update_device_task_triggers
Identity	list_permissions, list_role_assignments, assign_role, revoke_role, create_role, delete_role
Detections	list_detections, list_detections_v2, get_detection, resolve_detection, batch_get_detections
Detection Groups	list_detection_groups, get_detection_group, resolve_detection_group, search_detection_groups
EDR Rules	list_edr_rules, create_edr_rule, get_edr_rule, delete_edr_rule, enable_edr_rule, disable_edr_rule, update_edr_rule_definition
EDR Rule Exclusions	list_edr_rule_exclusions, create_edr_rule_exclusion, get_edr_rule_exclusion, delete_edr_rule_exclusion, update_edr_rule_exclusion_definition
Incidents	list_incidents, get_incident, close_incident, reopen_incident, update_incident_attributes
Incident Comments	list_incident_comments, create_incident_comment, get_incident_comment, delete_incident_comment, update_incident_comment_text
Executables	list_executables, search_executables, get_executable, block_executable, unblock_executable
Quarantine	list_quarantined_objects, get_quarantined_object, get_quarantine_count, batch_delete_quarantined_objects, batch_download_quarantined_objects, batch_restore_quarantined_objects, download_quarantined_object, purge_quarantined_objects, restore_quarantined_object
Installers	list_installers, get_installer, create_installer, delete_installer, generate_gpo_sccm_file
Mobile Devices	batch_activate_mobile_product, batch_get_enrollment_links
Network Access	list_ip_sets, get_ip_set, update_ip_set
Users	list_users, get_user, batch_get_users
Web Access	list_web_address_rules, update_web_address_rule_domains

Incident filters use unquoted enum constants. For example, use status==INCIDENT_STATUS_OPEN, not status=="INCIDENT_STATUS_OPEN".

Use search_executables with hashSha1 or displayName to resolve the executableUuid required by block_executable. ESET exposes executable listing with pagination only, so the MCP server scans pages client-side.

For automation troubleshooting, create_device_task adds a specific hint when Run Command task creation returns an empty-body HTTP 500. Use list_device_task_runs with includeFailureSummary=true to append _mcpFailureSummary from status, error, reason, and exit-code fields.

For create_incident_comment, pass {"text":"..."}. The MCP server wraps it into ESET's required {"comment":{"incidentUuid":"...","text":"..."}} request body.

Policy and assignment inventory tools support pagination with pageSize and pageToken: list_device_groups, list_policies, list_policy_assignments, and list_ip_sets. Use get_policy with decodePolicyData=true to recursively decode base64 PolicyData blobs into _mcpDecodedPolicyData for troubleshooting product settings such as firewall/network protection. If decoded policy data contains an ar archive after the first JSON object, *.lzma members such as endpoint.lzma are decompressed and exposed under archiveMembers[].decoded. list_ip_sets is limited by ESET to Common features policies; unsupported policies may return HTTP 400, while HTTP 500 with an empty body should be treated as an upstream ESET failure for the policy or tenant.

For large endpoint policies, combine get_policy options to keep output focused: omitRawPolicyData=true removes raw base64 blobs, decodedSearch="firewall" returns decoded matches, and decodedPath="archiveMembers[0].decoded.parsed.Settings" extracts a specific decoded path. When decodedPath or decodedSearch is used, full decoded policy data is omitted by default; set includeFullDecodedPolicyData=true to include it.

ESET Connect exposes only limited dedicated network/web policy mutation APIs: Network Access Protection supports list_ip_sets, get_ip_set, and update_ip_set; Web Access Protection supports list_web_address_rules and update_web_address_rule_domains. Other firewall rule create/update/delete work must be handled through policy data updates rather than a dedicated firewall-rule CRUD endpoint.

ESET Connect does not expose an update endpoint for existing policies. To change endpoint firewall settings safely, use build_endpoint_policy_clone_with_mutation to generate a create_policy payload, or create_endpoint_policy_clone_with_mutation to create a cloned policy with a decoded endpoint.lzma JSON mutation. The source policy is not modified. Typical firewall rule insertion path: policy.data.Settings.Firewall.Rules.ce_value.

Prerequisites

• Node.js >= 18.0.0
• On-Prem: ESET PROTECT On-Prem 13.0+ with REST API enabled
• Cloud: ESET Business Account / ESET PROTECT Hub with API user (Integrations enabled)

Installation

From npm

npm install -g eset-protect-mcp

From GitHub

git clone https://github.com/Fenrindale/eset-protect-mcp.git
cd eset-protect-mcp
npm install
npm run build

Configuration

Environment Variables

Variable	Required	Description
ESET_MODE	No	onprem (default) or cloud
ESET_USERNAME	Yes	API username / email
ESET_PASSWORD	Yes	API password
ESET_SERVER_URL	On-Prem only	Server URL (e.g., https://protect-server:9443)
ESET_VERIFY_SSL	On-Prem only	false to allow self-signed certs (default: true)
ESET_REGION	Cloud only	eu, de, us, jpn, or ca
ESET_REQUEST_TIMEOUT_MS	No	HTTP request timeout in milliseconds (default: 120000)
ESET_EXECUTABLE_SEARCH_MAX_PAGES	No	Max pages scanned by search_executables (default: 20)
ESET_EXECUTION_MODE	No	live (default), read-only, dry-run, or scoped
ESET_ALLOWED_TOOLS	No	Comma-separated tool allowlist
ESET_DENIED_TOOLS	No	Comma-separated tool blocklist
ESET_REQUIRE_APPROVAL	No	none, all, risk levels (low_write, high_write, destructive), or tool names
ESET_APPROVALS_DIR	No	Approval record directory (default: .eset-mcp/approvals)
ESET_APPROVAL_TOKEN	No	Token required by the local approve_action tool
ESET_APPROVAL_TTL_SECONDS	No	Approval validity window (default: 900)
ESET_AUDIT_LOG	No	JSONL audit log path for tool decisions and executions
ESET_ALLOWED_DEVICE_UUIDS	No	Comma-separated device UUID allowlist for scoped mode
ESET_ALLOWED_GROUP_UUIDS	No	Comma-separated group UUID allowlist for scoped mode
ESET_ALLOWED_RULE_UUIDS	No	Comma-separated EDR rule UUID allowlist for scoped mode
ESET_ALLOW_GLOBAL_SCOPE	No	true to allow global EDR exclusions in scoped mode

Approval and Sandbox Controls

The server includes a local policy gate before any ESET API call. The default live mode preserves existing behavior.

Mode	Behavior
live	Execute tools normally, unless allow/deny/approval variables are configured
read-only	Allow only list_*, get_*, batch_get_*, and search_* tools
dry-run	Return a sanitized action summary for write tools without calling ESET
scoped	Enforce configured UUID allowlists and require approval for high_write and destructive tools by default

Write tools are classified as low_write, high_write, or destructive. When approval is required, the first tool call returns approvalRequired, writes a pending approval record, and does not call ESET. A human can then approve it with the local approve_action tool or by writing a matching JSON approval file under ESET_APPROVALS_DIR. Approved actions are one-shot and are consumed after execution.

Two local security tools are always registered:

Tool	Purpose
list_pending_approvals	Show pending approval records from the local approval store
approve_action	Approve or deny one pending action when ESET_APPROVAL_TOKEN is configured

Example guarded configuration:

ESET_EXECUTION_MODE=scoped
ESET_REQUIRE_APPROVAL=high_write,destructive
ESET_ALLOWED_RULE_UUIDS=rule-uuid-1,rule-uuid-2
ESET_ALLOWED_GROUP_UUIDS=group-uuid-1
ESET_AUDIT_LOG=/var/log/eset-mcp-audit.jsonl

Usage with MCP Clients

VS Code / GitHub Copilot — On-Prem

{
  "mcp": {
    "servers": {
      "eset-protect": {
        "command": "npx",
        "args": ["-y", "eset-protect-mcp"],
        "env": {
          "ESET_MODE": "onprem",
          "ESET_SERVER_URL": "https://your-protect-server:9443",
          "ESET_USERNAME": "your-api-user",
          "ESET_PASSWORD": "your-api-password",
          "ESET_VERIFY_SSL": "false"
        }
      }
    }
  }
}

VS Code / GitHub Copilot — Cloud

{
  "mcp": {
    "servers": {
      "eset-protect": {
        "command": "npx",
        "args": ["-y", "eset-protect-mcp"],
        "env": {
          "ESET_MODE": "cloud",
          "ESET_REGION": "eu",
          "ESET_USERNAME": "[e-mail]",
          "ESET_PASSWORD": "your-api-password"
        }
      }
    }
  }
}

Claude Desktop — On-Prem

{
  "mcpServers": {
    "eset-protect": {
      "command": "npx",
      "args": ["-y", "eset-protect-mcp"],
      "env": {
        "ESET_MODE": "onprem",
        "ESET_SERVER_URL": "https://your-protect-server:9443",
        "ESET_USERNAME": "your-api-user",
        "ESET_PASSWORD": "your-api-password",
        "ESET_VERIFY_SSL": "false"
      }
    }
  }
}

Claude Desktop — Cloud

{
  "mcpServers": {
    "eset-protect": {
      "command": "npx",
      "args": ["-y", "eset-protect-mcp"],
      "env": {
        "ESET_MODE": "cloud",
        "ESET_REGION": "us",
        "ESET_USERNAME": "[e-mail]",
        "ESET_PASSWORD": "your-api-password"
      }
    }
  }
}

ESET PROTECT API Setup

On-Prem

• Enable the REST API in More > Settings on your ESET PROTECT Web Console
• Open API ports in your firewall (default: 9443)
• Create an API user with appropriate permission sets

Note: The Administrator account cannot use the API.

Docs: ESET PROTECT On-Prem REST API

Cloud (ESET Connect)

• Log in to ESET Business Account / ESET PROTECT Hub as Superuser
• Create an API user with Integrations enabled under Access Rights
• The user must complete account setup via invitation email
• Use the correct region (eu, de, us, jpn, ca) matching your ESET PROTECT server location

Docs: ESET Connect

Cloud Regions & Domains

Region	Auth Domain
EU	eu.business-account.iam.eset.systems
Germany	de.business-account.iam.eset.systems
USA	us.business-account.iam.eset.systems
Japan	jpn.business-account.iam.eset.systems
Canada	ca.business-account.iam.eset.systems

Development

git clone https://github.com/Fenrindale/eset-protect-mcp.git
cd eset-protect-mcp
npm install
npm run build
npm start

Release

CI runs on pushes and pull requests to master.

To publish from GitHub Actions, configure npm Trusted Publishing for this package:

Field	Value
Publisher	GitHub Actions
Organization or user	Fenrindale
Repository	eset-protect-mcp
Workflow filename	publish.yml
Allowed actions	npm publish

Then release by bumping the package version and pushing the matching tag:

npm version patch
git push origin master --follow-tags

License

MIT — see LICENSE for details.