Automox MCP Server

Name: Automox MCP Server
Author: AutomoxCommunity

作者：AutomoxCommunity版本 2.2.9i★ –i在你的电脑上运行

注册名称com.automox/automox-mcp

安装

概览

作者提供的说明（英文原文）

Official MCP server for Automox. Manage devices, patches, and policies in natural language.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID, AUTOMOX_ORG_ID

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "automox": {
      "command": "uvx",
      "args": [
        "automox-mcp"
      ],
      "env": {
        "AUTOMOX_API_KEY": "your-value",
        "AUTOMOX_ACCOUNT_UUID": "your-value",
        "AUTOMOX_ORG_ID": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add automox --env AUTOMOX_API_KEY=your-value --env AUTOMOX_ACCOUNT_UUID=your-value --env AUTOMOX_ORG_ID=your-value -- uvx automox-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "automox": {
      "command": "uvx",
      "args": [
        "automox-mcp"
      ],
      "env": {
        "AUTOMOX_API_KEY": "your-value",
        "AUTOMOX_ACCOUNT_UUID": "your-value",
        "AUTOMOX_ORG_ID": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "automox": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "automox-mcp"
      ],
      "env": {
        "AUTOMOX_API_KEY": "your-value",
        "AUTOMOX_ACCOUNT_UUID": "your-value",
        "AUTOMOX_ORG_ID": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AUTOMOX_API_KEY 机密必填 env
Your Automox API key
AUTOMOX_ACCOUNT_UUID 必填 env
Account UUID from Automox Settings > Secrets & Keys
AUTOMOX_ORG_ID env
Numeric Automox organization ID. Recommended — required by most tools, optional for tools that don't need org context.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过域名 automox.com 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32655 个服务器的 0%
发布到注册中心的时间比此分类中其他 32655 个服务器的 19% 更新
基础检查结果等于或优于此分类中其他 32655 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Automox MCP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.2.9）于4个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, SuperCollider

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

SuperCollider

作者：Tok

Make sound with SuperCollider: synths, drums, chords, melodies and soundscapes over OSC.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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.

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.

	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: 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.

Download the latest automox-mcp- .mcpb from the GitHub Releases page.
Open Claude Desktop → Settings → Extensions.
Drag the .mcpb file 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):

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:

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](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.

Variable	Required	Default	Description
`AUTOMOX_API_KEY`	Yes	—	Automox API key (org-scoped recommended — see key types)
`AUTOMOX_ACCOUNT_UUID`	Yes	—	Account UUID from Secrets & Keys
`AUTOMOX_ORG_ID`	Recommended	—	Numeric organization ID (required by most tools)
`AUTOMOX_MCP_READ_ONLY`	No	`false`	Disable all write operations (85 of 133 tools remain)
`AUTOMOX_MCP_ALLOW_APPLY_REMEDIATION_ACTIONS`	No	`false`	Opt in to the `apply_remediation_actions` tool, which patches/runs worklets on endpoints immediately. Off by default even in write mode.
`AUTOMOX_MCP_ALLOW_SPLASHTOP_BULK_INSTALL_UNINSTALL`	No	`false`	Opt in to the `splashtop_bulk_install_uninstall` tool, which installs/uninstalls the Splashtop client across an entire server group in one call. Off by default even in write mode.
`AUTOMOX_MCP_ALLOW_DELETE_DEVICE`	No	`false`	Opt in to the `delete_device` tool, which permanently deletes a device record and its history (`DELETE /servers/{id}`). Irreversible and not reconstructable through the MCP. Off by default even in write mode.
`AUTOMOX_MCP_ALLOW_UPLOAD_POLICY_FILE`	No	`false`	Opt in to the `upload_policy_file` tool, which uploads a local installer file to a Required Software policy. Reads from the local filesystem, so it also requires `AUTOMOX_MCP_UPLOAD_ALLOWED_DIRS` and only works on the stdio (local) transport. Off by default even in write mode.
`AUTOMOX_MCP_UPLOAD_ALLOWED_DIRS`	No	—	Comma-separated absolute directories `upload_policy_file` may read installers from. Required for that tool to register; paths are canonicalized and must resolve inside an allowed dir.
`AUTOMOX_MCP_UPLOAD_MAX_BYTES`	No	`10737418240`	Max installer size for `upload_policy_file` (default 10 GB, Automox's ceiling).
`AUTOMOX_MCP_UPLOAD_TIMEOUT_SECONDS`	No	`3600`	Upload read/write timeout for `upload_policy_file` (large installers need more than the default request timeout).
`AUTOMOX_MCP_MODULES`	No	all	Comma-separated list of modules to load (see below)
`AUTOMOX_MCP_TOKEN_BUDGET`	No	`4000`	Max estimated tokens per response before truncation
`AUTOMOX_MCP_SANITIZE_RESPONSES`	No	`true`	Sanitize API data to mitigate prompt injection

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

只显示了开头部分；其余内容请在仓库中阅读

Automox MCP Server

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

SuperCollider

作者的 README

Automox MCP Server

Table of Contents

What's New in 3.0

Self-Hosted vs. Hosted

Quick Start

1. Get your Automox credentials

2. Create a .env file

3. Connect to your AI assistant

What Can I Ask?

Configuration

Environment Variables

2. Create a `.env` file