Automox MCP server

What the model can do

Automox endpoint patching: devices with OS, agent, connection, compliance and pending patches, a device's missing patches with severity and CVEs, policies and their compliance counts, devices needing attention, the event log, manual patch approvals and device groups. Can scan a device, reboot it, install named patches or all updates, run a policy on one device, approve or reject a patch, and move a device to another group or mark it an exception, each only when asked.

Reads

• automox_devicesAutomox devices: name, OS and version, agent version, group, connected, compliant, needs reboot or attention, pending patch count, exception, tags…
• automox_device_patchesSoftware and patches on one Automox device: name, version, severity, CVEs, whether installed, ignored or deferred, and whether a reboot is needed.
• automox_policiesAutomox policies with their compliance counts: id, name, type (patch, required software, worklet), and how many devices are compliant…
• automox_needs_attentionAutomox devices that need attention: non-compliant counts by severity (critical, high, medium, low) and the devices…
• automox_eventsThe Automox event log between two days: event name (e.g. system.patch.applied, system.patch.failed, system.add), device, policy and time.
• automox_approvalsAutomox patches waiting for (or given) a manual approval decision: approval id, software and version, policy, status (pending, approved…
• automox_groupsAutomox device groups: id, name, parent group, device count and the policy ids applied to it.

Acts, when you ask

These change something in Automox. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• automox_scan_deviceTell an Automox device to scan now (GetOS): it refreshes its inventory and its list of missing patches.
• automox_reboot_deviceForce an Automox device to reboot now.
• automox_install_patchesInstall the named patches on an Automox device now (e.g. KB5031356), outside its policy's schedule.
• automox_install_all_updatesInstall every available update on an Automox device now.
• automox_run_policyRun an Automox policy now on one device (remediate it): patches it per the policy or runs the policy's worklet…
• automox_decide_approvalApprove or reject an Automox patch waiting for manual approval.
• automox_update_deviceChange an Automox device: move it to another group (which changes the policies that patch it), mark it an exception (left out of reports…

Connect it

First connect Automox on Dashboard → Connections, then add Memtro to your client once. The Automox tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Automox connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which devices are missing critical patches?
• › Which machines need a reboot?
• › How compliant is the Windows workstations policy?
• › Which patches are waiting for approval?
• › Scan the finance laptop FIN-LT-07 now

Questions

Is this an official Automox MCP server?

No. It is Memtro's MCP server with Memtro's Automox connector behind it: the connector reads Automox through its API with the credentials you connect on Dashboard → Connections, and Automox publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Automox?

Only when you ask, and only what it has been granted: scan a device now (refreshes its inventory and patch list); reboot a device now (interrupts whoever is using it); install named patches on a device now; install all available updates on a device now (ignores policy filters); run a policy now on one device; approve or reject a patch waiting for manual approval; move a device to another group, rename it, or mark it an exception. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

• GitHub MCP server
• AWS CloudWatch MCP server
• Sentry MCP server
• ServiceNow MCP server
• Okta MCP server
• Twilio MCP server