Skip to content

Summary

Automox's official MCP server for endpoint management — 130+ tools over devices, patches, policies, groups and audit data, self-hosted or on Automox's hosted endpoint.

Features

  • 130+ tools across devices, policies, patches, groups and webhooks
  • Read-only mode limited to 85 non-write tools
  • Automox-hosted endpoint over HTTP with a Bearer token — nothing to install
  • Policy Catalog templates for creating policies from best practice (hosted only)
  • Self-hosted option via PyPI, uvx or a one-click Claude Desktop .mcpb bundle

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Automox MCP Server" tools will be available.
{
  "mcpServers": {
    "automox-mcp": {
      "command": "uvx",
      "args": [
        "--env-file",
        "/path/to/.env",
        "automox-mcp"
      ],
      "env": {
        "AUTOMOX_API_KEY": "your-api-key",
        "AUTOMOX_ACCOUNT_UUID": "your-account-uuid",
        "AUTOMOX_ORG_ID": "your-org-id"
      }
    }
  }
}

Description

The official Model Context Protocol server for Automox, the cloud-native endpoint management platform. It puts the Automox Console and Webhooks APIs behind natural language, so an administrator can ask "are we ready for Patch Tuesday?" and get pending patches, outstanding approvals and tonight's policy schedule in one answer instead of five console tabs.

Coverage is unusually broad for a vendor MCP server: more than 130 tools spanning devices, policies, patches, groups, webhooks, worklets, vulnerability sync, maintenance windows, advanced device search and the audit trail. Operations that would expose secrets are excluded by design, and a read-only mode narrows the surface to 85 non-write tools for assistants that should never change anything.

Hosted or self-hosted

Version 3.0 added an Automox-run deployment at https://console.automox.com/api/mcp, reachable over HTTP with a Bearer token from any client that supports custom headers — Claude Code, Cursor, MCP Inspector — with nothing to install or update. The hosted service also adds Policy Catalog templates, letting the assistant search Automox's library of best-practice policies and create one from a template.

The self-hosted server remains fully supported and is the path for Claude Desktop today, since the hosted endpoint does not yet support the OAuth flow Claude Desktop's custom connectors require. It installs from PyPI as automox-mcp, runs under uvx, and ships a one-click .mcpb bundle; Automox is also listed in Claude's Connectors Directory.

Credentials

You need an Automox API key and Account UUID, plus an Org ID for org-scoped operations. Automox recommends an org-scoped key over a global account key: the advanced device search family has been observed returning 403 with global keys even for full administrators.

Related MCP Servers

MCP: AWS MCP Server

by Amazon Web Services

New

AWS's managed MCP server: call any AWS API, run sandboxed Python against your account, and load AWS agent skills on demand — under IAM, CloudWatch and CloudTrail.

Featured

Google's official MCP server for driving the gcloud CLI from natural language, with allowlist and denylist controls over which commands an agent may run.

Browse all MCP servers →