Automox MCP Server 3.0 | Customer Setup Guide
Getting Started
Automox MCP Server 3.0 is centrally hosted. There is nothing to download, install, or keep updated. You connect your AI assistant directly to Automox's hosted endpoint using your existing API key.
This guide covers connecting for the first time and migrating from a self-hosted 2.x installation.
What you need
|
Item |
Where to get it |
|---|---|
|
The endpoint URL |
|
|
An org-scoped Automox API key |
Automox Console→ zone Settings→ Secrets & Keys→ Add API Key. Use an org-scoped key. Global and account keys can return 403 errors on some search features. |
|
An MCP client that supports HTTP with a custom header |
Claude Code, MCP Inspector, Cursor, and most MCP-capable clients. Claude Desktop's built-in connector does not currently support this, see Troubleshooting below. |
Authentication is your API key sent as a Bearer token, included on every request:
Authorization: Bearer YOUR_AUTOMOX_API_KEY
Your permissions in Automox apply exactly as they do in the console and API. The MCP acts as you.
Setting up for the first time
If you've never used the Automox MCP server, this is your whole setup. There's no package to install.
- Create an org-scoped API key in the Automox Console (organization Settings → Secrets & Keys → Add API Key).
- Connect your client to the hosted endpoint using one of the options below.
- Start asking questions.
Migrating from a Self-Hosted 2.x Installation
If you're already running the Automox MCP server locally (through PyPI, uvx, or the Claude Desktop extension), migrating is two separate steps: remove the local server, then connect to the hosted one. There's no in-place upgrade and nothing to convert, no configuration file to move and no data to port.
Step 1: Remove the local 2.x server
Claude Code:
claude mcp remove automox
Use whatever name you registered the server under. “automox” is the common default.
Claude Desktop / the MCPB extension: Open Claude Desktop and go to Settings → Extensions. Find Automox and either toggle it off (you can turn it back on later) or choose Uninstall to remove it completely. Restart Claude Desktop afterward so the old tools no longer appear.
If Claude Desktop is where you use Automox, keep the extension installed and only remove it when you're moving to a client that can connect to the hosted server, such as Claude Code or Cursor.
Step 2: Connect to hosted 3.0 MCP
This is the same process as a first-time setup. Use the instructions below for your client.
Connecting Your Client
Claude Code
claude mcp add --transport http automox \
https://console.automox.com/api/mcp \
--header "Authorization: Bearer YOUR_AUTOMOX_API_KEY"Open a new session and ask something like, "What’s our compliance posture?"
MCP Inspector (for evaluation or debugging)
npx @modelcontextprotocol/inspector
In the UI:
- Transport Type = Streamable HTTP,
- URL = https://console.automox.com/api/mcp,
- Authentication, Bearer Token = your API key (paste the raw key).
- Click Connect, then Tools → List Tools.
Other MCP clients
Any client that supports streamable HTTP MCP servers with custom headers will work. Configure:
URL: https://console.automox.com/api/mcp
Header: Authorization: Bearer YOUR_AUTOMOX_API_KEYWhat to Expect
- The same broad tool coverage you already know: devices, policies, patching, groups, reports, webhooks, vulnerability sync, and more. You don't need to know tool names, just describe what you want (for example, “find Windows devices not seen in 30 days”).
- New in 3.0: Automox's best-practice policy template library. See below.
- Confirmation before changes. Read operations run freely. Anything that modifies your environment is flagged so your AI client asks you first.
- The highest-risk operations, like bulk remediation execution and device deletion, aren't available at all on the hosted service. They're off by design.
- No stored credentials. Your API key travels with each request and is never persisted by Automox.
Troubleshooting
|
Symptom |
Cause / fix |
|---|---|
|
Adding the hosted server fails in Claude Desktop's "custom connector" screen |
Claude Desktop's built-in custom connector only supports signing in with OAuth. The hosted service doesn't have OAuth yet, it only accepts an API key, so pasting the hosted URL in there will fail. This is a different thing from the Automox MCP desktop extension: install that instead (one-click .mcpb install, also in Claude's Connectors Directory). It runs the server locally on your machine and connects using the same API key you already have, so you still get full functionality in Claude Desktop, just through the extension rather than the custom connector screen. |
|
401 Unauthorized |
The |
|
“OAuth Authentication Failed” or an error about invalid JSON |
Your client fell back to OAuth discovery after a 401. Fix the Bearer header rather than trying a custom header name. |
|
403 Forbidden on some tools |
Check your key's scope. Use an org-scoped key. Some user-management features require admin scopes. |
|
Answers look off |
AI assistants can make mistakes. Verify important results in the Automox Console before acting on them. |
Frequently Asked Questions
Does my self-hosted 2.x server stop working?
No. Your existing self-hosted installation continues to work, there's no change to it or to how you get it. The hosted service is simply a new option if you'd like to use it, with no requirement to switch at this time.
Do I lose any capabilities by moving to the hosted service?
No. The hosted service runs the same tools you already have access to today.
Will I need to switch to SSO?
Not yet. The hosted service uses the same API key model you use today. SSO and per-user authentication are planned for a future release, and we'll provide clear migration guidance when that happens.
I use Claude Desktop. What should I do?
Keep using the Automox MCP desktop extension for now. Claude Desktop's native connector option requires OAuth, which the hosted service doesn't support yet.
Need help? Submit a Support request.
