July 29, 2026

Axle MCP Server: Operate Your Agents from Claude, Cursor, and ChatGPT

Axle Team

Originally sent to Axle customers on May 19, 2026.

We've launched the Axle MCP server, giving compliance teams a way to operate Rose, Baley, and Sam directly from MCP-aware tools like Claude, Cursor, and ChatGPT.

Analysts and engineers can pull live alert metrics, trigger reruns, and inspect investigation context without leaving the tools they already work in.

Newly available MCP tools

Pull real-time alert metrics across orgs, time windows, and alert groups
Predict the impact of a rerun before committing to it
Read investigation context, flags, and module outputs
List and inspect recipes, strategies, templates, and registered flags
Stream Copilot threads against any open alert or investigation
Load Axle resources (alerts, investigations, entities) by URL

Scoped access, same safety rails

The server is built on the latest MCP protocol with OAuth 2.1 authorization, so access is scoped per user and respects your existing Axle org permissions — admins control exactly which teammates can connect a client, and to which orgs.

Every tool exposed over MCP is governed by the same safety rails we built for the in-product Copilot: destructive operations require a structured plan card before they execute, and reprocessing actions surface a predicted-impact preview so analysts can review the change before approving. The same protections apply whether the agent is running inside Axle or driving the API from an external client.

No version skew

We extracted the customer-facing tool functions into a shared module — every new tool we ship to Copilot is automatically available over MCP, so there's no gap between what the in-product agent can do and what your own scripts and AI tools can do.

Full setup instructions are in the Axle MCP documentation. Want it enabled in your account? Book a walkthrough or reach out at sales@axleruns.com.

More from the blog