- Home
- MCP servers
- Automox
Automox
- python
1
GitHub Stars
python
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"automoxcommunity-automox-mcp": {
"command": "uvx",
"args": [
"--env-file",
".env",
"automox-mcp"
],
"env": {
"AUTOMOX_ORG_ID": "YOUR_ORG_ID",
"AUTOMOX_API_KEY": "YOUR_API_KEY",
"AUTOMOX_ACCOUNT_UUID": "YOUR_ACCOUNT_UUID"
}
}
}
}The Automox MCP Server lets you access Automox management capabilities through AI assistants. It exposes focused workflows for common tasks like managing devices, policies, and user accounts, enabling interactive automation without building a full API wrapper. You can run it locally or over HTTP/SSE to integrate with your preferred MCP client.
How to use
You interact with the MCP server through an MCP client or AI assistant. Start by configuring your environment with your Automox credentials, then run the server and connect your client. Typical usage patterns include listing devices, checking policy health, applying policy changes, running immediate remediation, and reviewing audit trails. Your client can pass high-level intents like updating a policy, rebooting a device, or inviting a user, and the MCP server will guide you through the required steps and surface results.
How to install
Prerequisites you need before installing and running the MCP server are clearly defined so you can prepare your environment.
Running the MCP server locally
Configure your environment and start the MCP server using the recommended runtime. The server can be run directly with a local runtime and your API credentials loaded from a file.
Available tools
list_devices
Summarize device inventory and policy status across the organization, including unmanaged devices and filtered views by policy status or management state.
device_detail
Return curated device context including recent policy status, assignments, queued commands, and key facts. Use include_raw_details to fetch sanitized raw payloads when needed.
devices_needing_attention
Identify devices that require immediate action based on automated checks and policy status.
search_devices
Search devices by hostname, IP, tag, status, or missing patches severity to locate targets quickly.
device_health_metrics
Aggregate health metrics for devices, with options to limit sampling and control staleness in responses.
execute_device_command
Issue immediate commands to devices such as scan, patch_all, patch_specific, or reboot.
policy_health_overview
Provide a summary of recent policy activity across the organization.
policy_execution_timeline
Review recent executions for a policy to understand outcomes and timing.
policy_run_results
Fetch per-device results for a policy execution, including stdout, stderr, and exit codes.
policy_catalog
List policies with type and status summaries, with pagination and helpful metadata for navigation.
policy_detail
Retrieve policy configuration and recent history for a policy.
apply_policy_changes
Preview or submit structured policy create/update operations with normalization of helper fields and schedules.
patch_approvals_summary
Summarize pending patch approvals and their severity to guide decision-making.
decide_patch_approval
Approve or reject a patch approval request.
execute_policy_now
Execute a policy immediately for remediation across all devices or a specific device.
invite_user_to_account
Invite a user to the Automox account with optional zone assignments.
remove_user_from_account
Remove a user from the Automox account by UUID.
audit_trail_user_activity
Retrieve audit trail events performed by a specific user on a given date, with optional pagination and sanitized payloads.