Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Official MCP server for Automox. Manage devices, patches, and policies in natural language.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID, AUTOMOX_ORG_ID비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
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/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"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
AUTOMOX_ORG_ID env이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 도메인 automox.com 기준으로 확인되었어요(레지스트리가 도메인 소유를 확인해요)
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: AUTOMOX_API_KEY, AUTOMOX_ACCOUNT_UUID
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(2.2.9)은 4개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Python MCP
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
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.
Local-only Python MCP server for the Files.com API.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요