Most MDMs bolt a chatbot onto a legacy console. DockMDM ships a native MCP server, so Claude, Codex, or any AI agent connects directly to your fleet: query devices, run jobs, and build Zebra MX configurations in plain language.
"Which scanners are below 20% battery?" The agent queries live telemetry and answers with real device data.
App installs, kiosk mode, lock, reboot, agent updates. The agent runs the same jobs the console does, and devices report results back.
Describe device behavior in a sentence. The agent generates the MX profile, validates it against the schema, and deploys it.
The AI acts with a credential you issue, scoped to your org. Authenticated, logged, revocable.
DockMDM speaks the Model Context Protocol, the open standard AI tools use to reach external systems. Point Claude, Claude Code, Codex, or your own MCP client at your DockMDM endpoint and your fleet shows up as tools the agent can call.
// WHAT AI DOES NOT DO HERE
The AI never acts on its own. It uses a credential you issue, does only what that admin account can do, and every request lands in the server log. Wipe and other destructive operations are explicit job types, never a side effect of something else.
Create an account, enroll a device, connect your MCP client. Free for up to 3 devices.
Start free →