--- title: "Automox MCP server for AI agents - actionlake" description: "Give Claude 129 Automox actions through one MCP server: saved searches, remote control. Your agent never holds the credential. 100,000 calls a month free." canonical: https://actionlake.com/connectors/automox updated: 2026-10-23 --- Connectors · MSP & PSA # Automox MCP server for AI agents. actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Automox and the rest of your systems. It gives your agent 129 Automox actions (81 reads, 34 writes and 14 that wait for a confirmation) and holds the Automox credential itself, so the agent never does. It paces Automox's limits and records every call. [Connect Automox free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) 100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you. `claude mcp add --transport http actionlake https://connect.actionlake.com/mcp` the first call ``` do { action: "automox.global_api_keys.list", intent: "check which Automox account is connected" } # List Global API Keys · read · 1 upstream call ``` - 129 actions in one signed file - 81 read look, never change - 34 write create and update - 14 wait for a yes destructive, confirmed first Set up ## Connect Automox in three steps. 1. 01 ### Add actionlake to Claude. Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us. `https://connect.actionlake.com/mcp` 2. 02 ### Connect Automox. Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. actionlake stores what you paste write-only, sealed under your tenant's key. - `api_key` Automox API key ``` account { op: "connections.requirements", service: "automox" } # free: exactly what to paste, and what is found for you ``` 3. 03 ### Make the first call. Check before a write. Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free. ``` do { action: "automox.global_api_keys.list" } # list global api keys · read · 1 upstream call check { action: "automox.users.update", input: { … } } # free: inputs, permissions, cost and confirmations, nothing sent ``` Automox at a glance **Sign-in** Bearer token. No consent screen: your agent can connect it for you, but the key then passes through your chat. To keep it out of the model's context, paste it in the console instead. **You provide** `api_key` **Limits we pace to** 60 calls a minute, per connection **API covered** Automox Console API (console.automox.com/api)`console.automox.com` **Built from** Automox's documentation, read 23 October 2026[console.automox.com](https://console.automox.com/api/docs) **Service file** Version 1.0.0, signed (Ed25519) **Cached reads** 75 of 81 reads, for up to 5 minutes; a write clears what it affects **Shared entities** 4, so ask can line Automox up with your other systems **Data** Processed and stored in Sydney, Australia. No US region yet Capabilities ## What an AI agent can do in Automox. 129 actions in 46 areas. Every one carries its effect, so a key can allow the reads and hold the rest. - **81** read look, never change - **34** write create and update - **14** destructive wait for a confirmation 1. ### Saved searches 11 7 read · 3 write · 1 destructive List Search Cached Results · List Saved Searches · List Saved Searches Containing Device · List Saved Searches for a Given Device 2. ### Remote control 10 3 read · 5 write · 2 destructive List Attended Access Setting for Device · List Device Installation and Registration Status · List Device Session Status · Bulk Install or Uninstall Splashtop RMM client 3. ### Policy windows 9 6 read · 2 write · 1 destructive List the Next Scheduled Window Dates by Device. · List Next Scheduled Window Dates by Group · List a Scheduled Window · Check Whether a Scheduled Window is Currently Active 4. ### Policies 8 3 read · 4 write · 1 destructive List Policies · List Policy Details · Create a New Policy · Update a Policy 5. ### Webhooks 7 2 read · 3 write · 2 destructive List Webhooks · Get Webhook · Create Webhook · Update Webhook 6. ### User API keys 6 3 read · 2 write · 1 destructive List Organization API Keys for a User · Decrypt Organization API Key · List Specific Organization API Key by User ID · Create an Organization API Key for a User 7. ### Devices 5 2 read · 2 write · 1 destructive List Devices · List Device Details · Update a Device · Delete a Device 8. ### Global API keys 5 2 read · 2 write · 1 destructive List Global API Keys · Create Global API Key · Delete Global API · Update Global API Key Metadata **38 more areas · 68 actions** - Remediation action sets **5** - Server groups **5** - Users **4** - Cloud worklets **3** - Data extracts **3** - Device search metadata **3** - Policy history **3** - Policy runs **3** - Zones **3** - Account users **2** - Approvals **2** - Cloud worklet executions **2** - Device commands **2** - Device search **2** - Reports **2** - Worklet catalog **2** - Account invitations **1** - Account roles **1** - Account user zones **1** - Accounts **1** - Audit event types **1** - Audit events **1** - Cloud worklet types **1** - Device inventory **1** - Device inventory categories **1** - Device packages **1** - Events **1** - Organization API keys **1** - Organization packages **1** - Organizations **1** - Policy run devices **1** - Policy stats **1** - Remediation issues **1** - Remediation solutions **1** - Remediation upload formats **1** - Webhook deliveries **1** - Webhook event types **1** - Zone users **1** Top actions ## The Automox API, shaped for agents. The ids your agent types, what each does, and the one name it shares with other systems. 24 of Automox's 24 action names are shared with at least one other connector, so an agent learns them once. | Action | What it does | Effect | Same name in | | --- | --- | --- | --- | | `automox.users.list` List Organization Users (Legacy) | List Organization Users (Legacy). | read | `identity.user.list` 474 connectors | | `automox.users.get` List Organization User by ID | List Organization User by ID. | read | `identity.user.get` 399 connectors | | `automox.devices.list` List Devices | List Devices. | read | `device.endpoint.list` 65 connectors | | `automox.account_roles.list` List Account RBAC Roles | List Account RBAC Roles. | read | `identity.role.list` 184 connectors | | `automox.users.update` Fully Update a User | Fully Update a User. | write | `identity.user.update` 280 connectors | | `automox.policies.list` List Policies | List Policies. | read | `security.policy.list` 36 connectors | | `automox.global_api_keys.list` List Global API Keys | List Global API Keys. | read | `identity.api_key.list` 96 connectors | | `automox.global_api_keys.create` Create Global API Key | Create Global API Key. | write | `identity.api_key.create` 100 connectors | | `automox.devices.get` List Device Details | List Device Details. | read | `device.endpoint.get` 57 connectors | | `automox.webhooks.list` List Webhooks | List Webhooks. | read | `automation.webhook.list` 202 connectors | | `automox.global_api_keys.delete` Delete Global API | Delete Global API. | destructive | `identity.api_key.delete` 76 connectors | | `automox.global_api_keys.update` Update Global API Key Metadata | Update Global API Key Metadata. | write | `identity.api_key.update` 43 connectors | Try it ## Prompts to paste into Claude. Each one names the Automox actions it will call, so you know what it reads and what it changes before you send it. 1. Read read Which Automox devices have not checked in for a week? calls `automox.devices.list` 2. Write write Fully Update a User in Automox. Show me exactly what you will send before you save it. calls `automox.users.update` Governance for Automox ## Destructive actions wait for a yes. 14 Automox actions are destructive. These are all of them: - Delete Global API `automox.global_api_keys.delete` - Delete a Device `automox.devices.delete` - Delete a Policy `automox.policies.delete` - Delete Webhook `automox.webhooks.delete` - Delete Account User `automox.account_users.delete` - Delete Existing Server Group `automox.server_groups.delete` - Delete an Organization API Key by ID `automox.user_api_keys.delete` - Delete a Scheduled Window `automox.policy_windows.delete` - Delete Saved Search `automox.saved_searches.delete` - Uninstall and Delete Splashtop Device Registration `automox.remote_control.uninstall` - Delete an Action Set `automox.remediation_action_sets.delete` - Bulk Delete Action Sets `automox.remediation_action_sets.bulk_delete` - Rotate Webhook Secret `automox.webhooks.rotate_secret` - Force Disconnect All Active Splashtop Sessions on a Device `automox.remote_control.force_disconnect` A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after. do automox.global_api_keys.delete confirm_policy: **human** Delete Global API? **intent:** the user asked me to delete Global API run suspended · waiting for a named person · key _automox-agent_ cannot confirm itself In the console, or from an emailed signed link. a key for this connector ``` account { op: "keys.create", name: "automox-agent", allowed_actions: ["automox.*"], cap_calls: 2000, confirm_policy: "human_for_writes", approval_rules: [ { match: "automox.global_api_keys.delete", approver: "lead@example.com" }, { match: "automox.devices.delete", approver: "lead@example.com" }, { match: "automox.policies.delete", approver: "lead@example.com" } ] } ``` Illustrative. Scoped to Automox only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person. Cost ## What Automox costs on actionlake. Every Automox action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Automox refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. - 1 upstream call per action all 129 Automox actions - 129 actions page each page of a long list is one call - 75 reads can be cached a cache hit costs nothing - 100,000 calls a month, free paid plans from US$49 a month for 250,000 [See pricing](https://actionlake.com/pricing) Action index ## Every Automox action. 129 actions by area: the id your agent calls, what it does, and its effect. **Saved searches 11** - `automox.saved_searches.cached_results` List Search Cached Results read - `automox.saved_searches.create` Create a Saved Search write - `automox.saved_searches.delete` Delete Saved Search destructive - `automox.saved_searches.get` List a Saved Search read - `automox.saved_searches.list` List Saved Searches read - `automox.saved_searches.list_for_device` List Saved Searches Containing Device read - `automox.saved_searches.list_for_device_paged` List Saved Searches for a Given Device read - `automox.saved_searches.refresh` Refresh Cached Search Results write - `automox.saved_searches.result_ids` List Saved Search Results read - `automox.saved_searches.run` Execute Saved Search read - `automox.saved_searches.update` Update Saved Search write **Remote control 10** - `automox.remote_control.attended_access_bulk_set` Set Attended Access Setting for Devices in Bulk write - `automox.remote_control.attended_access_get` List Attended Access Setting for Device read - `automox.remote_control.attended_access_set` Set Attended Access Setting for Single Device write - `automox.remote_control.bulk_software` Bulk Install or Uninstall Splashtop RMM client write - `automox.remote_control.device_status` List Device Installation and Registration Status read - `automox.remote_control.force_disconnect` Force Disconnect All Active Splashtop Sessions on a Device destructive - `automox.remote_control.initiate_connection` Initiate Splashtop Remote Control Connection write - `automox.remote_control.install` Install Splashtop RMM Client write - `automox.remote_control.session_status` List Device Session Status read - `automox.remote_control.uninstall` Uninstall and Delete Splashtop Device Registration destructive **Policy windows 9** - `automox.policy_windows.create` Create a New Scheduled Window write - `automox.policy_windows.delete` Delete a Scheduled Window destructive - `automox.policy_windows.device_schedule` List the Next Scheduled Window Dates by Device. read - `automox.policy_windows.get` List a Scheduled Window read - `automox.policy_windows.group_exclusion_status` Check Scheduled Window Status for Server Groups read - `automox.policy_windows.group_schedule` List Next Scheduled Window Dates by Group read - `automox.policy_windows.is_active` Check Whether a Scheduled Window is Currently Active read - `automox.policy_windows.search` List Scheduled Windows (POST) read - `automox.policy_windows.update` Update a Scheduled Window write **Policies 8** - `automox.policies.clone` Clone a Patch Policy write - `automox.policies.create` Create a New Policy write - `automox.policies.delete` Delete a Policy destructive - `automox.policies.device_filters_preview` List Device Filter Preview read - `automox.policies.execute` Schedule Policy for Immediate Remediation write - `automox.policies.get` List Policy Details read - `automox.policies.list` List Policies read - `automox.policies.update` Update a Policy write **Webhooks 7** - `automox.webhooks.create` Create Webhook write - `automox.webhooks.delete` Delete Webhook destructive - `automox.webhooks.get` Get Webhook read - `automox.webhooks.list` List Webhooks read - `automox.webhooks.rotate_secret` Rotate Webhook Secret destructive - `automox.webhooks.test` Test Webhook Delivery write - `automox.webhooks.update` Update Webhook write **User API keys 6** - `automox.user_api_keys.create` Create an Organization API Key for a User write - `automox.user_api_keys.decrypt` Decrypt Organization API Key read - `automox.user_api_keys.delete` Delete an Organization API Key by ID destructive - `automox.user_api_keys.get` List Specific Organization API Key by User ID read - `automox.user_api_keys.list` List Organization API Keys for a User read - `automox.user_api_keys.update` Update a specific Organization API Key by ID write **Devices 5** - `automox.devices.batch_update` Update Multiple Devices write - `automox.devices.delete` Delete a Device destructive - `automox.devices.get` List Device Details read - `automox.devices.list` List Devices read - `automox.devices.update` Update a Device write **Global API keys 5** - `automox.global_api_keys.create` Create Global API Key write - `automox.global_api_keys.decrypt` Decrypt Global API Key Value read - `automox.global_api_keys.delete` Delete Global API destructive - `automox.global_api_keys.list` List Global API Keys read - `automox.global_api_keys.update` Update Global API Key Metadata write **Remediation action sets 5** - `automox.remediation_action_sets.bulk_delete` Bulk Delete Action Sets destructive - `automox.remediation_action_sets.delete` Delete an Action Set destructive - `automox.remediation_action_sets.get` List an Action Set read - `automox.remediation_action_sets.list` List Action Sets read - `automox.remediation_action_sets.run_actions` Execute Remediations in an Action Set write **Server groups 5** - `automox.server_groups.create` Create New Server Group write - `automox.server_groups.delete` Delete Existing Server Group destructive - `automox.server_groups.get` List Group Details read - `automox.server_groups.list` List All Groups read - `automox.server_groups.update` Update Existing Server Group write **Users 4** - `automox.users.get` List Organization User by ID read - `automox.users.list` List Organization Users (Legacy) read - `automox.users.patch` Partially Update a User write - `automox.users.update` Fully Update a User write **Cloud worklets 3** - `automox.cloud_worklets.get` Get worklet read - `automox.cloud_worklets.list` List worklets read - `automox.cloud_worklets.trigger` Trigger worklet execution write **Data extracts 3** - `automox.data_extracts.create` Create a New Data Extract write - `automox.data_extracts.get` List Data Extract by ID read - `automox.data_extracts.list` List Data Extracts read **Device search metadata 3** - `automox.device_search_metadata.device_fields` List Device Fields read - `automox.device_search_metadata.fields` List Searchable Fields read - `automox.device_search_metadata.scopes` List Search Scopes read **Policy history 3** - `automox.policy_history.get` List Policy Information read - `automox.policy_history.list` List Policy Execution Counts read - `automox.policy_history.runs` List Policy Execution History read **Policy runs 3** - `automox.policy_runs.count` List Policy Run Count read - `automox.policy_runs.list` List All Policy Executions read - `automox.policy_runs.list_by_policy` List All Policy Executions By Policy UUID read **Zones 3** - `automox.zones.create` Create a New Organization write - `automox.zones.get` List Organization Details read - `automox.zones.list` List Organizations for an Account read **Account users 2** - `automox.account_users.delete` Delete Account User destructive - `automox.account_users.get` List Account User Information read **Approvals 2** - `automox.approvals.list` List Manual Approvals read - `automox.approvals.update` Update Manual Approval write **Cloud worklet executions 2** - `automox.cloud_worklet_executions.list` List executions across all worklets read - `automox.cloud_worklet_executions.list_by_worklet` List executions read **Device commands 2** - `automox.device_commands.create` Issue a Command to a Device write - `automox.device_commands.list` List Device Command Queue read **Device search 2** - `automox.device_search.search` List Search Device Details read - `automox.device_search.typeahead` List Values for Typeahead Search read **Reports 2** - `automox.reports.needs_attention` List Devices that Need Attention read - `automox.reports.prepatch` List Pre-Patch Report read **Worklet catalog 2** - `automox.worklet_catalog.get` List Worklet Details by ID read - `automox.worklet_catalog.search` Search Worklet Catalog read **Account invitations 1** - `automox.account_invitations.create` Create Account Invitation write **Account roles 1** - `automox.account_roles.list` List Account RBAC Roles read **Account user zones 1** - `automox.account_user_zones.list` List Organizations for User read **Accounts 1** - `automox.accounts.get` List Account Details read **Audit event types 1** - `automox.audit_event_types.list` List Audit Event Types read **Audit events 1** - `automox.audit_events.list` List Audit Events read **Cloud worklet types 1** - `automox.cloud_worklet_types.list` List worklet types read **Device inventory 1** - `automox.device_inventory.list` List Device Inventory read **Device inventory categories 1** - `automox.device_inventory_categories.list` List Device Inventory Categories read **Device packages 1** - `automox.device_packages.list` List Device Packages read **Events 1** - `automox.events.list` List All Events read **Organization API keys 1** - `automox.organization_api_keys.list` List Organization API Keys read **Organization packages 1** - `automox.organization_packages.list` List Organization Packages read **Organizations 1** - `automox.organizations.list` List Organizations read **Policy run devices 1** - `automox.policy_run_devices.list` List Policy Execution Details read **Policy stats 1** - `automox.policy_stats.list` List Policy Compliance Statistics read **Remediation issues 1** - `automox.remediation_issues.list` List Issues for an Action Set read **Remediation solutions 1** - `automox.remediation_solutions.list` List Solutions in an Action Set read **Remediation upload formats 1** - `automox.remediation_upload_formats.list` List CSV Formats for Uploading Remediations read **Webhook deliveries 1** - `automox.webhook_deliveries.list` List Delivery Logs read **Webhook event types 1** - `automox.webhook_event_types.list` List Event Types read **Zone users 1** - `automox.zone_users.list` List Organization Users read Questions ## The Automox MCP server, answered. **Is there an Automox MCP server for Claude?** Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 129 Automox actions across saved searches, remote control, policy windows and policies, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Automox. **What do I need to connect Automox?** Automox API key. The free call account { op: "connections.requirements", service: "automox" } lists exactly what to paste. **Can an AI agent delete or change things in Automox?** Only if its key allows it, and only with an explicit confirmation. 14 Automox actions are destructive, including delete Global API, delete a Device and delete a Policy. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it. **Will an AI agent use up my Automox API limit?** actionlake paces every call to the limits in the Automox service file: 60 calls a minute per connection. Repeated reads are answered from cache (75 Automox actions can be), which never reaches Automox. **What does an Automox action cost?** One upstream call, the only unit actionlake bills. A list that pages bills one call per page (129 Automox actions page). Cache hits, searches, dry runs and calls Automox refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000. **Which Automox API does it cover?** The Automox Console API (console.automox.com/api) at console.automox.com. It is built from Automox's documentation as read on 23 October 2026. 129 actions in 46 areas, each one in the signed service file (version 1.0.0). **Does actionlake keep my Automox data, and where?** actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Automox credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models. **Which AI clients can use it?** Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names. ## More connectors like Automox Shares the most action names with - [Tailscale 17](https://actionlake.com/connectors/tailscale) - [Liongard 16](https://actionlake.com/connectors/liongard) - [Imperva Cloud Application Security 14](https://actionlake.com/connectors/imperva-cloud-application-security) - [Tactical RMM 12](https://actionlake.com/connectors/tactical-rmm) - [Wazuh 9](https://actionlake.com/connectors/wazuh) - [Sublime Security 8](https://actionlake.com/connectors/sublime-security) Joins with, on shared entities - [Microsoft 365 Users 3](https://actionlake.com/connectors/microsoft-365-users) - [Cloudflare 3](https://actionlake.com/connectors/cloudflare) - [JumpCloud 3](https://actionlake.com/connectors/jumpcloud) - [VMware Carbon Black Cloud 3](https://actionlake.com/connectors/vmware-carbon-black-cloud) - [Google Workspace Directory 3](https://actionlake.com/connectors/google-workspace-directory) - [Slack 2](https://actionlake.com/connectors/slack) Browse - [All MSP & PSA connectors](https://actionlake.com/connectors/category/msp-and-psa) - [All connectors](https://actionlake.com/connectors) - [How actionlake compares](https://actionlake.com/compare) actionlake is independent. It is not made or endorsed by Automox; the name is the vendor's own. Counts are from the Automox service file, version 1.0.0. ## Give your agent Automox today. [Connect Automox free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing) Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free. --- Source: https://actionlake.com/connectors/automox More: https://actionlake.com/llms.txt