Automox MCP Server

Automox MCP Server

The official MCP server for Automox. Talk to your Automox console using natural language — this MCP server connects AI assistants like Claude to your Automox environment so you can manage devices, check compliance, run policies, and more, just by asking.

You:   "Are we ready for Patch Tuesday?"

Claude: Here's your readiness summary — 3 devices need patches, 2 approvals are pending, and your patch policies run tonight at 2 AM...

[!IMPORTANT]

For bug reports or feature requests, use help.automox.com or your typical escalation paths.

[!CAUTION]

AI assistants can make mistakes. Responses produced by the MCP server may be incorrect or incomplete. If you see this happening consistently, please let us know.

Table of Contents

• What's New in 3.0
• Self-Hosted vs. Hosted
• Quick Start
• What Can I Ask?
• Configuration
• Security
• Privacy Policy
• Alternative Installation
• Updating
• Migrating to the Hosted Server
• Troubleshooting
• Frequently Asked Questions
• Development
• Versioning
• License
• Support

What's New in 3.0

Automox MCP Server 3.0 adds a centrally hosted option to replace the legacy self-hosted solution. The hosted server supports all the functionality you're already using, plus one new capability.

• Hosted server: Automox now runs and maintains a version of this same server for you. Nothing to install, connect your AI client to https://console.automox.com/api/mcp with your existing API key. See Self-Hosted vs. Hosted below.
• Policy Catalog templates (hosted only): The hosted service can search Automox's library of best-practice policy templates and create a policy directly from one, so you have a starting point without building a policy from scratch. This is separate from asking about the policies already deployed in your org, this is Automox's own recommended template library.
• No capability loss: The hosted service exposes the same tool coverage you already have through this repository.
• No forced migration: This self-hosted server and the Claude Desktop extension keep working exactly as they do today. Moving to the hosted service is currently optional (but recommended), see Migrating to the Hosted Server.
• Auth is unchanged for now: Both versions use the same Automox API key. SSO is planned for a future release.

Self-Hosted vs. Hosted

Both run the same open-source server code. The difference is who installs and runs it, and one capability that's currently hosted-only.

For self-hosted setup, see Quick Start below. For the hosted server, see Migrating to the Hosted Server, which also covers connecting fresh with no prior install.

Quick Start

1. Get your Automox credentials

You need three values from the Automox Console:

Automox has two API key types, and the difference matters here:

Symptom: 403 on the search tools while reads work everywhere else usually means the key, not your permissions — switch to an org-scoped key for the target org. API Key and Account UUID are always required. Org ID is recommended but optional — some tools that don't require org context will work without it.

2. Create a .env file

AUTOMOX_API_KEY=your-api-key

AUTOMOX_ACCOUNT_UUID=your-account-uuid AUTOMOX_ORG_ID=your-org-id

3. Connect to your AI assistant

Claude Desktop (recommended) — one-click MCPB install:

New: Automox MCP is now also listed directly in Claude's Connectors Directory. Open Claude Desktop, go to Settings > Connectors, and search "Automox" to connect without leaving the app. The manual steps below still work too, nothing about them has changed.

1. Download the latest automox-mcp- .mcpb from the GitHub Releases page.
2. Open Claude Desktop → Settings → Extensions.
3. Drag the .mcpb file into the Extensions window.
4. Paste your API key, Account UUID, and (optionally) Org ID into the prompts.

No .env file, no terminal — credentials are stored in Claude Desktop's secure config. The bundle pulls the matching automox-mcp release from PyPI on first run.

Claude Code (CLI):

claude mcp add automox-mcp uvx -- --env-file /path/to/.env automox-mcp

Cursor / any other MCP client — add to your MCP config:

{

"mcpServers": { "automox-mcp": { "command": "uvx", "args": ["--env-file", "/path/to/.env", "automox-mcp"] } } }

That's it. Start asking questions.

What Can I Ask?

The server exposes 130+ tools across devices, policies, patches, groups, webhooks, worklets, vulnerability sync, maintenance windows, and more. You don't need to know the tool names — just describe what you want:

For the full list of tools, parameters, and MCP resources, see the [Tool Reference](docs/tool-reference.md).

Tip: You can also ask the server itself — the discover_capabilities tool returns all available tools organized by domain.

Configuration

Environment Variables

Applies only to self-hosted 2.x servers. Not applicable to the hosted 3.0+ server.

| AUTOMOX_MCP_TOOL_PREFIX | No | — | Prefix all tool names (e.g., `autom