Summary

This deploys and deletes — treat the credential as production access.

Deployment, script execution, group deletion and endpoint removal (which uninstalls the agent) are all in the same toolset as the read-only inventory calls. The credential you configure is the blast radius. Set `ACTION1_ORG_ID` deliberately, or leave it out and pass the organisation per call, so a mistaken tool call cannot silently land in the wrong tenant. Testing goes through the MCP Inspector rather than a shell, since the server speaks over stdio.

What it is

An unofficial but broad server over the Action1 RMM REST API. It exposes device inventory, vulnerability data, deployments, automations and reporting as tools, so fleet work can be driven from a conversation.

What you get

Endpoints: `list_endpoints`, `get_endpoint`, `update_endpoint`, `delete_endpoint`, `list_discovery_endpoints`, plus `requery_installed_apps` and `requery_installed_updates` to force a refresh
Vulnerabilities and updates: `list_vulnerabilities`, filterable by severity, and `list_windows_updates`
Deployments: `deploy_updates` with CVE targeting, reboot rules and retry windows, `deploy_software` from the catalogue, and `run_script` from the script library
Groups: `list_endpoint_groups`, `get_endpoint_group_contents`, `add_endpoint_to_group`, `update_endpoint_group`, `delete_endpoint_group`
Policies and results: `list_policies`, `get_policy`, `get_policy_results` for per-endpoint success and failure detail
Automations: `list_automations`, `create_automation` for daily, weekly or monthly schedules, `update_automation`, `delete_automation`
Reporting: `list_reports`, `get_report_data`, `export_report` to CSV, `requery_report`, and `get_activity_logs` for the audit trail

Requirements

An Action1 account and API credentials — a Client ID and Client Secret created under Configuration, then Users & API Credentials. The project is mcp-action1, version 1.0.0, built from a checkout with `npm install` and `npm run build`, then launched as `node dist/index.js`. Node.js `v18.0.0` or higher. Configuration is four variables: `ACTION1_CLIENT_ID`, `ACTION1_CLIENT_SECRET`, `ACTION1_REGION` (`na`, `eu` or `au`) and an optional `ACTION1_ORG_ID`, which can also be passed per call.