){kind=logo}
An AI assistant connected to your endpoint-management platform can request changes across your entire fleet. On a shared service, that power comes with one hard rule: every request has to stay inside the access your credentials actually allow.
That's the problem Automox MCP Server 3.0 is built to solve. It adds a hosted deployment of the Automox Model Context Protocol (MCP) server, an open standard for connecting AI applications to external systems. Automox runs it on infrastructure shared across multiple customers, so you're not the one maintaining a local server.
Kannan Thayumanavar worked on hardening the hosted service before it reached general availability (GA), and kept hardening it after. His focus: testing proposed fixes before they became instructions for the rest of the team.
A proposed fix with its own bug
A security audit produced a list of findings and proposed fixes. Kannan's first instinct was to treat it like a checklist and work straight through.
He didn't.
"Instead I tested every single fix on a throwaway copy of the code before writing it up," Kannan says. "That caught real mistakes, including a proposed fix that had its own bug in it. The team could then just execute down the list with confidence, and the GA blockers got closed fast."
Only fixes that survived that test run made it into the remediation guide — and before the guide went to the team, Kannan ran a second full verification pass. It caught mistakes the first pass had missed.
Regression tests for customer isolation
Kannan also added automated tests for the customer-isolation behavior the fixes addressed — tests that now check whether updates to the underlying open-source code break those covered behaviors before anything ships.
The stakes are high by design.
"Every customer who uses it hands us their API key," Kannan says. "That key can see and control their whole device fleet." "A tenant-isolation bug here is a serious one, where one customer touches another customer's infrastructure. Fixing that, and building measures to identify and prevent those, is what I'm most proud of."
Connecting to the hosted service
The setup documentation includes connection settings for Claude Code, Cursor, and other clients that support streamable HTTP with custom headers. You authenticate with an Automox API key sent as a bearer token.
With a compatible client, you can ask which endpoints are missing patches or request endpoint-management actions. The API key's scope and inherited permissions govern what the assistant can do.
Sources
Automox MCP Server repository – Hosted and local deployment options, compatible clients, API key authentication, and setup instructions
Using Global API Keys – Organization and account scope, and inherited user permissions
Model Context Protocol – The open standard's own description of what MCP connects
Frequently asked questions
It's an MCP server that connects an AI assistant to the Automox platform. You can ask about your endpoints and request actions in plain language. Version 3.0 adds a deployment hosted by Automox alongside the local server.
Claude Code, Cursor, and any client that supports streamable HTTP with custom headers. Claude Desktop's built-in custom connector requires OAuth, which the hosted service doesn't yet support. Claude Desktop users can install the local Automox MCP extension instead.
No. The local server remains available. The hosted service is an added option for compatible clients when you want Automox to run and update the server.
The Automox API key used for the connection. An organization key carries the permissions of the user who created it in that organization. A global key inherits the key owner's permissions in whichever organization the request targets.
An organization-scoped key. Global account keys are unreliable on the Advanced Device Search tool family and can return 403 errors.
)
)
)
)