What Smplify MCP is and how it works
Smplify MCP is the hosted Model Context Protocol gateway for the Smplify Platform. It gives MCP-capable clients a single endpoint they can use with your Smplify bearer token to inspect fleet state, answer operational questions, and carry out approved admin workflows.
What is MCP?
MCP, or Model Context Protocol, is an open standard for connecting AI applications to external systems like tools, data, and workflows. If you want the broader background first, read the official MCP introduction.
Why teams use Smplify MCP
Model Context Protocol gives AI clients a standard way to discover tools and call them safely. For Smplify, that means teams can connect once and let an MCP-capable client translate natural-language requests into live Smplify operations using the permissions already embedded in their own bearer token.
Instead of hand-writing API calls or building a custom gateway for each client, operators get one hosted MCP endpoint, one connection flow, and one shared set of docs for connection, reference, and security guidance.
What Smplify MCP can enable
- Review devices, policies, apps, users, and enrollment posture before a change is made.
- Prepare rollout plans, remediation candidates, and admin summaries in natural language.
- Support approved actions through the hosted gateway when a trusted operator explicitly confirms them.
- Make the same Smplify workflows available across multiple MCP-capable clients without rebuilding integrations for each one.
MCP provides the standard connection layer. Smplify MCP adds the hosted endpoint, bearer-token boundary, and operational guidance around it.
How the hosted flow works
The current implementation keeps the bearer-token model that the Smplify Platform already uses while making it easier to connect that auth model to modern AI clients.
1. Connect the client
Users open the connection guide, sign in directly to Smplify from the browser or paste an existing bearer token, and generate the correct client configuration locally.
2. Call the hosted MCP endpoint
The client sends MCP requests to /mcp using bearer-based authentication over Streamable HTTP.
3. Execute with tenant-scoped permissions
The gateway validates the request, applies hosted controls, and then forwards Smplify tool calls using the caller’s own bearer token.
Where to go next
- Go to Reference for supported tools, live controller coverage, uptime, and gateway status.
- Go to Connection Guide when you are ready to install Smplify MCP in a supported client.
- Go to Security if your team wants to review hosted controls, control boundaries, and customer best practices before rollout.