Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Official MCP server for Automox. Manage devices, patches, and policies in natural language.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID, AUTOMOX_ORG_IDLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add automox --env AUTOMOX_API_KEY=your-value --env AUTOMOX_ACCOUNT_UUID=your-value --env AUTOMOX_ORG_ID=your-value -- uvx automox-mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"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"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
AUTOMOX_ORG_ID envEsta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con el dominio automox.com (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (2.2.9) llegó al registro hace 4 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Python (uv) en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, FactLot
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.
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.
https://console.automox.com/api/mcp with your existing API key. See Self-Hosted vs. Hosted below.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.
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.
.env fileAUTOMOX_API_KEY=your-api-key
AUTOMOX_ACCOUNT_UUID=your-account-uuid AUTOMOX_ORG_ID=your-org-id
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.
automox-mcp- .mcpb from the GitHub Releases page..mcpb file into the Extensions window.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.
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_capabilitiestool returns all available tools organized by domain.
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
Solo se muestra el principio; lee el resto en el repo