Official MCP server for Automox. Manage devices, patches, and policies in natural language.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
Not yet automatically verified
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Documentation Overview
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.
[!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/mcpwith 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.
| Self-hosted (this repository) | Hosted (MCP Server 3.0) | |
|---|---|---|
| Install | You install and keep it updated (PyPI, uvx, the Claude Desktop extension, or via Claude's Connectors Directory) | Nothing to install, Automox runs it |
| Where it runs | Your machine | Automox's multi-tenant service |
| Auth | Your Automox API key | Your Automox API key (same model, for now) |
| Claude Desktop | Works today via the one-click extension, installable from GitHub Releases or Claude's Connectors Directory | Not yet, Claude Desktop's built-in custom connector requires OAuth, which the hosted service doesn't support yet |
| Other clients (Claude Code, Cursor, MCP Inspector, etc.) | Works via your local config | Works today over HTTP with a Bearer token header |
| Good fit if | You want to run your own infrastructure, or you use Claude Desktop today | You want zero maintenance and use a client that supports custom HTTP headers |
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:
| Value | Where to find it |
|---|---|
| API Key | Use an org-scoped key — zone Settings > Secrets & Keys > Add API Key (docs); see key types below |
| Account UUID | Settings > Secrets & Keys (shown on the page) |
| Org ID | The numeric ID in the URL when viewing your organization |
Automox has two API key types, and the difference matters here:
| Org-scoped key (recommended) | Global / account key | |
|---|---|---|
| Scope | One organization — the zone it was created in | Every org in the account; inherits the key owner's role per org |
| Created at | Zone Settings > Secrets & Keys | Account Global Access Management > Keys (Full Administrator) |
| Tool coverage | All tools (verified: works immediately on the search family) | Unreliable on the Advanced Device Search family — advanced_device_search, device_search_typeahead, saved-search create/read/update/delete, list_searches_for_device, get_device_assignments — observed returning 403 in most orgs even for full administrators, while working in others; the upstream authorization behavior is inconsistent and the mechanism is unconfirmed |
Symptom:
403on 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
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.
- Download the latest
automox-mcp-<version>.mcpbfrom the GitHub Releases page. - Open Claude Desktop → Settings → Extensions.
- Drag the
.mcpbfile into the Extensions window. - 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):
Cursor / any other MCP client — add to your MCP config:
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:
| Ask this | What happens |
|---|---|
| "Are we ready for Patch Tuesday?" | Checks pending patches, approvals, and policy schedules |
| "What is our compliance posture?" | Returns compliance rates, non-compliant devices, and health breakdown |
| "Give me the full profile for the Caldera server" | Combines device details, inventory, packages, and policy status |
| "What devices need attention?" | Surfaces devices flagged for immediate action |
| "Reboot the device 'Testing box'" | Searches for the device and issues a reboot command |
| "Create a patch policy for Firefox targeting the 'MCP testing' group" | Creates the policy with sensible defaults |
| "What did Mark Hansen do in Automox last week?" | Queries the audit trail across the date range |
| "Find all Windows devices not seen in 30 days" | Uses advanced device search with structured queries |
| "Show me vulnerability remediation status" | Lists action sets with issues, solutions, and progress |
| "Search the worklet catalog for USB security" | Browses community worklets with evaluation/remediation code |
For the full list of tools, parameters, and MCP resources, see the Tool Reference.
Tip: You can also ask the server itself — the
discover_capabilitiestool 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.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
13
Stargazers on the source repository.
Last commit
22d ago
Most recent push to the default branch.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Automox MCP Server
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/automox-mcp-server)HTML Embed
<a href="https://allmcps.com/mcp/automox-mcp-server"><img src="https://allmcps.com/api/badge/automox-mcp-server?style=directory" alt="Automox MCP Server on AllMCPs" /></a>