Automox released Automox MCP Server 3.0, which adds an Automox-hosted deployment of its Model Context Protocol (MCP) server.
Previously, the server ran locally. That restricted use to desktop clients, and each administrator had to install and update their own copy. Web-based assistants and hosted agent platforms, which cannot run a local process, could not connect.
With the hosted server, any MCP-capable client connects using the administrator's Automox API key, and Automox maintains the server. Access is governed by each user's existing Automox role and organization scope. The Automox MCP Server is now available directly in Claude.
"Capability was never the barrier. Automox MCP already covers the full published API surface. The barrier was that using it took a desktop client and a local install, so it stayed a tool for the most technical people on the team," said Jason Kikta, CTO at Automox. "Hosted MCP removes that. You bring the assistant you already use and your Automox API key. Your role and org scope govern what it can do, the same as they always have. Nothing to install. Nothing to maintain. Nothing out of date."
The server provides 133 tools covering the published Automox Console and Webhooks APIs, with secret-exposing operations excluded by design. An operator can ask "Are we ready for Patch Tuesday?" and receive pending patches by severity, the approval queue, and each policy's schedule in one response. A read-only mode limits the assistant to 85 non-write tools.
Customers choose their own AI assistant and model. Conversations stay between the customer and their chosen AI provider, and Automox receives only the API calls the assistant makes.
Automox MCP Server 3.0 is available now to Automox customers. The local server remains available through PyPI and the MCP Registry. The Automox console remains the primary interface for the platform, with MCP providing a second path for teams connecting their own AI assistants, tools, or agents.
The Latest
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...
Virtual Private Networks became a cornerstone of enterprise security at a time when corporate infrastructure looked very different from today ... For years, this model worked well. But the architecture behind VPNs assumed a centralized corporate environment—one where the network itself was the hub of activity. In a cloud — first world, that assumption no longer holds ...
Website outages get resolved just as fast in August as they do in November. I went looking for the opposite: the summer slowdown everyone assumes is there once the people who fix things are away. It isn't in the data we collected, covering 1.8 million confirmed outages across tens of thousands of websites ...
This year, many of the cloud infrastructure contracts signed in the early days of the AI boom will come up for renewal. As the year goes on, I anticipate we'll see a significant amount of cloud vendor swapouts and multi-cloud adoption, and the reason isn't just GPU depreciation. It's because they're tired of their current cloud providers ...
There's a moment the many observability teams have experienced days into bringing a new service into production: you realize that the vendor's claims of "intelligent" behavior included a large serving of hype. Their dashboards look nice until they don't, the failure modes are a black box, and no one on the team can confidently explain why the system did what it did at 2 am. Agentic AI is about to force every Ops team to relive that moment at web-scale until they start treating these systems as the dependencies they actually are ...