
Automox MCP Server
Operate Automox endpoint fleets from your coding agent—query devices, drive patches, and adjust policies without living in the admin console.
Overview
Automox MCP is a MCP server for the Operate phase that lets coding agents manage Automox devices, patches, and policies via the official stdio integration.
What is this MCP server?
- Official Automox MCP over stdio (PyPI package automox-mcp v2.2.1)
- Natural-language control of devices, patches, and organization policies
- Requires AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID, and typically AUTOMOX_ORG_ID
- stdio transport suited to Claude Code, Cursor, and local agent configs
- Open-source server on GitHub (AutomoxCommunity/automox-mcp)
- Server schema version 2.2.1 on PyPI package automox-mcp
- stdio transport with 3 documented environment variables (API key, account UUID, org ID)
Community signal: 6 GitHub stars.
What problem does it solve?
Patch status and policy changes usually mean context-switching out of your editor into Automox’s UI while agents cannot see your fleet.
Who is it for?
Indie operators or tiny IT leads who run Automox on real devices and want MCP-driven fleet checks from Claude Code or Cursor.
Skip if: Builders without an Automox subscription, or anyone who only needs generic OS hardening scripts unrelated to Automox.
What do I get? / Deliverables
Your agent can query and act on Automox org data in-thread so endpoint hygiene stays aligned with how you already work in the repo.
- Agent-callable Automox device and patch operations
- Policy inspection and updates driven from chat
- Repeatable stdio MCP config for local agents
Recommended MCP Servers
Journey fit
Endpoint patch and policy control is ongoing production operations after you ship, not a one-off build task. Device inventory, patching cadence, and org policies map directly to infrastructure hygiene and fleet maintenance.
How it compares
Live Automox API integration via MCP—not a static hardening skill or generic shell cheat sheet.
Common Questions / FAQ
Who is Automox MCP for?
Solo builders and small teams with an Automox account who want their coding agent to manage patches and policies alongside development work.
When should I use Automox MCP?
During Operate when you need device inventory, patch compliance, or policy updates without leaving your agent session.
How do I add Automox MCP to my agent?
Install the automox-mcp PyPI package, set AUTOMOX_API_KEY and AUTOMOX_ACCOUNT_UUID (plus AUTOMOX_ORG_ID when required), and register the stdio server in your MCP client.