Connection, supported tools, and live gateway status
This section brings together the hosted connection guide, current MCP coverage, and the live status signals teams usually want before they connect production clients.
What this page covers
Use it as the operational reference for setup, gateway health, supported tool families, loaded controllers, and the current hosted request envelope.
Connection guide
The hosted setup page generates the client-specific configuration for Claude, Codex, Cursor, VS Code, and other supported MCP-capable clients.
Start there if you need to sign in to fetch a bearer token, paste an existing token, or copy the exact configuration snippet for your MCP client.
Live controller inventory
These controller groups are loaded from the running Smplify MCP service so the reference page stays aligned with the current hosted tool surface.
Current hosted coverage — a curated, high-signal set (~193 tools) is advertised by default across Apple, Windows, and Linux; the full generated surface is available on demand.
Supported tool families
Smplify MCP turns the Smplify Platform admin surface into MCP tools that clients can call through one hosted endpoint.
Fleet operations
Inspect device state, check-in posture, enrollment status, and tag or policy coverage across Apple, Windows, and Linux before deciding whether any action is needed.
Cross-platform policies and compliance
Author cross-platform policy bundles and per-platform profiles/payloads (Apple, Windows, Linux), review policy gaps, and compare current state before a human approves any change.
Apps and software updates
Combine app inventory, device targeting, and policy context for software rollout — including Windows MSI deployment and OS software-update policies (rolling), status, and version catalogs.
Identity, enrollment, directory, and admin workflows
Review enrollment (Automated Device Enrollment and account-driven ADDE/ADUE), Directory integrations (Microsoft Entra, Google, LDAP) with sync and lookup, users, roles, and admin surfaces through the same MCP connection.
Hosted request envelope
The shared gateway applies request controls per bearer token so one client or agent cannot overwhelm the hosted service.
- Current hosted target: 60 requests per bearer token across a rolling 60-second window.
- Parallel agents using the same bearer token share the same request budget.
- Sequential review-first workflows are the best fit for stable day-to-day use.