Blog Post

Product news & info
3 MIN READ

[Product Update] The Future of Endpoint Management is Conversational

JordanOC's avatar
JordanOC
Google Team
5 days ago

Hello,

 

We are now soft-launching support for the Model Context Protocol (MCP) within the Android Management API (AMAPI). While this is a “behind-the-scenes” infrastructure update, it is the critical first step toward a new way of managing devices. By exposing AMAPI via MCP, we are providing the standardised building blocks that will allow EMM providers to eventually build high-quality, conversational AI assistants.

The Engine Under the Hood: Why MCP Matters

Think of MCP as a universal translator.. It allows AI agents (like the ones powering smart chatbots) to securely “read” and understand the technical data from your fleet - like device policies, battery stats, and security logs. 

By standardising how AI interacts with Android device data, we’re making it faster and easier for EMMs to evolve their dashboards, toward a conversational, intent-based model.

The Shift: From “Point-and-Click” to “Just Ask”

What does this look like in practice? Imagine it’s 4:55 PM on a Friday, you get an urgent request to identify how many devices in your fleet need a critical security update before the weekend.

Traditionally, this means logging into your console, navigating sub-menus, filtering, exporting a CSV, and manually cross-referencing a report. It works, but it takes time you don’t have.

With our new MCP-enabled infrastructure, you’ll be able to ask:

"Show me all Zebra devices with a security patch older than 90 days."

And just like that, the answer is there. No filters, no CSV exports(!) - just the insight you need, instantly.

 

Mock example of interaction:


Proactive Management for Every Admin

This shift empowers admins of all skill levels to investigate issues faster and automate complex tasks without needing to be an expert in every corner of the EMM console.

The goal is simple: move away from static dashboards and complex menus toward a conversational, intent-based model.

Imagine having an intelligent assistant that understands your fleet data as well as you do. Instead of hunting for buttons, you can have a dialogue with your management console to:

  • Diagnose issues instantly: "Why did the latest app installation fail on Mark’s tablet?"
  • Proactively maintain hardware: "Find all devices with degrading battery health that need replacement next month."
  • Spot security risks: "Show me devices that failed a strong integrity check in the last 24 hours."

 

What’s Next?

We want to hear your thoughts as we see this shift. Are there any particular use cases you think you would like to use this for? What acronym do you think will stick for this next phase of device management?

As we roll out these capabilities to our partners, you can expect to see your management tools becoming smarter, more conversational, and more proactive.

  • Keep an eye on your EMM updates: Look for new "AI Assistant" or "Natural Language Search" features in your roadmap.
  • Ask your vendor: If you want to manage your fleet by simply asking questions, tell your EMM provider you’re ready for AI-powered management supported by Android's MCP integration.

The days of digging through dashboards are numbered. The conversation is just getting started!

Updated 5 days ago
Version 3.0

6 Comments

  • Michel's avatar
    Michel
    Level 4.0: Ice Cream Sandwich
    10 hours ago

    Interesting development for sure, and I see the benefits, but have to admit than when i started reading this post I was kind of hoping it would evolve in something else. 

     

    Conversational AI is nice for getting info such as in the example, but i'm sure we can do more with AI and the data that will be shared via our Android devices. How about a dashboard showing statistics and upcoming issues based on analyses of device data. Device experience for the end user is a up coming topic next to SLA's. Can't we use AI to proactively show us what issues might show up in the feature and respond on that? 

     

    If I need to ask my AI to list all outdated devices, i'm already to late. Or it would be an easy dashboard which can open with one click (as Moombas​ mentioned as well, typing takes time). One click overview beats a conversation with AI if you ask me. 

     

    Don't get me wrong, I am a big fan of AI, but I think we should look past the conversational AI and towards to more proactive AI (is there a name for that?)

    • JordanOC's avatar
      JordanOC
      Google Team
      10 hours ago

      Hey Michel​,

       

      I'm on your wavelength here for sure. I'll be honest, I'm mainly relieved to see this discussion move beyond "AI is great" to actual utility. 

       

      The main purpose of this post was to highlight the release of the MCP server we have just made available to EMMs and to give some lower stakes, "art of the possible" ideas without having to jump through additional hoops. At a high level, the MCP server packages a request nicely for the EMMs to interpret and expose as they see fit, curious if you have any additional thoughts on this bit Michel​ & Moombas​.

       

      I think "proactive AI" might be caught in the "agentic" discussion but that might be stale in 6 months 😅

      • Moombas's avatar
        Moombas
        Level 4.4: KitKat
        10 hours ago

        Yeah always start with the low hanging fruits and work up to the higher ones.

        I'm pretty sure at some point we will see something like that.

        Even on thing will be very likely not hit me as I know from our current MDM and most likely the others will do the same, AI will come along with additional license costs. Not sure if (at least on our end) we need it.

        You would need to get something in return and thats nothing i see yet on our side.

    • Moombas's avatar
      Moombas
      Level 4.4: KitKat
      10 hours ago

      I think we can get a gain out of it during troubleshooting if it provides reliable data.

      And if i say troubleshooting, i mean something like a call/meeting where the AI may listen and on site can provide "one click" overviews/dashboards or so on side saving time during that meeting.

      Or if the input for the filtering/dashboard is very complicated but speaking (not writing) it out to the ai to find the relevant devices can safe time when you in parallel can do other stuff.

       

      But as said before, it's the beginning and yet nothing i need to use and trust fully, sorry ;)

  • Moombas's avatar
    Moombas
    Level 4.4: KitKat
    11 hours ago

    Hey,

    definitely interesting to read but i might be oldschool on just those to points:

    • "The Shift: From “Point-and-Click” to “Just Ask”"
      • But, depending on the complexity of the actions behind the question, point-and-click might be way faster than asking (especially if you need to type the question in).
    • "The days of digging through dashboards are numbered. The conversation is just getting started!"
      • To be honest, the results of AI are nice but not 100% reliable yet. We are in an area where we need the 100% accurate data, so from my end, until this isn't solved and AI provides me with not matching results (which can be easily overseen in a large output), i still prefer the dashboards.

    I agree to, we are at the "start" but in this area i stay on my manual work but open minded to when AI gets more reliable.

     

    I already like AI when programming even the suggestions there are often are not accurate but this can be tested and aligned before used. 😅

    • JordanOC's avatar
      JordanOC
      Google Team
      10 hours ago

      Hey Moombas​,

       

      Completely agree with your points, that's where I think EMMs are in a pretty unique spot to deliver a great experience. AI is only as good as the data it is working with, in theory, every device record, policy information and report is in a standard structure on the EMM backend so it should be able to process everything without hallucination.

       

      Then it's a case of what do the EMM's do next, a few things off the top of my head:

      • Analysing, you'll be able to build a "perfect" dashboard for any scenario that you can save for future consumption or get reactive information on demand. 
      • Policy creation, the EMM should be grounded in it's own documentation and feature availability. Providing guidance on if you should edit an existing policy or create a new one, bonus points if it can auto generate a name and description based off your pre-existing best practices.
      • Supporting users, it should be able to look at your ticketing system and offer guidance on new issues and flag if other devices may be impacted by a reported issue. 

       

      For "the shift", I think most experienced IT admins will be able to navigate their EMM of choice quicker than an AI will be able to process the request for quite some time. Hopefully with these tools, folks who aren't quite as experienced can begin delivering at that same level.

       

      Let's see :D